Sitemap

Principles in Acceleration of Software Development

4 min readJul 15, 2018

--

Why it’s important but hard to keep moving faster.

Move fast. New features comes to the hands of users earlier and they would be happy if these are what they wanted. Having users feedbacks earlier reinforces product-market fit calibration. Eventually that’s key to make any project successful. But there’s one caution here. We should be aware of the second order of it: moving faster over time.

Our tendency to sacrifice the long-term efficiency for near-term one can be explained for an obvious reason: measuring how fast we currently are is substantially easier than how fast we will be in the future. We prefer certain choice and pick the former over the second. It accumulates over time and one day we realize we move as slow as a turtle does.

Also, as company scales, the complexity in organization, communication, product, and engineering increases, which disproportionate with the speed of development. Any system can be exposed to getting slowed down by the bottleneck.

How can we avoid moving slower in the future? The key is to set a principle and apply it as a set of strategies and tactics in whole levels. Here, let’s go over the principles of acceleration of software development.

Generalize a set of resolutions: the principles

Why principles? Because it gives greater extensibility to the one’s choices in different contexts in software development. It sets a paramount where anyone can construct a variety of concrete strategy, tactic, and practices according to a unique situation that one has.

  1. Anticipate Unknown of Unknown
  2. Take compound interest into account
  3. Make components moduled
  4. Transparentise information
  5. Automate process

1. Anticipate Unknown of Unknown

The first principle should be something so fundamental that it constructs other principles. Anticipate unknown of unknown. What is unknown of unknown? Well, it’s easy to know that you are reading this sentence (known of known). It’s easy to know you don’t know what the author is thinking right now (known of unknown). It’s hard to know we don’t know what we don’t know (unknown of unknown). Unknown of unknown means something completely outside of our consciousness. It’s a total surprise when we know unknown.

Get Taka Ishikawa’s stories in your inbox

Join Medium for free to get updates from this writer.

We should always be aware that unknown of unknown exists and it requires unbounded time to notice known of unknown and turn it into known of known. We need to proactively expand the scope of expectation to capture the unknown of unknown as early as possible. This entails the necessity of consistent prospection, inspection, and retrospection. At any stage of development, we want to integrate the above among the whole team.

2. Take compound interest into account

The second principle is a subset of the first principle relates to the linearity in the mode of human cognition on any time scale. We tend to believe the rate of change in any observation is constant and dismiss the factors that have compound interests as its attributes.

Identifying these features and taking according actions are key to accelerate the development. As an instance, writing tests has a substantial compound interest. In the face of deciding whether we should write tests, firstly we should be aware that it compounds. Then try estimating its compound rate. Although it depends on the context, the larger the project is, the more significant compound rate will be. And needless to say, the effect reinforces over time.

3. Make components moduled

The third principle is a more practical interpretation of the above. Over time, the complexity of any system increases. This introduces the need of understanding the interaction between the components of the system. The number of the component and its size would impact the speed of development. Memory size of human brain is limited. The more components the system have, the harder developers to understand the interactions between them. The larger the size of a component is, the more restrictive the development will be.

At any layer of development, architecture, design, implementation, quality assurance, and deployment, apply and practice modularity. Module serves a specific functionality as a unit of system, hides internal details from outside of the world, provides an interface to let others to consume it’s functions, and reduces interdependency between components. Thus it improves understandability of the interaction and flexibility of the feature development in the system in long-term.

4. Transparentise information

The forth principle scopes out to the environment of development. Software development happens in a team environment in majority of the cases. No sufficient information is shared among the team leads to have more unknowns of unknown. The team will stumble upon the unexpected surprises more often and suffers the slower development.

Transparency is a key for a team to coordinate efficiently by understanding the updated context of the project. Frequent, concise, clear, and open communication should be consistently encouraged throughout the organization.

5. Automate procecss

The fifth principle addresses a side effect of practicing the above principles, which may decreases the current velocity of the development by adding extra work. Having rigorous meta analysis, writing tests, sharing status among the team, all takes time. At some point, it may become too repetitive and redundant.

Make repetitive tasks executable by a single command or scheduled as much as possible. From infrastructure level to coding level, lots of automation tasks are available but dismissed.

Conclusion

It is not trivial task to retain the velocity of software development. With that, accelerating the software development is far harder to achieve. However, it’s addressable. It’s useful to understanding the nature of cognitive limitation of human minds and construct the set of principles to apply strategy and tactics.

The benefit of incorporating ideas as a set of principles is the density and generality. It’s easy to retain in memory and apply to different set of contexts. A few entails many. The simple one adapt.

Hope you enjoyed.

--

--