DevOps / SRE / Platform · 05.08.2026, 14:39 UTC
Every software company will become a dev tools company
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 05.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
If most software will soon be built by machines, the job of software engineers will change: from writing software to building the machines that write it.
Soon, engineers won’t be classified as frontend or backend, but as product engineers, who build the customer-facing product, and platform engineers, who build the tools those product engineers use. And since more and more code will be written by machines, we’ll need more platform engineers to build and fine-tune those machines.
“Call it harness engineering, call it loop engineering. It’s still platform engineering, and it’s building the tools every engineer depends on to write code at all.”
I’ve been thinking about it ever since the tokenmaxxing fiasco, and every time I read one of those reports showing that faster code generation, more often than not, just creates more friction downstream. Every team is wiring up its own prompts, its own guardrails, its own dashboard for tracking what the agent got wrong, none of it shared, all of it repeated across the org. Fragmentation, not speed, is what a hundred engineers each solving the same platform problem alone gets you.
Platform engineering, per its definition, means building the shared toolchains and workflows that let engineering orgs serve themselves, usually packaged into one internal developer platform covering everything an application needs across its life cycle. In plain terms, it’s developers building tools for other developers so the rest of engineering can ship with less friction. If you’re helping developers ship software with less friction, congratulations! …