A debugging thought process

Bugs I’ve filed on browsers | Read the Tea Leaves

I think filing bugs on browsers is one of the most useful things a web developer can do.

Agreed!

In a Land Before Dev Tools | Amber’s Website

A great little history lesson from Amber—ah, Firebug!

Phil Nash and Jeremy Keith Save the Safari Video Playback Day

I love this example of paying it forward:

• Phil Nash wrote a post on his site that really helped me, so
• I wrote a post on my site, which helped Peter, so
• Peter wrote this post on his site, which showed up via webmention on my site, and now
• this post will help somebody else …who I hope will write about it.

Google AMP - A 70% drop in our conversion rate. - Rockstar Coders

Google hijacking and hosting your AMP pages (in order to pre-render them) is pretty terrible for user experience and security:

I’m trying to establish my company as a legitimate business that can be trusted by a stranger to build software for them. Having google.com reeks of a phishing scam or fly by night operation that couldn’t afford their own domain.

The Art of Debugging

I was just helping out with some debugging at work and it reminded me of this great talk/post by Remy:

1. Replicate: see the bug
2. Isolate: understand the bug
3. Eliminate: fix the bug