Jecelyn Yeen

@jec.fish

Principal Software Engineer. Ex-Googler. 👩‍💻🇲🇾🤿

Just booked my travel to @jsnation.gitnation.org on 12th June in Amsterdam. @devnook.bsky.social and I will be talking on all the improvements to Chrome DevTools! You can join remote with below invite: gitnation.com/badges/jsnat... Or better yet, come and join in person! Great conf and great city!

Check out my badge & claim your free JSNation 2025 remote ticket!

Join 10k engineers worldwide at JSNation 2025 and meet 50 top speakers at June 12 - 16, 2025

gitnation.com

[1/3] Today marks my last day at Google & in Germany. I’m heading back to Malaysia! 🇲🇾 It’s been an incredible 5 years working on #ChromeDevTools and browser automation with the best team ever – the amazing Chrome team! 💙 One of the promises I made to myself when joining was to bring...

So many good #webperf improvements in Chrome 134 DevTools: - Calibrated CPU throttling - field date in perf trace - third-party highlighting and dimming - forced reflow insight - DOM size insight - Lighter console.timestamps for Extensibility API Rolling out from today!!!

Jecelyn Yeen@jec.fish · last yr.

🎉 Chrome 134 is here! What's new in #ChromeDevTools 🔐 New: Privacy and security panel 📈 Calibrated CPU throttling for #webperf analysis 🥇 Dim 3rd-party scripts in performance traces ....and more! Update Chrome and try them out! developer.chrome.com/blog/new-in-...

If you're using Speculation Rules there's a small bug in Chrome 133 (just rolling out now) where DevTools + Local Overrides causes prerenders to crash 😢 This only happens with DevTools open and when Local Overrides are enabled so shouldn't affect most of your users—but annoying for us developers!

Can we just hire someone to rethink browser devtools from scratch already? It's ridiculous that so much of their features are hidden away in nested menus that most developers will never even see.

Bild