January 11, 2021
0 min read

Software development principles you should know about

Software development principles you should know about.jpeg

What exactly are the principles of software development?

Software developers and engineers created or adapted several acronyms and idioms to help them stay focused. Some of these acronyms come from the fields of philosophy or science. Others engineers and project managers coined themselves to guide the software development process. Let’s take a close look at these principles, starting with the principles that developers adapted from other fields.

First off, let’s examine measure twice, cut once.

Measure twice, cut once

This principle originated sometime in the middle ages. Back then, the expression was, “mark seven times and cut once.” This is the version still used in Russia today. Regardless of how many times we measure, the principle remains the same: proper planning methods will yield the best results.  The literal meaning comes to us obviously.  If we have a piece of wood that needs cutting, it’s better to double-check our measurements so we don’t waste wood making mistakes. When applied to the world of software development, we use the term a little more broadly. When we measure twice and cut once in software development, we plan comprehensively, putting together the right team and mapping out our steps in detail. Developing within agile methodology we plan our sprints and prepare for testing.

Occam’s razor

Occam’s razor comes to us from an early medieval English Franciscan friar, William of Occam. The principle that William of Occam espoused was "entities should not be multiplied without necessity.” But what’s with the word “razor?” In philosophy, a razor allows us to eliminate unlikely answers to a problem.  Occam’s razor states that the simplest solution is usually the best solution. We should not try and apply complex answers when a straightforward answer will work as well or better. In software development, we use the principle of Occam’s razor to question adding complexity to a software solution. We can make code function as required by keeping it simple and easy to understand. Straightforward, clear code works better and proves easier to test.

KISS (keep it simple stupid)

This principle was coined in the US Navy in the 1960’s by Kelly Johnson. Johnson coined the acronym to describe how designers of aircraft should work. They should make their designs simple enough that an average mechanic with limited tools could repair the aircraft. KISS directs us to avoid unnecessary complexity, to design with simplicity as a goal. In software development we use the KISS principle to remind us to make our code easy for others to understand and navigate. Testing and debugging simple code will always be better than combing through byzantine structures to find errors. We must create code that shows simplicity and elegance, not code that shows off how dense and knotty our developers can write.

Now let’s take a look at principles created in the software development world

LOD (law of Demeter)

The law of Demeter guides developers to divide classes into independent entities. These entities should not connect with other entities unless they are closely related. The idea is that each class in code should communicate with related classes, but not with those they are not related to. In the original law, this meant “talk to your friends, don’t talk to strangers.” The law was first proposed by Ian Holland in 1987 while he was working at the Demeter Project. Demeter allows developers to keep systems organized and limits the possibility of bugs.

DRY (Don’t repeat yourself)

Andrew Hunt and Dave Thomas stated this principle in 1999 in their book The Pragmatic Programmer. "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system." At its core, DRY discourages engineers from repeating code in more than one place. This sort of repetition causes trouble when troubleshooting. 

A good example of DRY on a meta-level is HTML 5’s separation of HTML from CSS. Before HTML 5 CSS code would be embedded in the HTML itself, so every time a heading tag’s style would change, designers would have to comb through all the HTML to make changes. Often they would miss a tag or two, leading to messy designs and incoherent page layouts. When all the styling elements went into the CSS, designers had just one place to look to make the changes.

Avoid premature optimization

Donald Knuth played out this principle as a serious issue for programmers in the 1960’s. He wrote, “The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming.”  Developers need to make sure their code functions and proves useful before the team optimizes it. Otherwise, they will waste valuable time and resources on code that might not meet requirements.

YAGNI (You aren’t going to need it)

This principle guides developers to create the code that the team needs at the moment. They should not anticipate extra functions or try to code with a very broad agenda. Instead, the developers should create exactly what the software needs, extending functionality later as necessary.

Big Design Up Front (BDUF)

BDUF asks developers to plan thoroughly before coding. Typical for waterfall method software development, in agile we can also use the principle of BDUF. We can make sure we completely understand the requirements and the needs of the end-users before we begin coding.


Solid stands for: 

S  -   SRP (Single responsibility principle)

O -   OCP (Open closed principle)

L  -   LSP (Liskov substitution principle)

I   -   ISP (Interface segregation principle)

D -   DIP (Dependency inversion principle)

Let’s take a brief look at each element of SOLID:

SRP (Single responsibility principle)

SRP calls on developers to ensure that each element of code does one and only one thing. 

Our code should not act as a multi-tool, but rather as specialized tools meant for specific jobs. We should not use a hammer to change a pipe.

OCP (Open Closed principle)

OCP asks developers to finish sprints with the mindset that the code is open to expansion or extension but closed to modification. We do not want to re-invent the wheel with every iteration.

LSP (Liskov substitution principle)

The LSP principle states that code elements in a subclass should behave in the same manner as the elements in the superclass above them. Barbara Liskov described the principle in 1987.

ISP (Interface segregation principle)

ISP leads developers to code interfaces small enough that end users can focus on what they need, leaving out functionality that they don’t.

D -   DIP (Dependency inversion principle)

DIP encourages developers to focus on the interface level, not the implementation. Agile encourages DIP by asking for user stories. If we keep our eyes on what end-users and stakeholders require, we design simple, elegant solutions.

Here at Blocshop, we follow these software development principles to make solutions that work for our customers. If you’d like to see our implementation of these principles in action, please get in touch!

Learn more from our insights

Top 15 micro-SaaS ideas for your startup in 2023.png
December 06, 2021

Top 15 micro-SaaS ideas for your startup in 2022

What exactly do we mean by micro SaaS? Micro Saas solutions use a web browser or mobile app interface. Micro SaaS solutions usually come about through the effort of an individual or very small team. It aims to solve precise problems. Micro SaaS projects have small budgets and overhead. Customers use Micro SaaS solutions on a monthly or yearly subscription basis. Micro SaaS projects target a small niche of the consumer market.

Software engineer hourly rates in 2021 (based on experience and location).png
November 22, 2021

Software engineer hourly rates in 2021 (based on experience and location)

Region influences salary more than any other factor. Taxes rates, cost of living, and government benefit programs affect the rates software developers charge. Software developers in the USA  and Canada earn more than software developers in other countries.

The best programming languages for app development in 2022.png
November 15, 2021

The best programming languages for app development in 2022

Software developers usually have three main ways to create an app. They can choose to code a native app, a hybrid app or a progressive web app. Developers create native apps to function on one specific platform, usually either iOS or Android. They create these apps using Swift or Objective C for iOS. For Android they use C++, Kotlin or several other languages. 

Cross-platform mobile app development: Tools & frameworks for 2022.png
November 09, 2021

Cross-platform mobile app development: Tools & frameworks for 2022

The cross-platform development project aims to create apps compatible with several operating systems. Cross-platform apps work on iOS, Android, and Windows. Cross-platform apps look and feel like apps developed specifically for the operating system.

App development cost breakdown in 2022.png
November 08, 2021

App development cost breakdown in 2022

Your business needs an app, but you aren’t sure about the cost of creating an app. Without some figures, you can’t even begin to estimate the potential budget, so let’s get you sorted with the information you need to make your app a reality.

November 04, 2021

Web app development: a detailed guide

The best web apps give a responsive and engaging user experience through a browser instead of a single application. Think of web app development as a super-charged website. Web apps have many features of mobile apps coded for iOS or Android without the need to code for specific platforms. Developers create web apps using HTML, javascript, Python and CSS.

15 useful web app development tools for 2021.png
October 29, 2021

15 useful web app development tools for 2022

Web development vs app development: Choose the best for your business.png
October 19, 2021

Web development vs app development: Choose the best for your business

Outsource web development in 2021 and beyond: benefits & tips.png
October 15, 2021

Outsource web development in 2021 and beyond: benefits & tips

8 IT outsourcing trends in 2022.png
October 11, 2021

8 IT outsourcing trends in 2022

More and more firms choose to outsource their IT operations and functions. IT outsourcing grows each year. The Gartner report announced that firms spent $3.8 billion dollars on IT outsourcing in 2019. They expect that the trend will continue. Companies aiming for digital transformation need partners and tools. They need tools that they cannot build in-house with speed and accuracy. 

In-house development vs outsourcing software development.png
October 01, 2021

In-house development vs outsourcing software development

Every business starting software development must ask themselves what will serve them better, in-house or outsourcing? There is not a simple answer to the question. Making the choice to develop in-house or to outsource will have long-term consequences.

16 Software development project ideas.png
September 17, 2021

16 Software development project ideas

Every startup needs a great idea. Something unique and compelling. Startup businesses succeed when they find a customer need that they can fulfill. Startup businesses and independent software developers constantly search for just such needs.

Software development budget estimation.png
September 16, 2021

Software development budget estimation

An unlimited budget would make many teams very happy. But that approach has pitfalls. If the team works without much oversight or customer input, they may waste money. They might create features that the customers won’t use.

What are the differences between Agile and Waterfall?.png
September 07, 2021

What are the differences between Agile and Waterfall?

These days, most software development teams choose Agile methodology to organize their work. The Agile vs. Waterfall debate still rages, though. Many people question whether Agile works better than Waterfall in all circumstances. Does Agile deliver great ROI? Does Agile help teams work faster? Let’s take a close look at both Agile and Waterfall. We will examine the merits and drawbacks of each approach.

September 06, 2021

Converting Story Points to Hours: Why Doesn't It Work?

In traditional software development, teams would describe the amount of work they had in hours. But Agile software development teams have a better way. Agile teams use Story Points to estimate the work they have ahead of them. Let’s take a closer look at Story Points and hours, and examine the benefits of Story Points.

Scrum vs. Extreme Programming (XP): What's the difference?.png
September 02, 2021

Scrum vs. Extreme Programming (XP): What's the difference?

We've covered the Software Development Life Cycle (SDLC) and the Agile development framework. Now it's time to look at different methodologies and approaches to their implementation. There are several, but we'll focus in this article on just two of them, Scrum and Extreme Programming (XP). We'll look at the differences between them and how they can even be used together for even better results.

The Scrum Sprint cycle explained.png
September 01, 2021

The Scrum Sprint cycle explained

Agile Scrum teams break down large development projects into small bursts of activity, called Sprints. A Sprint in Agile is a short, time-boxed period where a software development team completes work. They choose which items and fixes they will tackle in Sprint Planning Meetings. The Sprint cycle sits at the very center of Agile methodology. 

Use Cases vs. User Stories: relationships and differences.png
August 12, 2021

Use Cases vs. User Stories: relationships and differences

Product Backlog prioritization techniques & tips.png
July 27, 2021

Product Backlog prioritization techniques & tips

Software development project management guide.jpeg
July 26, 2021

Software development project management guide