Vibe-Coding

Why This Caught My Eye The argument is that code you vibe-coded becomes legacy code the moment you move on, because nobody understands it well enough to maintain it confidently. That includes you, two months later. This sits in direct tension with what I write about in the “Vibe Coded and Lived to Tell” series. My take has been that vibe coding is a valid learning ramp and a legitimate prototyping tool. I think both things are true: it gets you moving fast, and the output is fragile in a specific way that earns the legacy label. Interesting read. ...

Every Monday, I publish a blog post. Then I write five slightly different versions of “hey, I wrote a thing” for LinkedIn, Twitter, Bluesky, and Mastodon. Each platform has different character limits, different audiences, and different best practices. It’s tedious. I wanted to automate it. Not with a frontier model, but with a small local one running on my laptop. Something like phi or llama, through Ollama. I didn’t need a polished production app. I needed a quick prototype to test my theory. My theory was that a small local model can handle a real, recurring task. …and it can do it well enough to be useful. ...