<p>One thing I&#39;ve started to do when I&#39;m actively developing a website or application is keep the dev tools open docked to the side. I do this for two reasons.</p>
<h2 id="disabling-cache">Disabling Cache</h2>
<p>First, dev tools have a nice setting that allows you to disable the cache when the dev tools are open. If you open up your browser dev tools, under <code>Preferences &gt; Network</code> there&#39;s an option to disable the cache</p>
<p><PostImage
    src="/images/posts/2022-12-08-developing-with-dev-tools-open/screenshot1.png"
    alt="A screen shot of the preferences screen in Chrome dev tools"
    width={622}
    height={457}
    centered
    shadowed
    priority
/></p>
<p>This just helps make sure I&#39;m not debugging old Javascript or CSS. It doesn&#39;t happen too often, but can save some hassle.</p>
<h2 id="catching-errors">Catching Errors</h2>
<p>The second, and probably more important reason is to catch errors and warnings early. While interacting with what I&#39;m working on, any errors, warnings or other messages of note will often pop up in the JavaScript Console in the dev tools. Keeping the console open and docked to the side allows me to easily see what might be happening that I might not notice. It definitely can cut down debugging later.</p>
<p><PostImage
    src="/images/posts/2022-12-08-developing-with-dev-tools-open/screenshot2.jpg"
    alt="A screen shot of the the developer console open alongside my blog"
    width={1200}
    height={765}
    centered
    shadowed
/></p>
<p>And besides, with larger 4k and ultra wide monitors, I have the screen real estate.</p>


RSS Feeds

All Posts

Blog Posts

Reading Logs

Photo Blog

Colors

Font

Posts Tagged
Dev Tips

Developing with Dev Tools Open