<story><title>Debugging tricks in the browser</title><url>https://alan.norbauer.com/articles/browser-debugging-tricks</url></story><parent_chain></parent_chain><comment><author>lewisjoe</author><text>The debugging tools built within the browsers have come a long way in the last couple of decades. I&amp;#x27;m a JS veteran and I&amp;#x27;m deeply grateful to all the people putting in such efforts to make debugging code in the browser so intuitive.&lt;p&gt;Whenever I go to a different zone of development, like backend or a different language, I miss this ecosystem of debugging tools that modern browsers have by default.</text></comment>
<story><title>Debugging tricks in the browser</title><url>https://alan.norbauer.com/articles/browser-debugging-tricks</url></story><parent_chain></parent_chain><comment><author>Jerrrry</author><text>&amp;gt;&amp;gt;setTimeout(function() { debugger; }, 5000);&lt;p&gt;This is clever; after all, the only way to beat the recursive turtle stack of chrome debuggers debugging themselves is with the debugger statement.&lt;p&gt;sam.pl, of the infamous myspace Sammy worm, used debugging gotcha&amp;#x27;s to prevent visitors from de-mystifying his obfuscated html homepage.</text></comment>