Burton Smith

Women's clothing sizes are the dumbest, most nonsensical thing ever...

One of the pain points of my #WebComponents type parser was its inability to parse types from "node_modules". Now it will parse them, and if it can't, it logs a warning with the type name, declaration location, and reason it was skipped. wc-toolkit.com/documentation/…

@mitchellh I also think there's a weird mentality being pushed sometimes where you're either 100% all-in on AI or you're not at all and being left behind. I think AI is another great tool I get to add to my arsenal.

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

@stolinski @wesbos They're from Canada. 😂

@wesbos My users are pretty underground, you probably haven't heard of them.

the libraries i use are so obscure that no one would bother compromising them.

@ryanflorence @diegohaz @stolinski The way we have worked around this in the past for clickable cards is to pass the click event to an interactive element within the card and tell it to ignore other clicks to prevent other element clicks from bubbling up to the card-level click event listener.

@ryanflorence @diegohaz @stolinski I love this idea! My biggest concern is that this would open the door for accessibility issues. That card scenario is a good example. It results in nested interactive elements. accessibilityinsights.io/info-examples/…

Remix 3 mixins are like components for element behavior. One thing I love about them is it gets rid of the awkward as/asChild composition dance.

In #WebDev, do you say "semi-bold" or "demi-bold"? #DesignSystems #CSS

@mattpocockuk This is great! Thank you! In the video you mentioned you have a video about preventing entropy. Are you able to provide a link to that?

AI helps you move faster, but it just accelerates software entropy. Here's how to de-slop a codebase ruined by AI, with one skill:

As always, a classy talk from @SALTnBURNem_636 @stirtrek! #DeveloperCommunity

CSS's light-dark() now accepts images, making it simpler to define alternate values for a dark color scheme. Here's how it works:

If you're using the Custom JSDoc Tags plugin for your #WebComponents, you can now add them at the property level! #property-level-custom-tags" target="_blank" rel="nofollow noopener">wc-toolkit.com/documentation/…

@stirtrek Let's gooooo!

🎙️ @stuffbreaker is speaking at #StirTrek2026! "The 5 Fundamentals of UX Everyone Should Know" 📅 1 May 2026 11:30 AM 🎟️ events.humanitix.com/stir-trek-2026… We're really looking forward to having Burton at Stir Trek this year!

@nicola_sosio @stolinski I'm saying this assumption is not necessarily true. x.com/i/status/20372…

@stuffbreaker @stolinski Not following you

Over engineered react patterns have poisoned how AI writes Svelte and other framework code. Like yo, it doesn't need to be that complicated.

@nicola_sosio @stolinski I would also argue that because of the quantity of varying quality and the amount it has changed over the years means that AI is more likely to struggle with React code. Quantity !== Quality

@stolinski Market will tell

@DavidKPiano @wesbos I heard they prefer "Frisky" and the people that live there are "Friskies".

@wesbos Tell her what? - It never gets that cold (F) - It's almost always that temp (C) - Nobody from there calls it San Fran (learned that the hard way)

My wife’s never been to SF. Who’s gonna tell her

When I was at Microsoft, we were trying to find ways around some of the pain points of #WebComponents, so I did an exploration on what Declarative Custom Elements could potentially provide us. #html #css #javascript dev.to/stuffbreaker/h…

@schneidenbach @kenwheeler

if your 250lb friend isn’t eating at least 100 big arches a month, something is wrong

@kentcdodds This isn't new. I think it's kind of weird that engineers have not traditionally been expected to be part of this process, but are now since they're not doing the grunt work of building things as much.

In the near future, the most important skills include "taste" and knowing the right product decisions to make. How do you teach this?

@DavidKPiano @kentcdodds This image is confusing if I try to follow the arrows.

@kentcdodds Double Diamond designcouncil.org.uk/our-resources/…