If I want to create a feature for an existing app (or build one from scratch), I will often face code that is not working as it is supposed to □♂️, and here is when I will pull out the "debugging arsenal" to find out what's wrong with the code in order to keep moving forward in the development process.Ī special note: when a bug is introduced by ourselves More often than not, I feel debugging is not solving a particular issue affecting a customer, but the natural process inherent to the development of software. No matter what's the case, they all have something in common: we need to use tools to help us debug the app and find what's wrong with it. Sometimes, though, the bug might have been introduced by ourselves □♂️, and we can find it difficult to step in the shoes of our past selves in order to understand why we did what we did. When hunting for actual bugs in the code, we need to focus on tools and systematic processes to analyse the code in search of what's not working and accept the fact that the person that wrote the code may not be available to answer our questions. ![]() Or I can debug as part of the normal development process (most likely).I can debug to find the root cause of an actual bug.This is not the result of a poorly implemented code, but what I feel is the natural process in which I find myself involved daily: ![]() Since I started working as a software developer, I find myself spending the majority of the day debugging a big react app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |