My experience is that “good” code enables all of that — CI/CD, meaningful testing, monitoring/logging, operational tooling, etc.
Making any of that work for spaghetti is rough, since it lacks the boundaries and entry points those things rely on. And even if you ostensibly have it for “bad” code, it tends to be fragile and unreliable. (As my many, many overnight pages have shown.)
Of course, that may be different perceptions of “good”.
Making any of that work for spaghetti is rough, since it lacks the boundaries and entry points those things rely on. And even if you ostensibly have it for “bad” code, it tends to be fragile and unreliable. (As my many, many overnight pages have shown.)
Of course, that may be different perceptions of “good”.
reply