Layers of abstraction and speedy development have left engineers unable to understand what lies beneath
You must log in or # to comment.
Abstraction is a problem now? OK… So startups are supposed to spend years understanding the market, then a few more years developing a possible product in assembly (remember, no abstractions), and somehow be successful at that.
We can’t all be funded by the NSA, my friend. Some of us don’t have 1B$ to lean on when developing our first product. Trust me, if I had that kind of money, nothing would be able to hurry me. But the unfortunate truth is that most of us have bills to pay without a war chest and while we spend our time deeply familiarising ourselves with something, that’s costing money, and it has to come from somewhere.
UBI would probably solve this, but until then, the majority cannot understand every layer they use - and most likely even most of us will have more fun making something that works.
Agile in corporate is shit, for damn sure. However just because you understand systems and can peel away abstractions, doesn’t mean you can and will make a great product. One does not forcibly mean the other. It can, but it doesn’t have to.
I’m with you on this one, that reads like a circlejerk par excellence. Let’s claim “agile” is at fault - and he might be right if he just defines it as corporate silo feature factories.
But he somehow missed the fundamental of what he means when he uses that word. This way it’s just a “we’re cool, the rest isn’t” - the most boring kind of tribalism.
Instead of baking a cake it’s “to write an app you first need to create a universe”.
