> we're not architects, we're bricklayers. In the conventional business mindset programmers just implement a plan devised by someone else.
I think this analogy is wrong. Like architects, we can and must help requesters understand what's possible. "Architect, please design me a house supported by tiny pillars." "Programmer, please solve the traveling salesman problem for me."
> Consequently we are fungible (easily replaced by cheaper alternatives), and a cost rather than an asset.
The more central to a business their code is, the more this mindset will hurt them.
I think this analogy is wrong. Like architects, we can and must help requesters understand what's possible. "Architect, please design me a house supported by tiny pillars." "Programmer, please solve the traveling salesman problem for me."
> Consequently we are fungible (easily replaced by cheaper alternatives), and a cost rather than an asset.
The more central to a business their code is, the more this mindset will hurt them.