They use a seeded pseudo-random number generator to ensure the next word is still random, but can be matched back to the seed. It’s clever, and hilarious how often Anthropic use “random” to explain how LLMs work.

The current crop of “AI detectors” are absolute bogus. When Anthropic releases their watermark detection API a strong positive should be fairly trustworthy for long prose. In theory the same API could help to lower a watermark score with trial and error. Use a second LLM to replace potential watermark candidates with synonyms; frankenslop.

I really don’t like vibecusation. That is just as dehumanising as everything else the AI industry has polluted our culture with. AI disclosure should be mandatory, watermarks and auto-detection warnings are the second best option (if they work).

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

I keep seeing the word “taste” pop up in conjunction with AI usage in web development.

According to Syntax episode #1027 it is “taste” that now defines the “design engineer”.

I do think that this role in particular is such a huge role in the future now, of the world that we exist in with AI and all these things. And somebody who has design taste and design style is gonna be able to create some really amazing stuff.

5:57 - Scott Tolinski

Scott and Wes define a “design engineer” as someone who uses AI to be an expert in all roles.

It’s like, can somebody just look at a website that you’re building and say, that’s not the right tagline. That’s not the right copy. You don’t have to go through this whole thing of, like, oh, let’s get the copywriter involved.

7:15 - Wes Bos

You must listen to the audio to hear the disrespect dripping off that last line.

I’m guessing these are vibe-transcribed quotes so listen to the first 15 minutes for the full conversation.

Forget expertise, forget qualifications. Forget a career of research and training to deeply understand a profession. It’s all fair game for a design engineer with taste.

I hate to burst your bubble lads, but that is not a “design engineer” you’re describing, that’s a Jackass of all trades with an LLM addiction. Your “taste” is defined less by knowledge and more by financial privilege to afford another round of crackers to feed the stochastic parrot.

Wes stops reading the Vercel article being referenced before the important part:

We collaborate on everything because of each person’s unique background and skills. While each person can execute independently, we’ve found that our best work is done through collaboration. None of us is process/tools-driven. We care about the outcome, not the process/tool.

Design Engineering at Vercel

Vercel stress collaboration, not “tools” (AI is not just a tool.)

The reality is that LLM-driven development is the great leveller. Developers with access to the same LLMs are hitting their heads on the same skill ceiling. For those suffering imposter syndrome this is a relief. AI work mandates enable the quiet quitting their bosses feared.

The 10x unicorns love the taste of their own slop. Their dilemma is attesting superiority. The coping mechanism has become: “You’re prompting it wrong!” — think “MCP”, “skills”, “loops”, etc. Everyone believes they can rub the magic lamp more effectively. “Taste” in this context is the opposite end of the extrusion. They go off vibes because they never learnt what it takes to reason about good design. They’re overconfident in their ability because of limited exposure to real expertise. They don’t know what they don’t know.

So yeah, this design engineering defined by AI and “taste” is a bit silly, if you ask me.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

I’ve written for years about how WordPress breaks CSS and how horrendous theming has become the norm. I tried to raise issues but they went nowhere. My last remaining issue was closed today, unresolved.

After all this time the only manageable way to build bespoke WordPress themes is to disable the block editor entirely. I haven’t bothered to write up my approach but it’s very similar to Amber Weinberg’s “Building Modular Themes with ACF Flexible Content” — pair that with Terrence Eden’s “A big list of things I disable in WordPress” and you’ve got a similar base theme to mine.

I shared a tip recently to wrangle plugin CSS into a cascade layer. Perhaps a similar approach, with hooks or output buffering, can rein in WordPress pollution. It’s such a moving target though, I’d hate to maintain that.

These days I strongly advise clients to question whether WordPress is worth the investment. Most websites can be static with their infrequent content updates. Use a headless CMS for regular news/blogs if that’s cost effective.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

John Gruber posts “App Store Rejection of the Week: Dark Hours” (now retracted) about Terry Godier’s “Browsers have standards, the App Store has judgment” (since edited).

Godier claimed to have built an astronomy app called Dark Hours over four months, and that Apple rejected the app “on the grounds that it was Astrology”. Gruber ran with the story, heavily criticising Apple.

The next day Gruber retracted his post. The app rejected by Apple was called Asterly, not Dark Hours, and did in fact contain astrology, as Godier later admits. Gruber even gave Godier a draft before publishing his original post and Godier “offered not a word of caution”.

The story doesn’t end there!

The developer of an app called DarkHours called out Godier on Bluesky citing similar features and bugs. Godier quickly posts Mea Culpa - Dark Hours blaming AI and Claude for the rip off. Godier redirected his domain to the original app.

The original DarkHours also appears to be heavily vibe-coded. It’s MIT licensed too, so a simple attribution would have been sufficient. Comments on Mastodon suggest “It’s slop all the way down.”

Whatever the truth, these are dark hours for open source, that’s for sure.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

They were shipping 1.1 MiB of JavaScript to the browser to render markdown and syntax highlight code examples — in the browser.

They moved this work to the server (good) using React Server Components (bad).

RSC proved to be unbearable, even by TanStack standards. They then wrote their own markdown parser and syntax highlighter, and despite using SSR for the initial page load, they’re back to rendering markdown in the browser.

At no point in this palaver did anyone stop to ask, why are we re-rendering the same markdown for every request?

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

I checked The Pi Hut and Pimoroni both are priced the same for the UK market.

Raspberry Pi 5 for £292.80? Who in their right mind would buy that?

I see they introduced a 1GB model for £43.20. A 1GB Pi 5 has extremely limited use, a Pi 4 or even Pi 3 with more RAM would be a better choice. 1GB is a marketing scam. They can claim “from £43.20” and maybe trick a few unobservant suckers.

I bought my 8GB Pi 5 for £65.75 in 2023 and even that was way too expensive.

I’ve noted similar price hikes for computer parts. The PC and self-hosted hobby is dead right now. Guess who ruined it?

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Today I tried to rebuild my Tauri app and I get a weird error.

I run tauri info to find:

[✘] Environment
    ✘ rustc: not installed!
      Maybe you don't have rust installed! Visit https://rustup.rs/
    ✘ Cargo: not installed!
      Maybe you don't have rust installed! Visit https://rustup.rs/
    ✔ rustup: 1.29.0 (2026-03-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)

Weird, I thought I had installed Rust via Homebrew.

I run which rustup to find:

/opt/homebrew/bin/rustup

I run rustup and everything updates.

I check ~/.cargo/bin and see all the Rust tools are symlinked to /opt/homebrew/bin/rustup-init — the rustup-init file does not exist.

I delete everything and reinstall:

brew install rustup

Only to be notified:

This formula no longer provides `rustup-init`.

rustup is keg-only, which means it was not symlinked into /opt/homebrew,
because it conflicts with rust.

What does this mean? I’m using Homebrew because a package manager is supposed to be convenient. I’m not here for cryptic beer metaphors. What’s the point if it can’t install usable packages? This happens so often. Homebrew package break, I’m left trawling GitHub issues trying to make heads or tails.

So I give up and go to the original source piping install scripts straight to bash.

I get that Homebrew is an open source volunteer project. I don’t want to sound complainy. I just don’t understand what it’s supposed to do anymore.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Random talking with no context. I’m supposed to guess who is speaking and what they’re rambling on about? I look forward to the vague deja vu I get when it’s repeated in 40 minutes 🙄

This ain’t TikTok. Nobody is getting hooked on a poorly chosen mid-sentence quote that isn’t half as profound and the editor imagined.

I’m getting real tired of hitting fast-forward an unknown number of times to find the actual start. Much easier to hit unsubscribe.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

I can’t remember when or why I switched to VS Code. I moved to VSCodium for a short period last year and then gave Zed a spin.

These modern apps and their “developer experience” suck.

Sublime Text with five minutes of configuration in a breath of fresh air.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

(╯°□°)╯︵ ┻━┻

It’s practically impossible to control what CSS is actually output. The documentation and config are infuriating on missing details.

It’s not a problem until it’s a problem. As soon as you try to fix issues like animation shorthand a side effect is triggered elsewhere.

Lightning CSS is like one of those mini-games where you have to activate a row of switches but when you toggle one switch others are inverted. That game sucks.

I’m back to using ESBuild to bundle and minify CSS. If minification doesn’t matter, and it rarely does with HTTP compression, I’m using ten lines of janky Node.js to bundle CSS imports myself.

ESBuild is annoying too. I had to write a custom plugin shim to flag font and image URLs and “external” otherwise it cried about path resolution. I just want to bundle imports! Why is there no option to do the most basic thing?

I’m convinced none of these tool developers ever build real websites. Modern dev tools all have main character syndrome. Sorry, you’re not that important. By all means have your cryptic JSON dot file and CLIs for the converted. But please just export the no-nonsense primitive parts as a code library.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

TL;DR: keep your slop on GitHub.

Nice to see a project push back against the dead internet.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Shiki churns through all 932 code snippets on my blog in around ~1800ms. Lumis can do it in ~1400ms. On one hand that’s quite a significant saving, on the other hand it’s 2026 and I’m not running CI pipelines to rebuild the same code every commit. I hash-and-cache highlighted snippets so speed is a non-issue. And two seconds was never a problem anyway.

Lumis’ gimmick is that it uses Tree-sitter to properly parse code rather than regular expression pattern matching. In theory this should produce more accurate results.

Take a look at the before and after below. Lumis chokes on JavaScript template literal string interpolation.

Shiki can highlight whitespace. I bodged it myself in Lumis so ignore that random bar after @layer, that’s my mess. For these examples I used the Dracula theme which is objectively the correct theme under all circumstances. I slightly modified colour values in both Shiki and Lumis to boost contrast. I did not change where colours were applied.

Lumis does a better job picking up unique tokens like the CSS hex colour hash. However, I don’t think it’s always necessary to change their colour. I think hex colours should be a single highlight.

The JSX example below illustrates the opposite problem.

Why are the curly braces the same colour as the variables? The tokens were parsed but no colour was applied. Perhaps this is just a bad application of the Dracula theme. I’ll also concede that I’m used to seeing how Shiki does it.

Theme differences can be fixed if I cared to spend the time. That highlight mistake in the JavaScript code is more off-putting.

Side note: Lumis triggered GitHub’s vibe detector. There are slop commits and multiple SLOP.md files. All I’ll say is that quality of code is the least of my concerns.

All in all, not enough reasons for me to change. Maybe I’ll check again later.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

It’s nice to see CSS-Tricks ramping up quality content again. Following the Digital Ocean sale it was looking rather dicey. I feared it would be another .net magazine disaster. Remember when that just got eradicated? They promised to migrate content but now links just redirect to a generic landing page.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

I am persevering with Astro despite spending almost an hour trying to get my code editor to recognise HTML (it’s a modern app).

I was a little perturbed by Astro’s “Use minimal (empty) template” option writing a damned CLAUDE.md — come on! That’s absolute rage bait.

Now that I’m settled, Astro does look well designed and documented. The website I’m building is small enough should I ever need to jump ship. If Astro makes me snap I’ll take 11ty for a spin. If that fails I’ll go back to writing HTML as god intended.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Eric Meyer’s post on split-cell table headers uses @supports to detect Safari. I gave a drive-by suggestion to Sophie Koonin who adapted this for: “Time-based background colour transitions with Temporal and CSS color-mix” — that’s a really cool theme! I wish my website was themeable…

I would only use such a technique on sites I actively maintain. You never know what future browser versions might do to break it!

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Generative AI killed that career. Towards the end, I was asked to replace my thoughtful activity with ill-gotten slop. My prior activity was supported by my unique relationship with the tools and practices learned and refined over a long career of identifying patterns and differences. That experience, though shareable, was never fungible.

And the sea, Dent - Chris Dent

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.

Just skip to my next note.

Reading Salma’s post “Goodbye, forever, probably.” hits hard. Especially the part about AI killing developer education. I wish Salma all the best in her future.

I don’t like to swear so choose your own word: #$@! the AI boosters in this industry. Those selfish despicable #$@!s are destroying the web from the inside.

Personally I’m focused on my own challenge and opportunity. I’ve got no other skills to be successful offline. If I’m eventually driven away though, expect an explosive uncensored blog post! I’m half inclined to start naming and shaming these #$@! more directly.

I need a cup of tea to cool down.

Thanks for reading! Follow me on Mastodon and Bluesky. Subscribe to my Blog and Notes or Combined feeds.