How to build code with Technical Excellence

by

Looking at the software industry as it stands, it would accurate to assume that most working in it don't know what technical excellence is; software maintainability is seemingly non-existent, and technical debt often rampant. If you look at the distribution of cost associated to a software project you will see that 80% of costs are accumulated after a project's initial release. This would mean that software maintainability is a crucial element of any sort of technical excellence.

But if you ask a developer what they are doing to increase their software's maintainability, you probably won't get the answer you're looking for.

This is because software maintainability is not often central to any computer science curriculum or professional development environment. It has not been until recently that the industry is beginning to see the value in writing maintainable code.

If you read through most our posts on the site you will see a trend when speaking about the consequences of technical debt. The more technical debt you have in your software the harder it is to keep your system running smoothly and the more difficult it is to make changes to it in order to keep up to customer and industry demands. Technical debt is directly at odds with software maintainability.

So how do you deal with this?

The author of this post boils it down to writing CLEAN code.

Cohesive

Loosely coupled

Encapsulated

Assertive

Non-redundant

This aren't the only factors you need to pay attention too when writing code, but they are the most recognizable and easiest to understand. Again, if you go through our previous posts you will see persistent mentions of these qualities: specifically encapsulating code so that problematic sections won't be tethered to the whole product and inhibit progress in the future. Ultimately, the name of the game is building software with high code quality standards so that you can always meet the needs of the user and adapt to future demands.

To read the full post visit here.

Filed in: Technical Debt
Get the Pulse Newsletter  Sign up for the latest Software Intelligence news Subscribe Now <>
Open source is part of almost every software capability we use today. At the  very least libraries, frameworks or databases that get used in mission critical  IT systems. In some cases entire systems being build on top of open source  foundations. Since we have been benchmarking IT software for years, we thought  we would set our sights on some of the most commonly used open source software  (OSS) projects. Software Intelligence Report <> Papers
In our 29-criteria evaluation of the static application security testing (SAST)  market, we identified the 10 most significant vendors — CAST, CA Veracode,  Checkmarx, IBM, Micro Focus, Parasoft, Rogue Wave Software, SiteLock,  SonarSource, and Synopsys — and researched, analyzed, and scored them. This  report shows how each measures up and helps security professionals make the  right choice. Forrester Wave: Static Application Security Testing, Q4 2017  Analyst Paper
This study by CAST reveals potential reasons for poor software quality that  puts businesses at risk, including clashes with management and little  understanding of system architecture. What Motivates Today’s Top Performing  Developers Survey
Load more reviews
Thank you for the review! Your review must be approved first
Rating
New code

You've already submitted a review for this item

|