3 ms·
If you are spiking, then you should be throwing away that code. Don't productionise prototypes.
by cgrealy 5y ago
If you are spiking, then you should be throwing away that code.
Don't productionise prototypes.
- monocasa 5y agoDon't just throw untested prototypes in production, but you don't gain anything in a lot of envs by throwing away a prototype completely. You're likely to introduce additional issues by rewriting it for no reason.
- AnimalMuppet 5y agoWell, if a spike is going to become production, when it does, then write the tests (along with all the other cleanup that needs to happen if your going to turn prototype code into production).
- monocasa 5y agoYes, but that model is distinctly not TDD. You came to a design, then backfilled tests.
- AnimalMuppet 5y agoOnly if you keep the design of the spike when you convert it to production. But that should be part of the "production-izing" process, right? You convert it to a solid design instead of a quick-and-dirty hack?
- monocasa 5y agoMost of the time with this model, it's not a quick and dirty hack that is the result of spiking, but the design fleshed out with maybe stubs for a few of the low risk (to the overall design) error pathways. The whole point was getting to a design that fulfills the feature requirements but for which the contract boundaries weren't known going in.