3 ms·
This is exactly why I prefer tools that take a stance on what the right way to do something is. Even if I don't like some aspect, I at least have a little confi
by tsewlliw 15y ago
This is exactly why I prefer tools that take a stance on what the right way to do something is. Even if I don't like some aspect, I at least have a little confidence the author thought hard about a corner case and made a well considered decision.
At DevDays in Austin a couple years ago Joel Spolsky complained that at Freebirds ordering a burrito consists of telling them the recipe for a burrito. I've got work to do, I don't want to tell my tools how to make a burrito.
- jiggy2011 15y agoThe problem is a developer is not always in a position to make the decisions on what the right way to do things are. In order for a developer to understand the requirements of the software he requires a deep understanding of how the business works, which is probably at least as deep a the person specifying the software or managing the developer. Even if the developer has a better understanding that the manager about what is required he may still have rank pulled on him by the manager. A developer who understands the business well enough to write good software for it probably understands the business well enough to run it which makes the manager superfluous anyway.