4 ms·
A few things: 80% of the projects I've worked on already had code written for them when I showed up to work on them. There's no difference between the existing
by padobson 12y ago
A few things:
80% of the projects I've worked on already had code written for them when I showed up to work on them. There's no difference between the existing investment in legacy code and the existing investment in a property.
New home builds also have gotchas.
Programmer's promising "magic" goes back to my original point of communicating with the stakeholders. If you're promising "magic", you're just asking for the project to fail. Be clear an upfront, and your customer will realize you're an engineer and not a miracle worker.
- jiggy2011 12y agoProperty investment is a little different because you can usually recoup at least some of the money spent at a later date by selling the property. A building without a wood rot problem will always be worth more than one with one, especially when the problem is likely to get worse over time if it's not dealt with. A software project on the other hand is typically worth close to nothing if it doesn't fulfil it's requirements , so the sunk costs are different. To the second point, the problem with programming projects is that you are often competing against more enthusiastic and less experienced devs who are naive and under estimate.