davidluhr.bsky.social
Design engineer working on accessible design and code at Buffer. Creator of https://youtube.com/@buildux
64 posts
166 followers
41 following
Regular Contributor
Active Commenter
comment in response to
post
This is the core tradeoff of using a custom rendering and layout engine in Figma vs. building a tool directly with the web: it's going to be extremely difficult and costly to partially replicate features that entire browser teams spend years on, and there will always be a substantial lag.
comment in response to
post
Caldigit TS4
comment in response to
post
JSDoc with TypeScript only as a type checker is the right balance for me. No build step means even more time to wrestle with types.
comment in response to
post
This is a very thoughtful move. Removing barriers, especially for beginner-oriented content, really benefits the wider industry. For more advanced content, charging feels fair, as it's basically scaled consulting. But, I've always found providing all my content for free brings good business.
comment in response to
post
Thank you for the kind words! Glad you found it useful.
comment in response to
post
I'll definitely consider writing more about this. I put together a larger summary on LinkedIn so I can easily elaborate further as a full blog post.
comment in response to
post
This comes at quite a cost: not only do I lose my most productive hours, but meetings, especially information-sharing meetings, leave me feeling quite drained.
In contrast, pairing is energizing, and I've already had much more productive mornings with deep work.
comment in response to
post
It's only the second day of the experiment, but it's already made a big improvement in my work. I personally do my best work between 8 AM and 12 PM, but most of our recurring meetings fall in this window (when there's the most timezone overlap).
comment in response to
post
Happy to contribute if there's interest. Lately I've been focused on design engineering with fluid design. Always happy to cover accessibility or TDD topics as well.
comment in response to
post
Came together great! The definitely achieved the publication look and feel.
One thing I caught: the focus indicators on `.button` elements should be inverted on both light and dark modes. It isn't visible currently. Everything else is solid.
comment in response to
post
If you have any feedback on Buffer's Bluesky support, let me know! I joined Buffer in the spring this year and we're actively improving this new connection.
comment in response to
post
This is best achieved with negative margins using the % unit, which is relative to the parent. We fine tune the overlap amount that scales proportionally to the viewport and parent container.
We also set `pointer-events: none;` to prevent the image from blocking clicks.
comment in response to
post
Further down, we have feature sections with a grid layout and images that we want to overlap surrounding content.
These images need to proportionally overlap their containers as the screen (viewport) scales in size.
comment in response to
post
To achieve these, we use (negative) margins with `rem` for a fixed overlap amount.
We set a negative `margin-block-start` on the image, and match this amount with `margin-block-end` on the hero section. This allows us to control the overlap independent of the screen size.
comment in response to
post
Excited for this change. COTA's in full support so I hope it gets fully approved. From a trail work perspective, it doesn't seem to cause any additional work, so it's just getting the national forest rule changed.
comment in response to
post
- ShopTalk: shoptalkshow.com
- Design Details: designdetails.fm
- Radio Free XP: podcasts.apple.com/us/podcast/r...
- Dive Club (Deep Dives): www.dive.club/deep-dives
comment in response to
post
Same with design courses. If what we build doesn't work for people, what's the point?
comment in response to
post
These results are not surprising, given the training data from almost all websites having accessibility issues. One way to improve this is by writing unit tests that assert all needed accessibility details (semantics, ARIA attributes, user interaction, etc.), and even then it's not perfect.
comment in response to
post
There's a limit to how many tokens (characters) you can send as a prompt. Besides that, I always recommend writing small, focused unit tests with a single assertion each. It's best to only write tests for a single function, prompt AI to write that function, write tests for the next function, repeat.
comment in response to
post
There's also been a lot of propaganda that there's more job security in bigger companies. But there's just as much (if not more) volatility, as evidenced by all the massive layoffs.
comment in response to
post
Always impressed by HTML's backward and forward compatibility. The WorldWideWeb browser user experience has some really cool benefits. Having a new window for each page that is sized to the page's height allows you to arrange a whole "desktop" of pages for comparison. Somehow feels futuristic.