3 ms·
> ...there are places where people know pretty much what they are doing, most of the time. It's called spec programming, where you have programmers slinging co
by AuthorizedCust 8y ago
> ...there are places where people know pretty much what they are doing, most of the time.
It's called spec programming, where you have programmers slinging code against precise specifications. Common in ERP and regulatory or business compliance-driven code.
On the other hand, you have development. That is where you're attacking the less defined problems. Sure, we know the tools in our toolset, how to apply them, and time it takes to apply each tool. Problem is, the time to figure out the series of tools needed and their precise applications burns enormous time, time that could have been spent towards a MVP.
- mannykannot 8y ago> Problem is, the time to figure out the series of tools needed and their precise applications burns enormous time. In the use of the adjectives 'precise' and 'enormous', you are just repeating the same false dichotomy in a slightly different form, by ignoring (or not understanding) my point about the use of abstraction in analytical thinking. The people who are most successful in what you distinguish as development understand a good deal more about what they are working on than spec programmers need to, and they are not, as you imply, groping around in the dark for a solution - that's what spec programmers do when faced with a development problem.