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).
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.
That's very interesting! I'll have to check that book out (just given some of the open source projects I've dabbled in), anyone else have an opinion on it?
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).