Irhose Apori
Centeradiv

Centeradiv

A bug's life

A bug's life

Subscribe to my newsletter and never miss my upcoming articles

Every programmer encounters bugs often. From forgetting the quotes around your first "hello world", to crashing a programme, bugs are always with us. So what is a bug? bug-tracking.png A bug is a flaw in a programme or code that results in unintended and usually frustrating results or outputs. A bug occurs when a programmer's ego is bruised because their code doesn't do what they want it to do. Bugs are pesky and tiring. Firstly, it takes skill and concentration to find them( the stress in finding them has been greatly reduced by error logs). And if or when a bug has been found, the journey to debugging is one that requires the bravest of hearts and most enduring of spirits. Many a programmer has lost enthusiasm in their quest for debugging their code, and the truly special ones have masterfully turned their bugs into features.

iris-hime-deviantart-com-bug-feature-by-design-changing-the-word-doesnt-change-36161075.png OK, chill, that's too deep, lol. The general idea though, is that bugs are inseparable from a programmer's workflow, So it's important to know how to deal with the mental pressure that they exert. Here's how I deal with it...

2.jpg I encounter bugs on a daily basis(mostly the peewee ones). And when I started learning to code, I actually liked bugs(yes, I really did) because they helped expand my scope of learning, and thereby introduced me into more challenging terrain which I always set out to conquer - sometimes successfully and other times "meh". As time went on(not much time), I began to dislike bugs thoroughly because, amongst other things, the mental strain usually led me to consider abandoning ship. Then I encountered a bug in my React code recently, that led me to a "resolution of balance". I resolved to develop a love-hate relationship with bugs because I realised that in the course of trying to debug my code, I had explored really interesting concepts, read a number of useful articles and documentation and changed my mode of approach to debugging as a whole. I learnt the importance of breaking problems into tiny understandable bits that can then be solved systematically. Yes! I learnt all that on one debugging journey. And no, I wasn't successful in debugging the code, lol. That's why my relationship with bugs is love-hate. On the one hand, it gives me a good clean shove into the unknown from where I always return more knowledgeable and more importantly, more experienced; and on the other hand, there's the uncertainty of whether or not I'll be able to find the solution to my problem. All in all, I've learnt to approach each problem - bug or not - with a mind to gaining value. Even at the cost of my ego. That way, I convert any impending frustration into motivation.

 
Share this