First EVER YouTube, and hopefully the first of many to come ๐จโ๐ป watch this if you've a React/Next.js project that's got long-neglected ARIA issues coming up in Lighthouse
https://t.co/S8wwnt8ckZ
@housecor Claude code gave me such Friday energy yday; flat out refused to implement streaming of objects, kept fobbing me off with a loading spinner instead. Buddy, we all wanna go to the pub but we got things to do!
@housecor Company I work for have done it with reasonable quality and consistency for text outputs - itโs a lot of work, and I can imagine itโs even harder if youโre working with more complex outputs like data, interconnected systems, hardware etc
@housecor@playwrightweb@Cypress_io One watch-out with 1; if sub-components of the page can fail due to a partial API response, you might want to assert their presence to ensure patchy data doesnโt drop features that fail gracefully
@GeorgeMayer Iโm in a similar position - usually I work with established design systems and have found tools like Vanilla Extract fit better with building out reusable components that are synced with figma tokens
@mattpocockuk VERY interesting, so Iโve been lowercasing my zod schemas needlessly all this time ๐คฆโโ๏ธ
Feels wrong for them to match, but I can imagine this is great for consistency once youโre used to it
@mattpocockuk I find it super helpful for type hints on complex, multi-variate component styles, e.g:
<Button className="${button({ color: 'accent', size: 'large', rounded: true })}">
For this, @markdalgleish's Vanilla Extract and the Recipes package are great ๐
https://t.co/WZujqE768S
@GeorgeMayer This โ๏ธ
Sounds mean spirited, but totally agree on junior dev content; this platform and others is drowning in it, meanwhile content that pro devs need is buried
I'm only one module in and I'm absolutely loving @JoshWComeau's CSS course ๐
Such a thorough approach to teaching, not shying away from but embracing the messiness of CSS. Best Black Friday money spent by far
For UI developers, accessibility can be a daunting topic to get into; official docs are super dry to read, and debugging tools can throw up many intimidating errors
So, where do you start? Here are 3 recommended resources for building knowledge in bite-sized chunks ๐
Building a component library, or vetting OS options for accessibility? Then @heydonworks' excellent guide to creating inclusive components is a must-read
https://t.co/n5chi5QmWJ
Need to know how to build accessible table pagination, skip links, navigation, and other complex UI patterns?
Look no further than the excellent @weba11ymatters by @shadeed9
https://t.co/Ihd3dwIYpV