Learning about Code and Fix

Let me get to the point as soon as possible – Code and Fix is not a model. It is something more akin to anarchy. The whole concept here is about diving into coding with no planning at all. For this reason, it is called Code and Fix. In this, you completely skip all the crucial phases highlighted hitherto (requirements collection, architectural design, modeling, and so on) and start coding.

Then, if things go wrong, such as there are bugs or the software does not behave as expected, you start fixing. There is no dedicated time for writing documentation, nor for automation and unit testing. Versioning of the code is naive, and so is the dependency between modules (or maybe everything is stuck in just one huge module).

As you can imagine, there are few, if any, advantages to adopting this non-model. Let's start with the (obvious) disadvantages:

• You are basically working against whoever will maintain the code (perhaps your future self...