This is really getting out of hand.
We all know that #NoCode sucked. We all know that block programming was never good for anything other than learning and prototyping.
But hey, it looks like #AI and #VibeCoding fare a bit better right? And they could actually be the killers of the draggable blocks that we were all looking for.
But of course AI makes a lot of mistakes as well, it hallucinates APIs and configurations that don’t exist, and it will probably break production if you don’t double-check its code - and leave you alone to clean up the mess.
So how do NoCode companies try to pivot in the age of LowCode/VibeCode?
Simple, mesh VibeCoding and NoCode together!
Companies like Bubble apparently are pivoting away from building their Lego Mindstorm IDEs, to building products that leverage AI to solve coding problems. But instead of generating Python, Rust or JS these models would generate output in the NoCode intermediate language developed by Bubble, which in turn gets translated into real code. The advantage, according to the proponents, is that an output in their NoCode framework makes it easier for a non-programmer to understand what’s going on (compared to some undecypherable Python I guess).
Like, how many layers of abstraction, points of failure, corporate lock-ins and unaccountable production errors are you as a business likely to accept, just to avoid paying a salary to an engineer, and just because you really want your sales people to deploy data pipelines instead?
] A short thread on why I reject the “Open Core” model — and why 
!
A
Just rebuilt my Notion-to-social media automation with webhooks in Make.com and N8N. So much cleaner now! 