Debugging: You can't always get what you want

Debugging is a natural part of writing functional code. Code, like life, doesn't always work out the way we want it to. Debugging someone else's code can be even more challenging than writing your own code because other people will approach problems differently than you would. I have experienced moments of extreme irritation while attempting to solve bugs in a program; however, the more I write programs, the more I am learning to approach problems from different vantage points. I used to find debugging frustrating, but I now see it as an everyday process. It doesn't actually upset me like it used to. I just feel more motivated to resolve problems, and I have learned to step away and take breaks throughout the day. I am learning to develop confidence that I will eventually resolve the issue in the code. It's not a stressful thing for me anymore. It's what I do every day, and I enjoy the challenge.  

Debugging presents a challenge and an opportunity to learn. If I am having a difficult time, I have learned to do something else, like play my guitar or go on a walk. When I come back, answers are usually easier to come by. I enjoy debugging, but burnout is real. Sometimes, it's easier to solve the problem inside your head while you are not visually distracted by the actual code on the screen. I often resolve code problems when I am not actually looking at the code.

I like making things work and struggle with workaholic, obsessive tendencies. I always try to turn in my best work, and I would feel bad if I felt that someone else thought they could not rely on me. Compiling is necessary, but it's not the only requirement for a functional program. It would bother me if I knew that my code had bugs that I did not fix. I do my best to catch them.

I think a good O&M developer manages their stress and appreciates the details. It's actually harder to take apart someone else's program and fix it most of the time than just writing your own program from the ground up. This job is perfect for problem solvers and detail-oriented people that like to hyperfocus on solving a problem to completion.

Comments

Post a Comment

Popular posts from this blog

SalonAboutBeauty: Less Integration for Consistent Styling Across Components

Ensuring Consistent Variables Less provides several advantages for organizing CSS to ensure consistency across a website. The variables.less file defines reusable properties that allow a developer to easily communicate and maintain styles according to a style guide or theme.  The Less Web Development Cookbook describes properties in the variables.less file in relation to other programming languages: “Variables in Less are defined as the equivalent to statics in other programming languages. You assign a value to a variable once and use it everywhere in your code” (Meyghani & Jobsen, 2015, p. 50). It suggests that less allows a developer to set properties, such as colors and length, to variable names that retain their meaning and can be used everywhere in the code. Examples: @base-color: red, @primary: green.  By providing these definitions in a central location, developers create code consistency in all areas of the website. Creating an Organized File St...
Read more

Why “Human Error” Is Usually a System Design Problem

In complex systems, failure rarely comes from a single bad decision. It comes from problems that evolve slowly, cross boundaries, and remain unresolved while everyone involved behaves reasonably. Managing risk in these environments means managing trajectories, not just incidents. When ownership is divided strictly by role, function, or severity threshold, gaps are inevitable. Those gaps are where issues linger, age, and quietly accumulate risk, not because they were ignored, but because no one was responsible for carrying them forward end to end. This is common in healthcare, where delay is often necessary. A patient may require observation, referrals, or time to clarify diagnosis. The failure is not that care takes time; it is that the trajectory of care becomes fragmented. Each clinician escalates correctly within scope, yet no one owns the evolving picture across visits, domains, and decisions. The patient is evaluated repeatedly, reassured locally, and sent away without continuity ...
Read more

Challenges in Prosecuting Deep Web and Darknet Crimes: The Case of Ross Ulbricht and the Silk Road

  The deep web represents online information that is not easily accessible through search engines. Prosecuting crimes on the deep web is no more challenging than prosecuting crimes for any standard website because law enforcement can still track the user's location through a domain or IP address. Alternately, the darknet poses a challenge for law enforcement to address illicit activity because while the darknet is a web-based system, it is accessible only through the Tor protocol that encapsulates HTTP and HTTPS traffic, much like a VPN that hides a user’s location and identity. The Tor protocol, often called the Onion Router, contains methods for encrypting and routing traffic between peers. The purpose of the Tor protocol is to make web browsing anonymous by routing each request through multiple peers and altering encryption at various steps until the request reaches its destination. Subsequent requests may hop through different peers, making traffic appear random, unpredictable,...
Read more