3 ms·
This could work in what I'll call a Fowlerian model for software development. This means that the code has superb unit testing and coverage; and that functiona
by shagie 5y ago
This could work in what I'll call a Fowlerian model for software development. This means that the code has superb unit testing and coverage; and that functionality is protected behind feature toggles rather than as artifact deployment.
That model has its advantages - but requires a mature and disciplined team behind it to not mess everything up and write crap and talk about it later (if at all). Functionality is exposed when the feature toggle is enabled - not when the CD system deploys it.
I would have trouble with exposing new functionality without a review of any sort - even on my own (perfect) code.
This can work in that Fowlerian ideal and possibly in the consultancy that he works for where it's got a mature and disciplined team. The issue is that I've found it to be rare where that sort of maturity and discipline exists - and that the developers aren't under a schedule pressure that has them submit less than ideal code to be fixed up later.
"Hey! It complies! Ship it!" is meant to be humorous.
- alkonaut 5y agoAgreed. An excelleent team working on excellent code can use any process they want and be successful. That's why the interesting process discussion is really: "what works for a team of sloppy and mediocre developers?".