So my @nuxt_js layers article "Modular site architecture with Nuxt layers" is finally over the line!. It's *by far* the most in-depth technical article I've ever written, and covers theory and practice of migrating any existing Nuxt site to layers – with

Get rid of ads in Google Chrome Mobile by toggling on this accessibility setting

Liquid Barf more like it 🤮.

Claude AI just saved me hours of frustration. Chrome wouldn't open, with a vague "cannot open app" error. Claude diagnosed a corrupted code signature (following some keychain permission issues) and fixed it with a single terminal command. Imagine doing this with just web search.

🧠 I built a little tool to remind me of media + cognitive biases:. ⚙️ It has 15 common biases (with Google links) and 5 ways to slice and dice. 🙏 Thanks to Claude AI + @AnthropicAI

Was just thinking about the amount of junk code Vibe Coding can create. Is this just Generative Coding's "too many fingers" problem?.

If only Vibe Coding worked for (legacy) build config 😭. There's only so many times it can guess the next approach before you have to call bullshit.

How do Twitter's ads know so fucking little about me?.

So I just saw an ad on my Facebook feed for a fashion brand "Peter and Co" with a very stylish-looking older couple and a story about how they were retiring after 20 years of owning a successful fashion brand to spend more time with their grandkids, and having a closing down

I've been deep-diving @nuxt_js UI 3's form logic. It's very clever how it layers up functionality (zod, useId, useEventBus, provide, inject, composables) to manage inputs, fields, errors, and the form as a whole. I may look to do a deep-dive blog post soon!. cc @benjamincanac.

Yup, this.

I'd say it's written probably 75% garbage code (that works) in 10% of the time. Chasing its tail the other 50% of the time, with me chasing its tail the remaining 40%. My gut feeling is it's like when the client wants to take the MVP into production and some poor sod down the.

In fact it reminds me a lot of "Hello. French Polishers? it's just possible you can save my life. ". "Get these glasses!". "Come on you stupid thing!".

I'm cracking on with my vibe coding project today, and whilst it one can go round and round in circles on some tasks, there are some clear benefits to this. I'm finding it's no so great at refining, or at least it will try and refine the thing you ask for, but tackle the new.

This one-shot vibe coding is a con. Once it's impressed you with its "awesome first try" further updates just descend into frustrating nonsense. And the more you don't understand about the code the harder it's going to be to make it work.

WebStorm view for reference

I recently started using Cursor but couldn't work out why it felt "cramped" compared to WebStorm. Eventually, I realised making the gutter background color and the editor background color is the trick to make things feel lighter. Settings here:.

Whoohoo!.

Is it me, or does Claude 3.7 write a lot of garbage code?. It seems to completely overthink things, write a shit-ton of code, then when it doesn't work and you dig in, there's some fundamental logic errors. It looks great, but sometimes really, really isn't.