Member-only story
There Is No Benefit or Incentive for Developers to Create Quality Code on Software Projects
Speed is more important than quality on software projects
You get what you reward for. If you want ants to come, you put sugar on the floor. Charlie Munger
Creating software focuses on low quality, shortcuts and fast creation.Projects start quickly with short-term gains but quickly slow down and get slower Technical debt grows, making future development more complex and slower.
Technical debt creates complexity and long-term pain for the creation and maintenance of the software
Technical debt and low quality will slowly kill the project.
Why does poor quality code get created?
Software projects prioritize fast creation, not quality, and no developers are incentivized to create quality. The goal of software projects is meet the project deadline not create quality code.
Quality is a long-term benefit and most developers will be long gone when the technical debt trouble arise.
Fast software creation on a software project leads to a slow or failed finish.
Why is quality not a priority?
Creating software is misunderstood, quality is the fastest way to create software and smooth development with fewer error (Software development is a loser’s game).
Leadership (customers, project managers, etc) focus on meeting deadlines of an out of date plan. The common approaches are to take shortcuts, work longer and add more people.
Leadership focus on the symptoms and never the root cause. The root cause break's plan after plan. This pushes the project further back in smaller increments.
Quality is a long-term benefit and most people leading software projects only look at the short term. To achieve plans, the incentive and goals are to finish software faster and not on the quality.
Quickly creating low quality software moves the problems to later in the project, technical debt slows down all interactions with the…
