4 ms·
More than anything, this reflects how many business decisions a "programmer" makes. If a "programmer" was actually just a programmer, none of their beliefs wou
by chmod600 5y ago
More than anything, this reflects how many business decisions a "programmer" makes.
If a "programmer" was actually just a programmer, none of their beliefs would matter. Either it met the spec, or not.
But in reality, a lot of the job of a "programmer" is to make all those detailed decisions, and handle all the exceptional cases, that other people don't want to be bothered to think about. But those detailed decisions and edge cases need to be handled because much of the value of software is running the business worldwide at all hours with fewer humans involved, so those edge cases will come up constantly.
So all these little decisions fall on the one writing software. That's actually an incredible amount of power once you realize it.
- secondaryacct 5y agoBecause the speed at which they can write good specs cannot match a competitor doing iterative back and forth from an elevator discussion. Even in large slow banks, we churn feature releases weekly now with half finished stuff behind feature flags to see if they like it so far. And well, it works and they re happier and we can have lighter BAs, and spec mistakes cost a lot less as they are spotted faster, not after 3 months of blind work. Oh and btw the value of software is not to handle every edge cases well, but to be able to change, imho.