Vibe Coding Our Way to Disaster

Jake Nations' piece is quite well written. I liked his ideas. I do think it is funny that he spun his argument from how to b concise and code with AI less (hence the title) back around, explaining a new vibecoding structure. It's a good bit. I do like Hammock-Driven Development as a title, I personally always have thought more research and design before starting is good, but also there's times you just have to wait till you run into a problem face first to see it. I think times like that is when you step away from the desk, and remind yourself of a design, and tweak before going back in. Lightweight though because I cant be bothered to make large artifacts every task :D.

                Once upon a time,
                Chat told me I did a good job. 
                Now Job and Prod gone
            

Cassidy seems like so much fun! I am super excited to meet her, and I think the most pressing question I have is when you find something in your work sphere that you want to change (habits/relations/etc), how do you set about exacting that change?