DEV Community

Cover image for Quality Over Velocity

Posted on

Quality Over Velocity

Without excluding the IT business, it is highly likely that all professions today involve some level of stress. On top of having to meet deadlines, dealing with last-minute changes in requirements, and dealing with people, software engineers have to labor in front of a computer for 8+ hours, which adds to the stress.

One of the pillars of agile software development is self-organization, which is a must-have skill for a software engineer to be able to handle day-to-day tasks, especially when working in teams, allowing everyone to comprehend the larger context of the project, making decision-making more faster and easier.


You are free to choose, but you are not free to alter the consequences of your decisions.”
― Ezra Taft Benson

We make numerous judgments every day. We frequently make these judgments on our own, without any formal procedure in place, and often without even realizing it.
Few developers have a system in place for understanding context and repercussions and making better decisions.
Decisions might be simple or complex by nature. The more complicated ones are more difficult to create. The more difficult it is to make a decision, the more willpower it will take.


This week was not easy for me and my teammate ManipleKwizera on the backend, since sending an email to a registered user proved to be a difficult process for the three days we spent trying to fix it.
We were able to repair it thanks to our beloved senior developer KagaboFaustin by twiddling a handful of our laptop options.

success-shaking hands
To summarize, a smart software developer should prioritize quality over speed; providing a good working product to the world should be the primary goal, rather than releasing one that is buggy.

Top comments (0)