Since our robots do not need to be “rushed to market,” we can develop code in parallel, picking the most economical code to use in the robots. There is no rush: The trash is not going anywhere.
Greenfield
Codename: Order of the Phoenix
All changes to any code are created from scratch. Code is deleted and born again! Unchanged code is allowed to persist. Use of static libraries will make rewriting entire projects unnecessary, as any unchanged library code will not need to be rewritten. Accept that all code will need to burst into flames before better code can rise from the ashes!
Brownfield
Codename: Ministry of Magic
All changes to any code are developed by refactoring the existing code. Technical Debt accumulates! Use of static libraries will make much of the code reusable, but any changes will be through refactoring. Expect to occasionally get stuck in the mud!
Blackfield
Codename: Death Eaters
No code is ever deleted. Zombie code lives forever! No static libraries are used. Best Practices are ignored! Bloated frameworks and downloaded code are imported with reckless abandon! Slow programming languages, such as Python, Java, and PHP are used to “save development time.” No code, developed by this team, will ever be released as anything other than cautionary tales. Get used to disappointment!
Greyfield
Codename: Dumbledore’s Army
All tests are developed or performed by this team to test the code of the other teams (Greenfield, Brownfield, and Blackfield). Benchmark testing determines which team has the most efficient code. Team output testing determines which team is the most efficient at delivering features.
Leave a Reply