Step 26: Don’t Ignore that Error! ~ Pete Goodliffe

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

690

Abstract

ages to build up the suspense of a story in such a way that we absolutely want to know what happens on the next page.</p><p id="8ce1">What is important for novelists is vital for bloggers. If readers don’t finish reading the article, it messes up the statistics and causes Google to classify the content as irrelevant.</p><p id="31a8">If you want to know how to captivate readers with your content, read my article <i>How To Write Page-Turner Content.</i></p><div id="3a6f" class="link-block"> <a href="https://readmedium.com/how-to-write-page-turner-content-505bbcf5cbe6"> <div> <div> <h2>How To Write Page-Turner Content</h2>

Options

 <div><h3>When it comes to how to write a novel that is a real page-turner, there are many books and blog articles that explain…</h3></div>
            <div><p>medium.com</p></div>
          </div>
          <div>
            <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/0*v3Bcux7yl_pM_oPr)"></div>
          </div>
        </div>
      </a>
    </div><p id="ac1c"><a href="https://readmedium.com/d855be749e6c?source=post_page-----834577ca2b4a----------------------"><b><i>René Junge</i></b></a><b><i> a published author writing on <a href="https://medium.com/illumination">ILLUMINATION</a>.</i></b></p></article></body>

Step 26: Don’t Ignore that Error! ~ Pete Goodliffe

This is the 26th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 25th Step, read it.

Small hole in a giant ship is enough to cause it to sink, if not repaired in time. In programming a small error unnoticed, will ultimately turn to code-debt, which might take away project to a disastrous release.

Too many a times, we ignore error. May be because, we had a time constraint or we didn’t thought much about it due to plain laziness.

What is Error in code?

Error, what error? It won’t be serious. Honestly. I can ignore it.

try {
    // ...do something...
}
catch (...) {} // ignore errors

Why we shouldn’t ignore error?

Not handling errors leads to:

Brittle code: Exciting and hard-to-find bugs.

Insecure code: Code might be open for exploitation from hackers.

Poor structure: Too many checks to prevent some potential errors

How to look for errors?

Powerful IDE now-days highlight or warn about potential error.

Lint tools, static code analysis tools like PMD, findBugs can tell us about arrays of error.

Memory analysis tool

TL;DR Don’t Ignore the Error. Go through it, you will either fix a potential bug or learn a new stuff.

References: