4 ms·
> To a project manager, the programmer who hits every deadline (regardless of quality) is a good programmer. > To a customer, the programmer who solves their p
by anthonyb 14y ago
> To a project manager, the programmer who hits every deadline (regardless of quality) is a good programmer.
> To a customer, the programmer who solves their problem quickest is a good programmer.
Up until the codebase is such unbelievably appalling shit that you can no longer add new features, solve problems or reliably hit deadlines. I have worked on too many of these projects to be able to easily count them.
Typically, I'll be the one fixing up something after the previous developer has run away or has been sacked. There's often a culture shock when the manager/customer/project manager who is used to calling the shots suddenly finds that their latest idea needs to take a back seat while deeper (often 'invisible') problems get fixed.
Perhaps another take is that a "good programmer" is one who is still around and still adding features after a couple of years.
- prostoalex 14y agoIn the real world (or at least the world of garage sales and Antiques Roadshow), one man's junk is another man's treasure. In the programming world, one man's treasure is inevitably another man's unreadable spaghetti dependency-ridden junk.
- flyinRyan 14y agoNo, in the programming world there are projects that met the revolving door of mediocre programmers that no one is proud of, no one understands how it works or wants to, everyone just finds a place they think will have the effect their being driven to make and takes a shot.
- anthonyb 14y agoYeah, the code you're working on is really treasure in disguise. Whatever gets you through the day...
- ShawnBird 14y agoIf you are doing it for an employer it is at least worth what they are paying you for it. I would argue that qualifies as treasure.