Many other patterns in the text, re-arranging to make it more obvious:
Why do we estimate stories? Because developer time is expensive and someone has to budget for it.
Why do we prioritise features in backlogs? Because we can’t build everything and we need to choose what’s worth the cost.
Why do we agonise over whether to refactor this module or write that debug interface? Because the time spent on one thing is time not spent on another.
We have compilers: either it compiles or it doesn’t.
We have test suites: either the tests pass or they don’t.
Planning. Estimating. Feature prioritisation. Code review. Architecture review. Sprint planning. All of it is downstream of the assumption that writing code is the expensive part.
... type systems, linters, static analysis. Software gives us verification tools that most other domains lack.
Mario Zechner aka badlogic - (co?)creator of libGDX (for us old farts who were around in the early Android days): https://libgdx.com/
Later also heavily involved with Spine, which IME is still the defacto industry standard for 2D skinned animation in mobile/web games: https://esotericsoftware.com/
There is something different about CEOs that came from tech.
reply