Archive: October, 2022


                    5th                     10th                     15th                     20th                     25th                     30th     


Monday, October 31st, 2022

Do You Like Rock Music?

I spent Friday morning in band practice with Salter Cane. It was productive. We’ve got some new songs that are coming together nicely. We’re still short a drummer though, so if you know anyone in Brighton who might be interested, let me know.

As we were packing up, we could here the band next door. They were really good. Just the kind of alt-country rock that would go nicely with Salter Cane.

On the way out, Jessica asked at the front desk who that band was. They’re called The Roebucks.

When I got home I Ducked, Ducked and Went to find out more information. There’s a Bandcamp page with one song. Good stuff. I also found their Facebook page. That’s where I saw this little tidbit:

Hello, we are supporting @seapowerband at @chalk_venue on the 30th of October. Hope you can make it!

Wait, that’s this very weekend! And I love Sea Power (formerly British Sea Power—they changed their name, which was a move that only annoyed the very people who’s worldviews prompted the name change in the first place). How did I not know about this gig? And how are there tickets still available?

And that’s how I came to spend my Sunday evening rocking out to two great bands.

Sunday, October 30th, 2022

A four piece rock band on stage. Sea Power in full flow lit by atmospheric yellows and reds.

🎶 The Roebucks 🎶 and 🎶 Sea Power 🎶

Checked in at The Bugle Inn. Sunday session — with Jessica map

Checked in at The Bugle Inn. Sunday session — with Jessica


Checked in at Haus On The Hill. Sunday Roast — with Jessica

Chrome 108 beta - Chrome Developers

I think this might be the most excited I’ve been in quite some time about an update to browser support, which probably says a lot about my priorities:

Support for the avoid value of the CSS fragmentation properties break-before, break-after, and break-inside when printing.


Overloading buttons

It’s been almost two years since I added audio playback on The Session. The interface is quite straightforward. For any tune setting, there’s a button that says “play audio”. When you press that button, audio plays and the button’s text changes to “pause audio.”

By updating the button’s text like this, I’m updating the button’s accessible name. In other situations, where the button text doesn’t change, you can indicate whether a button is active or not by toggling the aria-pressed attribute. I’ve been doing that on the “share” buttons that act as the interface for a progressive disclosure. The label on the button—“share”—doesn’t change when the button is pressed. For that kind of progressive disclosure pattern, the button also has an aria-controls and aria-expanded attribute.

From all the advice I’ve read about button states, you should either update the accessible name or change the aria-pressed attribute, but not both. That would lead to the confusing situation of having a button labelled “pause audio” as having a state of “pressed” when in fact the audio is playing.

That was all fine until I recently added some more functionality to The Session. As well as being able to play back audio, you can now adjust the tempo of the playback speed. The interface element for this is a slider, input type="range".

But this means that the “play audio” button now does two things. It plays the audio, but it also acts as a progressive disclosure control, revealing the tempo slider. The button is simultaneously a push button for playing and pausing music, and a toggle button for showing and hiding another interface element.

So should I be toggling the aria-pressed attribute now, even though the accessible name is changing? Or is it enough to have the relationship defined by aria-controls and the state defined by aria-expanded?

Based on past experience, my gut feeling is that I’m probably using too much ARIA. Maybe it’s an anti-pattern to use both aria-expanded and aria-pressed on a progressive disclosure control.

I’m kind of rubber-ducking here, and now that I’ve written down what I’m thinking, I’m pretty sure I’m going to remove the toggling of aria-pressed in any situation where I’m already toggling aria-expanded.

What I really need to do is enlist the help of actual screen reader users. There are a number of members of The Session who use screen readers. I should get in touch and see if the new functionality makes sense to them.

Blogroll | Max Böck

A lovely collection of blogs (and RSS feeds) that you can follow.

(Just in case, y’know, you might decide that following people on their own websites is better than following them on a website controlled by one immature manbaby who’s down with the racists.)

Saturday, October 29th, 2022

Suspension · Matthias Ott – User Experience Designer

But most importantly, always write your most important thoughts on your own site. You can share the link on as many platforms as you like and have conversations with anyone who wants to connect with you and your work. But nobody can take it from you. You are in control. Forever.

Thinking about leaving Twitter

This is how I feel when I open up my feed reader—it feels like the opposite of opening Twitter:

The web remains a sea of interconnected ideas, across a kaleidoscope of forms and sources. Spending most of my time on just a handful of billion dollar sites squanders the possibilities and runs contrary to my values. There’s so much to be said for diversifying inputs, but there are only so many hours. It makes sense to economize.


Some common geographic mental misplacements.

Little Rules About Big Things · Collab Fund

Pessimism always sounds smarter than optimism because optimism sounds like a sales pitch while pessimism sounds like someone trying to help you.

I usually hate these kinds of lists of bumper-sticker aphorisms but some of these have me pondering my own work, like this one:

People learn when they’re surprised. Not when they read the right answer, or are told they’re doing it wrong, but when they experience a gap between expectations and reality.

Or this:

There are two types of information: stuff you’ll still care about in the future, and stuff that matters less and less over time. Long-term vs. expiring knowledge.

Friday, October 28th, 2022

If you watch this video at 0.5 playback speed, it sounds like an angry drunk hobo slurring his speech has wandered onto the stage—so much better that way:

Design Principles For The Web - Jeremy Keith

Replying to a tweet from @wormmmoon


Here’s mine:

Thursday, October 27th, 2022

Checked in at The Lord Nelson Inn. Monthly session in The Nelson 🎶 map

Checked in at The Lord Nelson Inn. Monthly session in The Nelson 🎶

Wednesday, October 26th, 2022

Checked in at Jolly Brewer. Wednesday night session 🎶🎻☘️ — with Jessica map

Checked in at Jolly Brewer. Wednesday night session 🎶🎻☘️ — with Jessica

Programming Portals

A terrific piece by Maggie Appleton that starts with a comparison of graphical user interfaces and command line tools—which reminds me of the trade-offs between seamless and seamful design—and then moves into a proposed paradigm for declarative design tools:

Small, scoped areas within a graphical interface that allow users to read and write simple programmes

Design Principles For The Web - Jeremy Keith - YouTube

Here’s the video of the talk I gave at Web Dev Conf in Bristol recently. I think you can tell that I had fun—it was a good audience!

Design Principles For The Web - Jeremy Keith

Replying to a tweet from @jensimmons

I’ve added these to my home screen on my phone:


On desktop I’ve installed:


(for everything else I use bookmarks)

Tuesday, October 25th, 2022


Speaking of in-person gatherings, I’ve got some exciting—if not downright nervewracking—events coming up soon.

Next week I’ll be in London for Leading Design. Looking at the line-up that Rebecca is assembled, I’m kind of blown away—it looks fantastic!

You’ll notice that I’m in that line-up, but don’t worry—I’m not giving a talk. I’ll be there as host. That means I get to introduce the speakers before they speak, and ask them a question or two afterwards.

Then, one week later, I do it all again at Clarity in New Orleans. I’m really honoured that Jina has invited me to MC. Again, it’s a ridiculously fantastic line-up (once you ignore my presence).

I really, really enjoy hosting events. And yet I always get quite anxious in the run-up. I think it’s because there isn’t much I can do to prepare.

During The Situation, I had something of an advantage when I was hosting UX Fest. The talks were pre-recorded, which meant that I could study them ahead of time. At a live event, I won’t have that luxury. Instead, I need to make sure that I pay close attention to each talk and try to come up with good questions.

Based on past experience, my anxiety is unwarranted. Once I’m actually talking to these super-smart people, the problem isn’t a lack of things to discuss, but the opposite—so much to talk about in so little time!

I keep trying to remind myself of that.

See, it’s different if I’m speaking at an event. Sure, I’ll get nervous, but I can do something about it. I can prepare and practice to alleviate any anxiety. I feel like I have more control over the outcome when I’m giving a talk compared with hosting.

In fact, I do have a speaking gig on the horizon. I’ll be giving a brand new talk at An Event Apart in San Francisco in December.

It was just a month ago when Jeffrey invited me to speak. Of course I jumped at the chance—it’s always an honour to be asked—but I had some trepidation about preparing a whole new talk in time.

I’ve mentioned this before but it takes me aaaaaaaages to put a talk together. Don’t get me wrong; I think it’s worth it. I may not be good at much, but I know I can deliver a really good conference talk …once I’ve spent ridiculously long preparing it.

But more recently I’ve noticed that I’ve managed to shorten this time period. Partly that’s because I recklessly agree to prepare the talk in a shorter amount of time—nothing like a deadline to light a fire under my ass. But it’s also because a lot of the work is already done.

When I have a thought or an opinion about something, I write it down here on my own website. They’re brain farts, but their my brain farts. I consider them half-baked, semi-formed ideas.

For a conference talk, I need something fully-baked and well-formed. But I can take a whole bunch of those scrappy blog posts and use them as raw material.

There’s still a lot of work involved. As well as refining the message I want to get across, I have to structure these thoughts into a narrative thread that makes sense. That’s probably the hardest part of preparing a conference talk …and the most rewarding.

So while I’ve been feeling somewhat under the gun as I’ve been preparing this new talk for An Event Apart, I’ve also been feeling that the talk is just the culmination; a way of tying together some stuff I’ve been writing about it here for the past year or two.

It’s still entirely possible that the talk could turn out to be crap, but I think the odds are in my favour. I’ve been able to see how the ideas I’ve been writing about have resonated with people, so I can feel pretty confident that they’ll go down well in a talk.

As for the topic of the talk? All will be revealed.

Get Blogging!

Your easy guide to starting a new blog.

A blog is an easy way to get started writing on the web. Your voice is important: it deserves its own site. The more people add their unique perspectives to the web, the more valuable it becomes.

A beautiful red-haired retriever with a beloved ball in its mouth, lying happily on the grass in a park.

I had fun on the weekend, hanging out with my buddy Cider.

I broke the rules. - Manuel Matuzović

A reminder that silos like Twitter can suspend your account without warning for no reason.

Having your own website is good.

Monday, October 24th, 2022

Checked in at Dover Castle. Sessioning — with Jessica map

Checked in at Dover Castle. Sessioning — with Jessica

In person

I’ve had the opportunity to gather with my peers a few times over the past couple of months.

There was dConstruct, which I hosted. That was just lovely.

Then a few weeks ago, in spite of train strikes and travel snags, I went to Bristol to give a talk at Web Dev Conf, a really nice gathering.

This past weekend I was in London for State Of The Browser, this time as neither host nor speak, but as an attendee. It was really good!

I noticed something rather lovely. There was enough cross-over in the audiences for these events that I got to see some people more than once. That’s something that used to happen all the time but became very rare over the past two years because of The Situation.

None of the organisers of these events were pretending that Covid has gone away. Each event had different processes in place to mitigate risk. I wrote about the steps I took for dConstruct. For some people, those measures might seem to go too far. For other people, they don’t go far enough. This is a challenge that every in-person event is facing and from what I’ve seen, they’re all doing their level best.

None of these events were particularly large. Attendence was maybe somewhere between 100 and 200 people at each one. I know that there’s still a risk in any kind of indoor gathering but these events feel safer than the really big tech gatherings (like the one in Berlin where I got the ’rona—that was literally tens of thousands of people).

Anyway, all three events were thoroughly enjoyable. Partly that’s because the talks were good, but also because the socialising was really, really nice—all the nicer for being in relatively safe environments.

It’s not exactly an earth-shattering observation to point out that the social side of conferences is just as valuable as the content. But now that so many of us are working remotely, I feel like that aspect of in-person events has become even more important.

Or maybe I’m just appreciating that aspect of in-person events after spending such a long time with screen-mediated interactions only.

The transitional web | Go Make Things

I’ve smelt the same change in the wind that Chris describes here—there’s finally a reckoning happening in the world of JavaScript frameworks and single page apps.

Reading The Unreal And The Real: Selected Stories Volume 2: Outer Space, Inner Lands by Ursula K. Le Guin.

Buy this book

Sunday, October 23rd, 2022

Jessica on the couch with Cider, a golden retriever, both of them with their eyes closed.

Snoozy Sunday.

Saturday, October 22nd, 2022

Michelle Barker on stage in front of a screenshot of the Utopia website.

Another shout-out to! #SotB2022

A presenter on stage showing a screenshot of the Utopia website.

Shout-out to! #SotB2022

Friday, October 21st, 2022

The beautiful face of a red-haired golden retriever in a rare moment of repose.

Sleepy Cider.

Going to London. brb

Thursday, October 20th, 2022

Why We’re Breaking Up with CSS-in-JS | Brad Frost

I’ve seen the pendulum swing back and forth many times over my years building on the web. I too feel like there’s something in the air right now, and people are finally acknowledging that most single page apps are crap.

But Brad makes the interesting point that, because they were incubated when profligate client-side JavaScript was all the rage, web components may have ended up inheriting the wrong mindset:

So now the world of web components has egg on its face because the zeitgeist at the time of its design didn’t have such a strong focus on SSR/HTML-first/ progressive enhancement. Had web components been designed in the current zeitgeist, things would almost certainly be different.

Building the new Utopia homepage | Trys Mudford

Trys has written up how he made that nifty little resizing widget on the Utopia homepage.

Wednesday, October 19th, 2022

Replying to a tweet from @jkdodd

Yes! See you there?


A recurring theme in my writing and talks is “lay off the JavaScript, people!” But I have to make a conscious effort to specify that I mean client-side JavaScript.

I thought it would be obvious from the context that I was talking about the copious amounts of JavaScript being shipped to end users to download, parse, and execute. But nothing’s ever really obvious. If I don’t explicitly say JavaScript in the browser, then someone inevitably thinks I’m having a go at JavaScript, the language.

I have absolutely nothing against JavaScript the language. Just like I have nothing against Python or Ruby or any other language that you might write with on your machine or your web server. But as soon as you deliver bytes over the wire, I start having opinions. It just so happens that JavaScript is the universal language for client-side coding so that’s why I call for restraint with JavaScript specifically.

There was a time when JavaScript only existed in web browsers. That changed with Node. Now it’s possible to write code for your web server and code for web browsers using the same language. Very handy!

But just because it’s the same language doesn’t mean you should treat it the same in both circumstance. As Remy puts it:

There are two JavaScripts.

One for the server - where you can go wild.

One for the client - that should be thoughtful and careful.

I was reading something recently that referred to Eleventy as a JavaScript library. It really brought me up short. I mean, on the one hand, yes, it’s a library of code and it’s written in JavaScript. It is absolutely technically correct to call it a JavaScript library.

But in my mind, a JavaScript library is something you ship to web browsers—jQuery, React, Vue, and so on. Whereas Eleventy executes its code in order to generate HTML and that’s what gets sent to end users. Conceptually, it’s like the opposite of a JavaScript library. Eleventy does its work before any user requests a URL—JavaScript libraries do their work after a user requests a URL.

To me it seems obvious that there should an entirely different mindset for writing code intended for a web browser. But nothing’s ever really obvious.

I remember when Node was getting really popular and npm came along as a way to manage all the bundles of code that people were assembling in their Node programmes. Makes total sense. But then I thought I heard about people using npm to do the same thing for client-side code. “That can’t be right!” I thought. I must’ve misunderstood. So I talked to someone from npm and explained how I must be misunderstanding something.

But it turned out that people really were treating client-side JavaScript no different than server-side JavaScript. People really were pulling in megabytes of other people’s code to ship to end users so that they could, I dunno, left pad numbers or something.

Listen, I don’t care what you get up to in the privacy of your own codebase. But don’t poison the well of the web with profligate client-side JavaScript.

Why we need CSS Speech - Tink - Léonie Watson

I was talking about this with Léonie just yesterday. I, for one, would love to have CSS speech support. You know who else would love it? Content designers!

In these days of voice interaction on every platform, there is a growing expectation that it should be possible to design that experience just like we can the visual experience. In the same way an organisation chooses a logo and colour palette for its website, it stands to reason that they may also choose a particular voice that represents their brand.

It’s wild that there’s no way to do this on the web.

The Proprietary Syndication Formats - Chris Coyier

Guess which format is going to outlast all these proprietary syndication formats. I’d say RSS, which I believe to be true, but really, it’s HTML.

Monday, October 17th, 2022

Envisioning Our Shared Storm with Andrew Dana Hudson - Long Now

This observation feels spot-on to me:

The shift that I noticed, totally anecdotally, is literary writers are starting to write more dystopian climate futures and science fiction writers are starting to write about climate solutions.

Sunday, October 16th, 2022

How to (not) make a button - Tomas Pustelnik’s personal website

A demonstration of how even reinventing a relatively simple wheel takes way more effort than it’s worth when you could just use what the brower gives you for free.

Saturday, October 15th, 2022

Filtered for the miracle of writing (Interconnected)

You don’t need to write for anyone else. You don’t need to share, or even keep it. You just need the act of it. Writing is a particle collider for reality and the imagination. And new discoveries are the result.

(That’s why I write here, of course. It’s how I think.)

It me.

Simon Collison | Building with a lightness of touch

If, like me, you despair at the tech stacking and JavaScriptification of everything, shut that out and pay attention to those who understand the material of the web, its inherent resilience and efficiency. We’re lucky that principled voices still advocate for simple and inclusive methods because building with efficiency and a lightness of touch makes the work feel meaningful and, sometimes, fun.

Thursday, October 13th, 2022

Two JavaScripts

There are two JavaScripts.

One for the server - where you can go wild.

One for the client - that should be thoughtful and careful.

Yes! This! I’m always astounded to see devs apply the same mindset to backend and frontend development, just because it happens to be in the same language. I don’t care what you use on your own machine or your own web server, but once you’re sending something down the wire to end users, you need to prioritise their needs over your own.

It’s the JavaScript on the client side that’s the problem. What’s given to the visitor.

I’d ask you, if you’re still reading, that you consider a separation of JavaScript between client and server. If you’re a dev, consider the payload, your bundle and work to reduce the cost to your visitor. Heck, think progressive enhancement.

Replying to a tweet from @WillCapellaro

I’ve done a timer on my own site:

  1. Start a countdown.
  2. Try fetching from the network.
  3. If there’s no response after the countdown, try the cache instead.
A beautifully tabby cat sits primly on the keyboard and trackpad of an open Apple laptop on a desk with an expression that almost looks like a scowl.

Coco demonstrates correct laptop usage. 💻 🐈


The Customer Onboarding Handbook [PDF]

A free PDF with five articles:

  • The Brand Experience Gap by Emma Parnell
  • Ongoing Onboarding: Taking Customers from First Use to Product Mastery by Chris How
  • Just Add ICE: 3 Ways to Make Your Customer Experience More Meaningful by Candi Williams
  • Effectively Researching and Using Customer Journey Maps by Lauren Isaacson
  • Using and Abusing Surveys in Customer Onboarding by Caroline Jarrett

Three of those authors spoke at this year’s UX London! 20 years later | Stopdesign

Doug casts an eye back on the Wired redesign he worked on 20 years ago. It’s hard to overstate the impact this had on the adoption of web standards.

We’ve come a long way:

We’ve come so far since this redesign in 2002. We no longer trip ourselves up trying to fit everything above an imaginable fold. Designs respond to various screen sizes. Text is comfortably larger and screens display at a much higher resolution. We tend to give everything more breathing room.

Fontshare: Quality Fonts. Free.

A whole lotta nice fonts—most of them variable fonts—from Indian Type Foundry.

The Web’s Next Transition | Epic Web Dev by Kent C. Dodds

The primary benefit of Progressive Enhancement is not that “your app works without JavaScript” (though that’s a nice side-benefit) but rather that the mental model is drastically simpler.

I think that’s the primary benefit to developers. The primary benefit to users is that what you build will faster and more resilient.

Anyway, this is a really good deep dive into different architectural choices for building on the web. Although I was surprised by this assertion in the first paragraph:

The most popular architecture employed by web developers today is the Single Page App (SPA)

Citation needed. Single Page Apps do indeed dominate the discussion, but I don’t think that necessarily matches the day-to-day reality.

Replying to a post on

So nice! And I love reading about the decisions and process behind the redesign.

Progressively enhance for a more resilient web :: jjenzz

I realised, progressive enhancement isn’t only about supporting that 1%. It’s about testing your app without JavaScript to ensure 100% of your users have a more performant, usable, available, and resilient experience.

A really good explanation of progressive enhancement as an approach to building anything on the web:

Progressive enhancement does not mean you need to provide the exact same UI without JavaScript. The enhanced experience should be better and it should do more, otherwise the enhanced experience is not needed at all. It enhances a degraded experience that also allows the user to accomplish their goal. For example, entering a postal code manually into a text box might be the degraded experience, and the progressively enhanced experience would prefill the text box based on Geolocation data.

Tuesday, October 11th, 2022

Bunny Fonts | Explore Faster & GDPR friendly Fonts

A drop-in replacement for Google Fonts without the tracking …but really, you should be self-hosting your font files.


There’s a repeated catchphrase used throughout Christopher Nolan’s film Tenet: ignorance is our ammunition.

There are certainly situations where knowledge is regrettable. The somewhat-silly thought experiment of Roko’s basilisk is one example. Once you have knowledge of it, you can’t un-know it, and so you become complicit.

Or, to use another example, I think it was Jason who told me that if you want to make someone’s life miserable, just teach them about typography. Then they’ll see all the terrible kerning out there in the world and they won’t be able to un-see it.

I sometimes wish I could un-learn all I’ve learned about cryptobollocks (I realise that the term “cryptocurrency” is the more widely-used phrase, but it’s so inaccurate I’d rather use a clearer term).

I sometimes wish I could go back to having the same understanding of cryptobollocks as most people: some weird new-fangled technology thing that has something to do with “the blockchain.”

But I delved too deep. I wanted to figure out why seemingly-smart people were getting breathlessly excited about something that sounds fairly ludicrous. Yet the more I learned, the more ludicrous it became. Bitcoin and its ilk are even worse than the occassional headlines and horror stories would have you believe.

As Jules says:

The reason I have such a visceral reaction to crypto projects isn’t just that they’re irresponsibly designed and usually don’t achieve what they promise. It’s also that the thing they promise sounds like a fucking nightmare.

Or, as Simon responded to someone wondering why there was so much crypto hate:

We hate it because we understand it.

I have yet to encounter a crypto project that isn’t a Ponzi scheme. I don’t mean like a Ponzi scheme. I mean they’re literally Ponzi schemes: zero-sum racing to the bottom built entirely on the greater fool theory. The only difference between traditional Ponzi schemes and those built on crypto is that crypto isn’t regulated. Yet.

I recently read The Glass Hotel by Emily St. John Mandel, a novel with the collapse of a Ponzi scheme at its heart. In the aftermath of the scheme’s collapse, there are inevitable questions like “How could you not know?” The narrator answers that question:

It’s possible to both know and not know something.

I’ve been thinking about that a lot.

Monday, October 10th, 2022

Three gents playing Irish music gathered around a round table in a pub: a flute player flanked by a fiddler on either side.

Fiddles and flute.


Checked in at Dover Castle. Monday night session — with Jessica

dConstruct 2022 — Polytechnic

A lovely heartfelt personal look back at dConstruct.

dConstruct was about the big ideas, but not in a wanky TED way. It was about ideas on the horizon brought into focus, it always left me wanting to know more.

dConstruct was never about the big showy thing that will make you millions. It was about the interesting. It gave you seeds to take away with you, and that’s important.

Sunday, October 9th, 2022

Descriptive engineering: not just for post-mortems – Dan Slimmon

I wrote a while back about descriptive and prescriptive design systems—and a follow-up post—but I didn’t realise there was such a thing as descriptive and prescriptive engineering.

Saturday, October 8th, 2022

Checked in at The Brunswick. Ye Vagabonds — with Jessica map

Checked in at The Brunswick. Ye Vagabonds — with Jessica

Lots of fiddles and one mandolin resting on tables.

A break between tunes.

Replying to a tweet from @askalot

Oh, the short ones—my notes—are almost always from mobile.

It’s the longer posts—my journal entries—that are almost never from mobile.

Reading Patternmaster by Octavia E. Butler.

Buy this book
Jessica sitting at a table with burger and chips. There’s a cute dog at the next table.

Pub lunch in the countryside (with dog).

Friday, October 7th, 2022

The audio from dConstruct 2022

dConstruct 2022 was great fun. It was also the last ever dConstruct.

If you were there, and you’d like to re-live the magic, the audio from the talks is now available on the dConstruct Archive. Here they are:

Thanks to some service worker magic, you can select any of those talks for offline listening later.

The audio is also available on Huffduffer on the dConstruct Huffduffer account. Here’s the RSS feed that you can pop into your podcast software of choice.

If you’re more of a visual person, you can watch videos of the slides synced with the audio. They’ve all got captions too (good ones, not just automatically generated).

So have a listen in whichever way you prefer.

Now that I’ve added the audio from the last dConstruct to the dConstruct archive, it feels like the closing scene of Raiders Of The Lost Ark. Roll credits.

Thursday, October 6th, 2022

Replying to a tweet from @Cennydd

Service Guarantees Blue Checkmark.

A laptop on a podium in a dark cinema, showing a slide deck called Design Principles For The Web.

Tech checking.

Wednesday, October 5th, 2022

Replying to a tweet from @hober

I’ve implemented it on

Fiddle, banjo, and flute gathered round a table in a pub.

Lovely tunes at The Star tonight.

Three book spines: Circe by Madeline Miller, The Unreal And The Real by Ursula K. Le Guin, and All The Birds In The Sky by Charlie Jane Anders. Three book covers: Circe by Madeline Miller, The Unreal And The Real by Ursula K. Le Guin, and All The Birds In The Sky by Charlie Jane Anders.

Got a good haul from Bristol’s second-hand bookshops. 📚

Replying to a tweet from @kino_auge

Yes, I publish the notes on my own site and send a copy to Twitter:

In the Indieweb world, it’s called POSSE: Publish on your Own Site, Syndicate Elsewhere:

Tuesday, October 4th, 2022

Picture 1 Picture 2

Checked in at The Star Inn. Sessioning in Brizzle

Going to Bristol. brb

The Thorny Problem of Keeping the Internet’s Time | The New Yorker

This story of the Network Time Protocol hammers home the importance of infrastructure and its maintenance:

Technology companies worth billions rely on open-source code, including N.T.P., and the maintenance of that code is often handled by a small group of individuals toiling away without pay.

Style with Stateful, Semantic Selectors

I’ve done this quite a bit: using ARIA attributes as “hooks” for styling and behaviour. It’s a way of thinking of accessibility as the baseline to build upon rather than something that can sprinkled on top later.

A Web Component Story

I get it. React feels good and it’s sticky. But all frameworks eventually fizzle out.

Thanks to Web Components, large companies are realizing you don’t need to rebuild buttons and other UI primitives every few years. Teams don’t need to argue about frameworks anymore. You can have your cake and eat it too!

I think this may be the best long-term argument for web components:

Any org that goes all in on a single framework will eventually find themselves swimming upstream to hire talent to maintain legacy code and avoid framework rot. But you can reduce this burden (and the associated costs) by using Web Components in your design system.

Days Since Incident

I love this list of ever-increasing timelines. All that’s missing is the time since the Carrington Event, just to remind us what could happen when the next one hits.

Sunday, October 2nd, 2022

A group of fiddlers and box players playing in the corner of a pub.

Playing in a session in Charlie’s, my old watering hole in Cork from my Art College days three decades ago.


Checked in at Charlie’s. Back in Charlie’s after 30 years, this time for a session — with Jessica

Saturday, October 1st, 2022

Checked in at An Spailpín Fánach. Cork Folk Festival, like map

Checked in at An Spailpín Fánach. Cork Folk Festival, like