What Software Development can learn from Biological Evolution?

from the first sight biological evolution looks too unpredictable to have any value for the constrained software development. we just don't have time, money and resources for these wild experiment, unlimited trials and errors. it really seems that nature could learn from us how to make things fast and effectively.

however, there are some principles that helped evolution to come up with amazing and efficient designs that made life flourishing on the earth. this post will explore what software development could learn from biological evolution. see my previous post for the review of evolution concepts and mechanisms and how they could be applied to software development.

1. evolution works

the evidence is richness of our flora and fauna which adapted to almost all possible conditions on our planet. organisms live in polar ice , in desert rocks , in the bottom of pacific ocean mariana trench (11 km deep) and even on the moon .

evolutionary approach is one of the most powerful and proven methods known to us for designing effective systems under complex uncertain conditions. there are no reasons why software teams should ignore this approach - they indeed often deal with complex uncertain requirements and environment.

there are 2 areas where evolutionary approach could be used:

1. project management - enhance the way people work and interact for building a system
2. design and build - the growth of this software system itself.
   

simple steps:

1. generate new and modify existing ideas (increase variations).
2. select potentially best ideas for building software better in a specific environment (form project genotype)
   
3. make this generation of ideas work for some time (interact with environment).
   
4. learn from results - keep useful and dump harmful ideas (natural selection - improve fitness).
   
5. go to the first step and produce the new generation of ideas
   

we can make this process more intelligent and less random and still learn a lot from biological evolution.

2. increase beneficial variations or how to generate good ideas.

organisms will not evolve without getting new variations of traits. some new variations in a gene pool could lead to better survival and fitness, but most of them are harmful. software development genotype is a pool of ideas applied for building a specific software system.

how could we generate many good ideas and avoid harmful?

mechanisms of idea's evolution

• mutations - continuous invention and modification of the new approaches based on individual creative insights and team brainstorming
  
• reshuffling - recombination of existing ideas
• gene flow - outside expert opinions and borrowed ideas from other disciplines (engineering, art, architecture, manufacturing, etc.) and study of complex systems (physical, biological, markets, societies, etc.)
  

prerequisites for generating many quality ideas:

powerful software teams with diverse range of

• skills / specialization - they cover broad knowledge areas of software development: customer domain and needs, project management, ui design, development, testing
  
• expertise / experience - combination of different approaches, insights and methods of experienced professionals with fresh ideas of newcomers.
  
• personalities - various traits that complement the whole team: creativity, discipline, pragmatism, attention to details , imagination, focus and leadership.

decentralized control / self-organization
centralized control reduces ability to come up with new ideas, which are not compliant with imposed top views. people from bottom, who implement the system, could generate better ideas, because they know environment deeply, experience it closely and receive immediate feedback from it. independent people, who have control over project decisions and responsible for results will strive to make the best decisions.

idea incubator

• free flow of ideas, sharing of knowledge and expertise.
  
• encouragement for innovative and creative thoughts and tolerance to failures.
• opportunity for every team member to express ideas, be heard and respected.
  

good ideas in a software project are necessary foundation of success, lack of them is disaster. do whatever is possible to generate many good ideas.

3. improve fitness - keep useful and dump harmful ideas

genes passed to the next generation are result of two factors: fitness (natural selection) and chance (genetic drift).

how could we improve blind process of selecting best ideas and avoid high failure rate?

establish clear fitness criteria
every organism have clear short-term goals - survive and reproduce to accomplish the long term goal - passing and increasing share of their genes in the next generations.
software projects should have clear fitness criteria, which aligns team members, guide their decisions and actions. criteria should be relevant to the most important goals of the project. it could reflect the purpose of the system, time to market, quality or cost. it should be clear, short and really important for survival and success.

maintain selection pressure and increase role of fitness vs. chance
low natural selection leads to more complex solutions. most mutations which don't increase fitness will be eliminated in a large population with fierce competition and strong selection pressure. this process could lead to a greater simplicity keeping only useful for fitness traits. in populations without much selection pressure, genetic drift increase chances of new genes survival (even disadvantageous). so population could have increased genes complexity without much advantage for fitness.

avoid genetic drift
genetic drift produces random changes in the frequency of traits in a population, which results from the role chance plays in whether a given individual will survive and reproduce. chance play enormous role in biological evolution (maybe even more important than natural selection) and a great source of inefficiency. we can do better in software development. transparent and independent decision making, self organization and power of diverse opinions will substantially decrease the role of the blind chance.

therefore, a team with many good ideas shaped by selection pressure and fitness criteria will produce the best results.

4. pragmatic implementation

good enough working solutions
animals shouldn't be perfectly adapted, they just need to be in par with their competitors. natural selection requires only requires something to work, not perfectly but work. evolution is more likely reshape existing structures than invent new ones.
the classic example is the panda's thumb , which it uses to grasp bamboo. the panda's true thumb is committed to another role. the lobed fins of early fish have turned into structures as diverse as wings, fins, hoofs and hands.

in software we could be satisfied with solutions which are not perfect at the beginning. we can live with them knowing that evolution forces and pressure will shape ideas behind and we will make these solutions better with more experience.

practical and immediate purpose

every new feature in the system should have some immediate purpose - evolution invented only something that has purpose.

exaptation - structures and behaviors that evolved for one purpose but take on a wholly new one, while remaining useful at every intermediate stage. it means that some features cannot evolve if they are not completely useful immediately. two way radio could be useful for animal communication, but it didn't evolve, because half-way radio is useless - it doesn't tell anything useful for animals about their environment. visible light is different - any small improvement in vision can provide big advantage in many environments.
there is an interesting question: could we miss great design ideas if we only develop for immediate purpose? there are many useful inventions that came as a result of fundamental science curiosity without much practical need at the beginning. however, i'm inclined to believe that software development is empirical discipline and more effective with developing for immediate purpose only.

repurposing
repurposing a structure does not have to involve the loss of the original structure. reptilian jaw bones turned into mammalian ear bones, without the loss of the jaw. the neural circuitry that allows us to make fine limb movements may have been adapted to produce speech as well.

sometimes just one aspect of a feature can be co-opted for another use. the first hard mineralised structures to evolve in our ancestors were the teeth of early fishes known as conodonts. once the ability to form hard hydroxyapatite had evolved, it could be exploited elsewhere in the body and may have been the basis of the bony skeletons of all vertebrates.

repurposing is an interesting lesson for the software development - successful reuse of existing structures for the new functions. at the first glance, it goes against main principles of good software design - single responsibility, isolation and decoupling of components. biological organisms don't have much choice with mutations- which could add only small changes. but efficient and economical designs of many organisms suggest that repurposing could be a good strategy. we could maximize reuse of the components for different purposes while keeping smaller inner parts isolated. relentless refactoring, removal of duplication and creating abstractions are the main methods. the ultimate condition is good understanding and mental control over the system .

no refactoring (or elimination of unused traits)
lack of refactoring seems as a serious flaw of biological evolution. new organisms repurpose what exists and build new structures on top of old without cleaning and eliminating unnecessary stuff. dna has a lot of junk. these structures are not needed

• wings of ostriches
• appendix
  
• male nipples

software team can use refactoring as an essential part of effective and pragmatic implementation and improvement of evolutionary approach.

5. making impossible possible with small continuous changes.

small changes accumulated over time cause substantial changes in organisms. continuous improvement of the genotype and small frequent changes work for all living organisms in this unpredictable and very complex world. they lead to highly fit, adapted and efficient solutions.

by weeding out harmful mutations and assembling beneficial ones, natural selection acts like an "improbability drive" that can, given enough time, produce results that appear completely impossible at first glance.

one of the most important lessons for software development is possibility to arrive with great solutions without planning and predicting them in advance. it is one of the best strategies in the complex, uncertain and changing environment.

agile approach is successful because it strikes the balance between adaptation to changing environment and predictability required for business.

principles:

• be open and ready to changes
• frequently get feedback, change and adjust in small steps
• continuously learn and reflect what works and what doesn't
• often evaluate if your project and systems are fit for their purpose and environment.

summary

evolutionary approach works if software team

• can generate many good ideas
  
• can select most useful ideas how to build the system
• works under healthy pressure to meet fitness criteria
• pragmatic in implementation
• learn from results, continuously adapt to needs and environment
  

reference

what software development can learn from biological evolution? (softwarecreation.org)

resources:
comparing intelligent software evolution to chaotic biological evolution
evolution: 24 myths and misconceptions , newscientist (requires subscription)
evolution , wikipedia