31 Dec
2012
31 Dec
'12
1:32 a.m.
On 31/12/12 12:04 AM, Richard wrote:
In article<1356920299.64010.YahooMailClassic at
web120002.mail.ne1.yahoo.com>,
steve<gkicomputers at yahoo.com> writes:
Where I work we use Gerrit (a Google tool well integrated with Git).
Code review is pretty thorough and most commits are seen by all team
members. I highly recommend the practice for any team.
--Toby
Engineers get paid by generating code that works
within the performance
capabilites of the system it's implemented on, not how it looks.
This is only true for one-off contract work type software. When
you're working on a product that has a lifetime longer than a single
release, it is very different. Every company I've worked at has
considered the lifetime of the software to span beyond the first
release and "how the code looks" was most certainly important to them.
Reuseable
code is about 3x the cost of a point design,
Based on what? Again, this is not in line with my experience as a
person paid to write software. On my current team, we peer review our
code through a web application called Review Board. Making code that
isn't a cheap throwaway one-off doesn't cost us 3x more.