new blog post: Vibe Coding for Flickr CC 4.0 Attribution
https://www.speedofcreativity.org/2025/07/05/vibe-coding-for-flickr-cc-4-0-attribution/
s/o @cogdog
People who tell me how unproductive AI is (as I check socials between #vibecode prompts)...
...are like virgins saying how sex is yucky.
@bruce learn to #vibecode in #gravy! Can't call yourself a #fullstackdeveloper unless you know how to get the bot to write #gravy.
This is where llm-assisted coding is at now (#llm #llms #chatgpt #vibecode)
I was having a bug yesterday where I suspected another program is messing with the files my agent is trying to edit. I barely know ebpf, tried a few tools to track reads/writes, then decided to roll my own. Most of this was built on entire autopilot while yapping on stream or at the coffee shop this morning.
I also generated a full in depth 8 module course to teach me what is actually going on.
It has a realtime web ui, database storage, all kinds of filters, a full documentation, it looks pretty, it worked pretty much right off the bat despite being totally non trivial in its design, and it took me basically 20-30 minutes of actual mental effort and yet I already learned a lot about kernel and ebpf. It’s not just a crud webapp.
Because noone in their right mind will shove #VibeCode|d #AIslop into #CriticalInfrastructure!
I don't #vibecode
I use AI for code suggestions and inspiration
The latest version of #ChatGpt #4o is very shit at coding.
I can see why #vibecode folk are frustrated and #luddites rejoice.
Eg;
Context "forgets" key spec points of the session, even ones that are critical to ops.
You have to jam everything with special checkpoint directives and hammer specs in, least they get forgotten.
It's terrible (and I have used earlier versions and #Claude)
In my opinion, what is happening because of the high compute burn, #OpenAi optimised the session manager. It burns less compute but is also more shit. The balance must be restored.
The way we build software is changing fast thanks to AI agents.
Cut through the "vibe coding" buzz – I explain what's happening, review tools like Copilot, Cursor, and Continue (plus local with Ollama!), and discuss how engineers can adapt. Importantly, I cover how this is reshaping the junior developer journey!
Check it out: https://nicolas.brousse.info/blog/agentic-development
I always forgot the exact ingridients or temperature. So I'm ...cooking... a simple companion app for my recipes. Will be easy to add/edit your own.
But first some designs and the biolerplate. Screenshot from actual app.
I honestly *can* see that AI could be helpful with really simple / monotonous tasks, like creating unit tests to help you describe what code you're going to write.
But would I let it write this code? Just no. This is terrible.
Oh wow:
```
If you're still seeing issues, we might need to try a different approach. Let's try creating a fresh SvelteKit project with Tailwind CSS using the official SvelteKit create command with the Tailwind
```
Wow, thanks #cursor. The last 10 minutes (and god knows how much compute power) was wasted on that slop.
Honestly Vibe Coding might be one of the most damaging things to the Software industry that I've seen in a fair while.