They'd rather treat the general version of Greenspun's 10th rule as a commandment, and create a new, ad hoc, informally-specified, bug-ridden, slow implementation of some fraction of whatever already addresses the requirement, than learn about how to use some existing tool that they don't already know.
One of my favorite examples is a company that home-rolled their own version of (a subset of) Kubernetes, ending up with a fabulously fragile monstrosity that none of the devs want to touch any more, and those who do quickly regret it.
I sure hope it doesn't involve a bunch of shell scripts to create a new, ad hoc, informally-specified, bug-ridden...
1. there's too much to learn and know, and the cs courseware and interviews are all about algorithmic complexity, rather than business setup and operations. same with "how do you raise money" vs "how do you make a great customer experience"
2. the market rewards building the new functionality, not building all the standard chunks required to run a business
if anthropic had great customer support built out, but no model and no claude-code, theyd be much worse than they are now having stuff people want but lacking the ability to serve it
---
clearly theres still plenty of b2b startup opportunities standardizing how all these things work, so that business can focus on their actual business rather than recreating all the basics
The ageism in tech probably has something to do with it.
When I see some of these brobdingnagian disasters, I always wonder if there were any adults in the room, when the idea was greenlighted.