It is incredibly easy now to get an idea to the prototype stage, but making it production-ready still needs boring old software engineering skills. I know countless people who followed the "I'll vibe code my own business" trend, and a few of them did get pretty far, but ultimately not a single one actually launched. Anyone who has been doing this professionally will tell you that the "last step" is what takes the maj…
I agree 100%. Boring old software skills are part of what it took to "write" this DSL, complete with a fully featured LSP: https://github.com/williamcotton/webpipe https://github.com/williamcotton/webpipe-lsp (lots of animated GIFs to show off the LSP and debugger!) While I barely typed any of this myself I sure as heck read most of the generated code. But not all of it! Of course you have to consider my blog to be "…
It was a lot of reviewing and proofreading and just verifying everything by hand. The only thing that saved me time was writing the test suite for it.
Would I do it again? Maybe. It was kinda fun programming by explaining an idea in plain english than just writing the code itself. But I heavily relied on software engineering skills, especially those theory classes from university to best explain how it should be structured and written. And of course being able to understand what it outputs. I do not think that someone with no prior software engineering knowledge could do the same thing that I did.