Umar Hansa
umaar.com · Personal blog · on HN since 2015
Umar Hansa, a web developer on Chrome DevTools, writes tips and tutorials on browser developer tools and web development.
What HN saysCommenters link its DevTools tips pages, such as inline breakpoints, the Changes panel, and CPU throttling, to explain how those features work.
25HN people shared it
14linked it in comments
35stories submitted
132story points
3 years agolast shared
2015people per year2026
Most-shared posts
- 1The largest collection of animated Chrome DevTools tips8 people · 24 points · first shared 2015 · 1 comments on HN
- 2Puppeteer Recorder Feature in Chrome DevTools3 people · 3 points · first shared 2020 · discussion on HN
- 3Chrome: CSS and JavaScript Code Diffs with the Changes Panel3 people · 2 points · first shared 2017 · discussion on HN
- 4Things I learnt after 5 years at Shazam2 people · 4 points · first shared 2020 · discussion on HN
- 5Chrome DevTools: Refactor Your Stylesheets with the CSS Overview Panel2 people · 3 points · first shared 2020 · discussion on HN
- 6129 inline breakpoints2 people · first shared 2019
- 7Conditional JavaScript: Only download when it is appropriate1 people · 75 points · first shared 2020 · 48 comments on HN
- 8Live edit already-running Node.js code with hotswapping in Chrome DevTools1 people · 3 points · first shared 2016 · discussion on HN
- 9Chrome Canary gets an integrated Node.js debugger1 people · 2 points · first shared 2017 · discussion on HN
- 10Using Cloud Vision & Speech Synthesis APIs for Identifying Images on the Web1 people · 2 points · first shared 2016 · discussion on HN
- 11The Spreadsheet I Use to Compare Job Offers1 people · 2 points · first shared 2020 · discussion on HN
- 12Replay how the browser drew your webpage with the Paint Profiler in DevTools1 people · 2 points · first shared 2016 · discussion on HN
- 13Using Chrome DevTools to Debug Node.js Code1 people · 2 points · first shared 2015 · discussion on HN
- 14Data Visualisation with 1B Shazam Music Recognitions1 people · 1 points · first shared 2020 · discussion on HN
- 15My code exercises I submitted to get job interviews at tech companies1 people · 1 points · first shared 2020 · discussion on HN
What HN people wrote when they linked it
umaar · 2020-11-14
I've put lots of little coding solutions, links to my videos and articles on my website [1], and have sent this to potential employers in the past for web dev jobs. It definitely helped accelerate things, and on 3 occasions I didn't have to do their take home test since my GitHub was enough. I don't have an up to date CV and my LinkedIn is empty.
I've also heard of potential colleagues giving positive sentiment to the hiring manager/boss: "oh that guy, I'm subscribed to his mailing list, he's good".
I've received a good number of offers, and one thing I've started to wonder: are interviewers thinking I'm a great dev because all these little side projects supposedly make me a better web developer? Or are they hoping I'll increase exposure to their brand since I already do talks and write articles?
I hope it's not the former, all the time I spend writing, doing talks etc. it's taking time away (with the exception of software-based side projects) from me learning about the art of software engineering.
[1] https://umaar.com
kaycebasques · 2019-05-17
We (Chrome DevTools) have had inline breakpoints since at least January 2017: https://umaar.com/dev-tips/129-inline-breakpoints/
The human-friendly variable mapping is very interesting, though. We'd love feedback on how well it works out in the wild.
mxstbr · 2018-11-15
It's also pretty stuttery on my 2017 MBP in Chrome, for what it's worth.
Maybe try developing with CPU throttling activated in the Chrome DevTools? https://umaar.com/dev-tips/88-cpu-throttling/
paulirish · 2018-08-01
> since devtools doesn't keep a log of all your changes
It does now, although you'll have to find it. :) Flavio mentioned this below, but peek at the new Changes panel: https://umaar.com/dev-tips/137-changes-panel/
And while it does track changes to all resources and inspector-stylesheet, any changes made to inline styles aren't captured yet.
That aside, styleurl looks great and clearly improves the collaboration workflow.
flaviocopes · 2018-08-01
This is amazing. I just tried editing a minified CSS, while the Chrome Dev Tools have a way to show the changes (https://umaar.com/dev-tips/137-changes-panel/) the result I get is the whole minified line.
This extension just tells me what things changed, so I can put them in another CSS file without editing the original minified CSS.
Thank you!
timrichard · 2018-06-14
If you use Chrome DevTools, there are a few resources that I think are really useful for getting the most out of them and making the workflow a bit easier.
Paul Irish has a great roundup here :
https://youtu.be/HF1luRD4Qmk
Umar Hansa has a great mailing list for DevTools tips, and there are some good ones to browse here :
https://umaar.com/dev-tips/
guiambros · 2017-07-12
Thanks for sharing, and for creating it! Great work. The tip on how to capture full sized screenshots without a browser extension[1] was already worth the visit.
[1] https://umaar.com/dev-tips/151-screenshot-capture/
niedzielski · 2023-04-27
I use source-map-explorer to see what's inside. Lighthouse Treemap provides a similar view.
[source-map-explorer]: https://github.com/danvk/source-map-explorer
[Lighthouse Treemap]: https://umaar.com/dev-tips/270-devtools-lighthouse-treemap/
jimmont · 2022-05-22
possibly related:
* https://umaar.com/dev-tips/241-puppeteer-recorder/
* https://umaar.com/dev-tips/248-recorder-playback/
* https://developer.chrome.com/docs/devtools/recorder/
I use Deno and its standard library for testing with Puppeteer.
I've found unit tests overrated and scenarios underrated (ie testing pyramid).
ludwigvan · 2019-05-19
Tacking a custom header to the response is a nice trick!
Could be particularly useful for GraphQL apps where every response is a big opaque answer from `/api/graphql`: Add the GraphQL operation name to the response header.
This will also help with Chrome Devtools where you can add custom headers to the Network tab, otherwise you just see tons of POST reqs to `/api/graphql`: https://umaar.com/dev-tips/115-manage-network-response-headers/
magicalist · 2019-05-17
Those have worked for a while now? Like https://umaar.com/dev-tips/129-inline-breakpoints/
The bigger issue is when local variables aren't captured by the context when paused in chrome. I'm curious how the Firefox devtools handle that.
jefkoslowski · 2016-03-02
pit2 · 2018-04-09
Here you have +100 more: https://umaar.com/dev-tips/
sanzen · 2017-04-21
Just the links from…