I’m a product and design system designer/developer
working for GitHub remotely from London.
What I’m doing now
- Designing GitHub Actions
- Co-administrating the Email Geeks Community
Latest from my feed
It turns out the cure for a weekday hangover is pulling the blinds down and listening to Brian Eno.
I needed to remove a column from a really long markdown table in an efficient way. This little web utility probably saved me an hour of manual effort.
Reclaiming My Time | Miriam Eric Suzanne
I’m several months late for a 2022 ‘year in review’, or a ‘new years resolution’ for 2023. I’m even late for the intro I wrote a few days ago.
That’s ok. This is my website, not my side hustle.
If I had more time, I would have recorded a shorter Loom.
Gratitude For a Web That Tries Not to Break - Jim Nielsen’s Blog
This made me wonder: how long will we really keep every feature of CSS? … How long can we reasonably go without removing the old? How viable is this approach over time? 100 years from now, will people still be able to write
floatin their CSS?
I can definitely see a future where either a new browser engine or a significant engine rewrite decides to support only a more “modern” subset of the CSS spec — especially if it’s Chromium. I don’t know the first thing about writing an engine but I think for that to work it’d have to reduce the net maintenance burden even after considering how to handle rendering sites using older CSS.
I could also see directional properties being deprecated from the spec in favour of logical properties (e.g.
margin-left) but this seems so far away. I’d be pleasantly surprised if that began by the end of this decade.
(I actually think
floatis an interesting but ultimately bad example since using it for layout was always a hack. It was and continues to be useful for its intended purpose, even if seldom used.)