Monthly Archives: March 2019

Think of Application Design like a big city

Countless times I have heard others few an application as a complete and well thought out. When they have looked at the code, they do so with assumption that every single line is intentional and in the proper place. I have had conversations trying to explain the design and well it works, and then have the conversation deviate(and justify) why a certain piece of code contradicts the design

Application and their design are more akin to big cities. Cities(except maybe Dubai) are not built from scratch to become a city. Let’s look at the following:


While I am not questioning the design of git itself(no reason to…yet), this is a great example of code that is layered over time. These first few lines span over a decade. In terms of a city, this file is an ancient district with a lot of history. There are lines that were added years ago that still exists. There are new lines that were added for various reasons recently. I bet there were lines removed for certain reasons a while back. Regardless, there is a story here to tell, just as there is to any big city.

The git code itself is rich with history just as much, if not more. Some code is old and untouched, and some are newly created. While the goal of it all is to function, not all of it would be done the same it it was built today.

Treat designs after the fact like city ordinances

Applications will invariably change over time the longer it is up and running. Whether the business is asking for a new feature, libraries need upgrading, APIs changing, there will be times design changes. As with every need, it is not feasible to re-design the application for every change.

Think of application “re-designs” as city ordinances. As a city grows, as time passes, as new needs arise or technology evolve…cities will pass new laws or ordinances. The goal, or at least they advertise it as such, is to help improve the quality and lives of everyone. When ordinances are passed, they usually include a grand father clause.

When it comes to your application, you don’t need to re-write everything immediately. When deciding to go in the new direction, you should do the following:

  • Implement the new design in the section(s) you are working
  • Pay close attention to PRs to make if the are using the new design
  • When the sections of the old design become manageable, work to remove the rest.

Example: A quick fix becomes a standard

Imagine in an application, I need to pull information from a new endpoint. Simple enough. I might not think much of it, I would add the following to the code:

response = requests.get('')
my_needed_info = response.json()['info']['status']

Over time, I or others find they need the same information. So we copy those simple lines over to where we need it. Simple. No problems, and we have more important things to do to care about design.

Just as with any big city, this thing that “just worked” starts to break down and cause problems. The API is unstable at the scale we use it at. We have this code in many places. Handling API failures, and our growing need to be stable, requires us to now address this.

Example: Solving the problem as an “ordinance”

Sometimes, it may be quicker to “change all the things!” Sometimes due to other needs and scope, it is better to go slow. So in the example above, lets say this code was spread out the entire application and you don’t have time to fix it. As with and ordinance, change what you need as you go forward. What I would do is first create an easy to use function which solves the problem:

def safe_info():
retry_count = 3
while retry_count > 0:
retry_count -= 1
response = requests.get('')
return response.json()['info']['status']
except requests.RequestException:
if not retry_count:

Safe enough. This function will retry automatically, still throw an exception if it continues to fail. Also return exactly what we need. Going forward, we should use this.

Now as we write code, we use this function. As we review PRs, we make sure others are using this over the old code. As you make changes around the old sections, change this code. New and junior employees may not be aware, so make sure they don’t use the old way. This is would be your responsibility as the lead developer.

Eventually, take care of the rest as you have time and the pending work becomes manageable.

In the end: Balance the needs

You don’t HAVE to follow this habit. Sometimes it would be beneficial to do it all in one fell swoop. The main thing to consider: Is your process the right one or is your process one where others may question your future decisions?

If people will question your quality, doing it all at once may be the answer. If people are questioning your time/effort, take a slower approach. The goal is to be able to keep designing and redesigning. Try to keep the business agree with your best judgement and not judge your previous efforts.


Wanted to get a website to talk about Software Development. Things are coming…

These things are a place to put my inside voices. The things I hold back from most people. Feel free to judge how ever. Curious how far this will take me…