{"id":22714241,"date":"2023-07-31T10:38:04","date_gmt":"2023-07-31T17:38:04","guid":{"rendered":"https:\/\/thenewstack.io\/?p=22714241"},"modified":"2023-07-31T10:38:04","modified_gmt":"2023-07-31T17:38:04","slug":"bad-code-stalls-developer-velocity","status":"publish","type":"post","link":"https:\/\/thenewstack.io\/bad-code-stalls-developer-velocity\/","title":{"rendered":"Bad Code Stalls Developer Velocity"},"content":{"rendered":"\n

Today’s software development teams are under pressure to move fast and deliver code on aggressive schedules. With increasing competition, software providers are rolling out more new features and products — more quickly than ever before to stay ahead of their rivals. As a result, deadlines are getting tighter. Meeting these deadlines is often the priority, even if it means that code quality suffers.<\/p>\n

Without standards for code quality and with mounting pressure to complete the project at hand, it can be easier to let bad code linger in the codebase for the sake of speed. But that approach is ultimately self-defeating. It slows down the entire development cycle while also hurting product quality and creating security issues.<\/p>\n

Bad Coding Is Slow Coding<\/strong><\/h2>\n
The speediness of poor coding is an illusion in the long run. When bad code gets overlooked, it creates technical debt that leads to lasting problems and ends up dragging down developer velocity. Remediating past coding errors is a cumbersome, time-consuming process. It’s much more difficult to fix errors from months or years ago than it is to correct them in real time. To diagnose why code isn’t working, you need context — you have to understand what that code’s purpose was to begin with. The older the code is, the harder it is to uncover that information. What if it was written by a developer who left the organization years ago?<\/p>\n
The technical debt from bad code means that developers are frequently interrupted. As developers create new code, they’re constantly forced to stop their work to mitigate flaws in existing code. This is also known as context switching — jumping between projects — in this case, writing new code and fixing old, flawed code. Context switching is highly inefficient.<\/p>\n\n
\n\t
\n\t\t
\n\t\t\t
\n\t \n\t\t\t\t\t $\"\"$ <\/span>\n\t <\/a>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t
\n\t\t\t
\n\t\t\t\t\nSonar equips developers and organizations to deliver quality, secure code fit for development and production, whether AI-generated or written by developers. Trusted by over 400,000 organizations globally to clean more than half a trillion lines of code, Sonar is integral to delivering software. Insight Partners is an investor in SonarSource and TNS.\n\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t
\n\t\t\t
\n\t\t\t\tLearn More
\n\t\t
\n\t\t\tThe latest from SonarSource\t\t<\/div>\n\t\t<\/div>\n\t\t