Twitter | Search | |
Addy Osmani
Engineering Manager working on • Husband & Dad • Make the web fast ⚡• Lead for speed
21,971
Tweets
1,805
Following
211,368
Followers
Tweets
Addy Osmani 16h
Replying to @usergenic
np, Brendan!
Reply Retweet Like
Addy Osmani 21h
Replying to @jaffreyjoy @John_Papa
Just me and a lot of fidgeting :) It does help when folks like John put together awesome extensions worth highlighting!
Reply Retweet Like
Addy Osmani 22h
Replying to @gauntface
Some might even say...a totally tooling tip ;)
Reply Retweet Like
Addy Osmani 23h
Replying to @sebastianmeier
I've used the settings-based approach before and found it more cumbersome than using Peacock. Personal view though! it might still be a better fit for many.
Reply Retweet Like
Addy Osmani Sep 18
Great work on this, John!
Reply Retweet Like
Addy Osmani Sep 17
Peacock for VS Code is *awesome*: ~ quickly change the color of each workspace. Makes it easier to identify different projects.
Reply Retweet Like
Addy Osmani Sep 17
Replying to @rnebhwani @Dieulot
I'd say our React + webpack specific solution (for Quicklink) should be ready in about ~ 2 weeks. Would be super helpful to have some early feedback on it.
Reply Retweet Like
Addy Osmani Sep 14
Perhaps you're thinking of ? :)
Reply Retweet Like
Addy Osmani retweeted
fantastic ms. Sep 12
⚡️I wrote about a way to leverage Actions to automatically optimize raster images on every pull request, in any repository. This means you’ll never ship an unoptimised image to production, even when using GitHub UI to make changes.
Reply Retweet Like
Addy Osmani Sep 13
Replying to @JonthanFielding
Thanks for continuing to work on this! Definitely want to circle back with feedback. I'm a little snowed under with perf review season at G for another week, but...soon! :)
Reply Retweet Like
Addy Osmani Sep 11
Thank you, Weston!
Reply Retweet Like
Addy Osmani retweeted
Firefox DevTools Sep 11
🌅 Now in Beta: Inactive CSS! We show you which CSS properties aren’t affecting the selected element and why. (Has this saved you time already? We love hearing from you and seeing screenshots!) —
Reply Retweet Like
Addy Osmani Sep 11
Could you file a bug report at with as much detail about the issue observed?
Reply Retweet Like
Addy Osmani Sep 11
cc could you help determine if there's a reproducible bug in WP here? It'd be very helpful for following up with a crbug if it's an issue.
Reply Retweet Like
Addy Osmani Sep 10
Replying to @tim_nolet
Ohhh. Now I've got that working. It initially wasn't clear I needed to click down/select a region. Once done screenshotting worked just as expected and the final code included await page.screenshot(). Thanks, Tim!
Reply Retweet Like
Addy Osmani Sep 10
Replying to @_nikchavan
I haven't used Puppetry before but see a few folks suggesting it. How have you found using it so far?
Reply Retweet Like
Addy Osmani Sep 10
Replying to @_ElleOhElle_
You have the best GIFs.
Reply Retweet Like
Addy Osmani Sep 10
+1. Big congrats, Amal!
Reply Retweet Like
Addy Osmani Sep 10
Replying to @davert
Can you expand on why? Many integration tests I've written had to start with a user flow reproduced with interaction simulation. Tools like this aren't going to write 100% of a test (ofc), but do accelerate authoring the MVP.
Reply Retweet Like
Addy Osmani Sep 10
Replying to @tim_nolet
Thanks, Tim! Looking fwd to more Recorder awesomeness. When I tried the screenshot option last, I was unsure if it should updated the generated script to include this step (did not appear to). Could you share what it's meant to do? :)
Reply Retweet Like