Stop rushing yourself
As software developers, many of our objectives revolve around kanban, we see how our tasks move from one place to another, causing us great pleasure and addiction when they appear as finished, and every time we want to move more and more cards as soon as possible, and to achieve that I am going to hurry! It makes sense right? If I do everything fast, I will finish the tasks in kanban fast. Please stop and think about what you said, things don’t work that way. This is one of the worst traps that software developers can fall into, and even worse, in our entire daily lives, It is a bad habit that we have learned indirectly from the course of our lives and that we must unlearn, both for a better professional and personal growth.
When we are looking for solutions to a problem in google, it is very common to want to find the answer without making any effort, we want to open the first link of StackOverflow, copy and paste the answer, and voila, we lived happily together ever after. Unfortunately, the reality is more complicated, and if we rush to find the answer what will happen is that we won’t t read well the solutions that we find on different websites, simply because what we need is not explicitly, so let’s visit more websites, but none has the solution (actually they had it, but we didn’t find It because we didn’t read well). then as the last alternative, we read the documentation, scrolling the page, hoping that in some bold subtitle there will be what we are looking for but we end up with noting. After a while we ask a more experienced developer for help, and he will probably read the documentation calmly, paying attention to every detail, and in a matter of minutes he will find the solution without having spent so much time browsing websites like we did, amazed, we asked him, how do you manage to find the solution so quickly, is this a sorcery of seniors? -No, It’s not, the answer was in the documentation.
Another situation which can affect us by rushing, is the cause of stress and mental fatigue, many people, including myself, do not like to give up, and we cannot leave any programming problem unsolved, for which we dedicate many hours, and even when we leave work, we continue to think how we can solve that problem, at this point, we are no longer doing anything productive, our mind is not able to think clearly due to great fatigue, so it is better to take a break, relax, clear our mind, and then continue working, it has happened to me that I cannot find the answer, and after a little break, just by looking at the code I know what is happening and I am able to find the solution quickly.
Even at the time of writing code, you can easily tell if the code author rushed with the task, many times it happens that when we program we think: I am going to finish this task either way and then I will focus on correcting aspects of clean code. The negative side is that when seeing the task ‘finished’ because it gives the correct result, we will be lazy to fix it, or the code ended up creating a big mess which is very difficult to correct because if you change something in the code everything stops working. This is why it is very important to take the time when performing a task, and do everything right from the beginning, if we don’t, we will end up with double work because, in addition to implementing the feature, we have to fix the code.
To conclude, rushing is not the best solution to finish our duties quickly, it can worsen our productivity, and can lead to embarrassing situations, do you want to ask a developer to read the documentation that you did not read well? I hope you said no, so better take your take the next time in your job and don’t rush yourself.
