Engineer Explains: ERROR handling strategies every developer must know

Milena Radivojević

We've asked experienced engineers to share how they would explain some tech terminology at three levels of experience - from junior developer to CTO.

Errors are unavoidable, but it’s ineffective error handling that can truly damage a business. If your app frequently crashes, users will lose confidence quicker than you can address the issues.

This makes it essential to prioritize how errors are managed during a program’s runtime.

Abiodun Olowode, Engineering Manager at Cleo, simplifies error handling for all levels—from entry-level developers to seasoned engineers and CTOs.

This video is a part of ShiftMag’s video series, Engineer Explains.

We’ve asked experienced engineers to share how they would explain some basic and some less basic tech terminology to different tech job titles or at three levels of experience — from junior developer to CTO.

More videos from the Engineer Explains series:

> subscribe shift-mag --latest

Sarcastic headline, but funny enough for engineers to sign up

Get curated content twice a month

* indicates required

Written by people, not robots - at least not yet. May or may not contain traces of sarcasm, but never spam. We value your privacy and if you subscribe, we will use your e-mail address just to send you our marketing newsletter. Check all the details in ShiftMag’s Privacy Notice