Re:Every time an engineer joins Google, a startup dies
by hello_moto on Thursday February 11, 2010 @04:13PM
(#1118770)
Speaking about legacy code, I read somewhere (probably via twitter) that new hires were given Michael Feather's book: "Working Effectively with Legacy Code".
I have a lot respect to companies that acknowledge these kind of issues and try to fix them.
I know there are many companies that just tell the engineers to quit whining/complaining about the current system and keep patching issues (fire and extinguish).
Re:Every time an engineer joins Google, a startup dies
by babycakes on Friday February 12, 2010 @09:53AM
(#1120648)
They have me a copy of that book during my orientation at Google, along with a series of other books on the core languages used within Google. Obviously, it's up to every engineer to put that to good use, but the company is making an effort to have people do things the right way.
Re:Every time an engineer joins Google, a startup dies
by hello_moto on Wednesday February 17, 2010 @10:28PM
(#1133323)
May I know the titles of the other books?
That being said, I have incredible respect for Google for being a few engineering/science driven Internet companies out there, which respects great hackers and beautiful, quality code. Most Internet companies (including many startups, with few great exceptions) are solving social, rather than scientific or technical problems and treat developers the same way Google treats servers (as a commodity, where the ability to replace them quickly -- and make do if they're unavailable -- is more important than their quality).