Bookmarks

The article has a lot of explanation around why pure black/white is a bad idea, but the really useful thing is a nice collection of off-black colours listed at the bottom of the article.

Clever approach to measuring CO2 emissions from frontend apps: gathering resource usage via th PerformanceResourceTiming API, then passing it through CO2.js. I'm still slightly skeptical that the mapping of resource size to emissions really holds for all types of sites but I think this a more realistic model.

Detailed look into precise details of how colour contrast applies to components - specifically how a border around an input field interacts with background colour - and how exactly the WCAG requirements work. My takeaway is that it only matters that there is 1 aspect of the component that is contrasting, as it means that component can be recognised.

Series of posts describing the Mini-M style of meetings, designed to support and grow managers (in a larger org, where there are at least 3 - 4 managers across Engineering-adjacent departments). It's structured as a support group where managers can help each other and develop each other's ideas. I like the framing of it being a "cabal" that work together to implement changes across the org, but question how effective that would realistically be.

Walkthrough of a new option in Git rebasing, why it is helpful for working with "stacked branches" (branch off a branch off a branch) and how to use it. I'm pretty convinced this will be better, as I tend to like working with stacked branches. And as a bonus, it's possible to set it as a default option, so all rebases have this behaviour.

Interesting pixel-style monospaced font. Surprisingly looks pretty good for code samples.

The entirety of Chris' book on using SVGs on the web. It's a few years old now, but I enjoyed the paper copy and thought it was a good summary of when to reach for SVGs, particularly around icons.

Great post outlining the concept of a "rhetorical situation", a specific structure that can be used to break down and analyse individual pieces of communication - in the context of software engineering, many of the examples revolve around code review. It could be a useful tool for making communication more effective by ensuring all pieces of the structure have been considered.

One of those tools to generate a range of colours based on starting and ending input colours. Seems like it has quite a lot of pre-written curves to generate the colours.

Pretty much does what it says on the tin. Possibly useful if for some reason an icon isn't viable.

Nice & lightweight icon search across a large number of icon collections.

Good article on increasing touch target sizes, particularly for mobile. There's a big grab bag of potential problems and solutions. The first section in particular is more general UX principles, then going onto looking in detail at CSS implementation details.

Interesting API to provide robots.txt output to block (known) various web scrapers, including those from AI bots.

Clear description of the behaviours of the new popover attribute, particularly focused on the "accessibility guardrails" that it automatically applies. Will be useful reference for what precisely the behaviours are.

Adam Argyle has written the CSS for animating one of the elements with the new popover attribute so that we don't have to. It's pretty clean too!

Interesting new technique to use the mask property to link to an SVG to create icons. I think I'd want to test this without the pseudo element though.

Nice practical description of composition and comparison of the different ways it can be implemented.

Useful and practical uses for the new :has() selector

Brief (and unfortunately cut off for non-subscribers) description of a format of a technical (IC or leadership) interview they call "Career History". The summary is that you find 3 - 4 roles in their history then ask the same rough set of questions about those roles with a view to discovering what the trajectory of their career is. There's also a description of red flags to watch out for (mostly lack of improvement and lack of empathy). The structure intentionally doesn't follow questions that the interviewee may have polished, prepared answers for, which I can see the value of but worry isn't the best for neurodivergent candidates.

Thorough explanation of how different physical and virtual keyboards (such as French AZERTY and German QWERTZ keyboards) can affect the KeyboardEvent events.