is designing sociotechnical architectures

Low-Code vibes killed

One of the worst decision you could have made in IT the last couple of years was believing the no/low-code hype. Most of the times, it resulted in your code being hidden behind proprietary IDEs with a DX worse than that of a children’s programming language. Usually, this argument is brushed off, just to be revived when your team finds out 6 months after purchase that even companies as big as Microsoft have not been able to find a satisfying solution for code versioning so far.

In comes vibe coding and it just killed your 500-person-year low-code invest overnight. No- and low-code are dead. Your testers can now vibe code most of your no/low-code applications in under a week each and the more delicate integration stuff that has always been annoying is still being done by your most experienced engineers.

Best of all: now you do all of this in a well known, open source programming language like Python.

Edit: I just found out Kenneth Auchenberg had the same hunch 14 days ago: https://kenneth.io/post/no-code-is-dead-long-live-vibe-coding


This post is part of my “vibes after 100” series. After 100 days of vibe coding I decided to start writing down my thoughts. You will read a lot about killing. Because vibe coding is killing it.