Hi, I'm David - you might be here because I - Wrote a couple of kids books about programming in JavaScript - Spoke to you at an event or conference - Had a fabulous time with you and a cocktail - Have offered you some software consulting Available at https://t.co/4q6CNLAqgj 🖤

Had a really great time with The Outer Worlds 2 this weekend. The reviews seem to be all over the place - which I think is perhaps reflective of how much your builds do seem to matter. Setting is still a touch indistinct, but ~15 hours in is hitting its stride.

It'll never happen because they probably only have the nerve to be cool one time, but Tron 4 should be soundtracked by Perturbator. You know it'd be great. Or Perturbator + Health + The Algorithm.

Also, that's an affiliate link, and I promise to embody the spirit of non-profit by ensuring that any proceeds go towards "entertainment in the metal bar over the road" ;)

Exited to be speaking at Build Stuff in Vilnius. It's always my last conf of the year, has great vibes and is always a great excuse for a party (the metal bar over the road from the venue is excellent). Come! 15% off tickets with this link:

Excited to be keynoting Init 2025 ( https://t.co/yeEWtC52vj ) on Banja Luka in Bosnia & Herzegovina this morning! A new country for me, excited to see it and meet everyone!

I want to manifest this into the world. It's a category of absolute dirt and muck that infects all software, in all languages. Makes comments actually useful and contextual. There is prior art - @wallabyjs does this during debug sessions. Why not prod.

Let's call them "Active Comments".

I wish we could re-invent comments to be the way we instrument code. I love the idea, despite it breaking from regular form. It might even rescue their utility. var id = 1; someAccount.IsLoggedIn = true; //? User {id} authenticated Imagine if that replaced endless otel/logs

Switching between a Mac and Windows a lot at the moment and one of the most useful things I've done is rebind the PowerToys Command Pallet to Win + Space - gives me a more or less identical launcher experience across the different operating systems.

Really enjoyed recording this very wide ranging conversation with @icooper and @hanneslowette https://t.co/KkXVPAR6EV

Thrilled to be back at NDC London 2026 in January with a new talk - Meditations on Code as Art. Tracing the through-line from digital graffiti and the Apollo 11 launch computer to the creative urge to see yourself reflected in your work. On sale now. https://t.co/lmo5qyMwAj

So I'm gonna be doing a new and ultra weird talk next year - and I'm doing a bit of a test run at DotNetNorth next month. https://t.co/RqRoOy9LO0 It's gonna be weird, come out.

There is no better timezone than "Romance Daylight Time".

Oh I have shaved 500 yaks and I would shave 500 more more...

Commemerating new conference talks by being "back on my bullshit" with some fun new shirts

A models output is an exaggerated version of a language or communities anti-patterns by default. Like any programmer with just enough knowledge and not enough context.

Incredible tools for experts that can provide that additional literacy, but each ecosystem anti-pattern is amplified by default. I love these tools, but if you're not re-working and co-authoring the outputs with refactoring iterations, you'll end up in a bad place.

JavaScript vibe code is often spaghetti/full of mixed concerns Good software design all exists in context, so while the tools are powerful, the true vibe coded "just go with it" approach will yield mediocre to bad results frequently without authorial control.

Interesting observation re:model assisted code - vibe coded software exhibits the average anti-patterns of the languages culture and ecosystem. .NET vibe code trends towards enterprise over/no-design (services, managers et al)

In fact, most of the ire you see against "object orientated code" is just ire against procedural code disguised as OO-code. And of course, yes, that stuff is bad.