3 ms·
You're presenting one way of running, "a large code base in production" as if it's the only way. It's not. The other way is to deploy frequently, accept some
by TameAntelope 5y ago
You're presenting one way of running, "a large code base in production" as if it's the only way.
It's not.
The other way is to deploy frequently, accept some amount of bugginess, and build your systems to deal with it appropriately.
Running and maintaining a large code base is not the huge technical challenge it once was, but unfortunately the relics of the past remain, and force everyone to do things their way, lest their hard-won knowledge becomes obsolete.
- LilBytes 5y agoMaybe they are frequently deploying to prod, but those pipelines are being used by other processes and commits. There's a big differece between committing small changes to an existing service or infrastructure base frequently, and conversely a PR or feature request from left field from a recent acquire.
- nightowl_games 5y agoThe code bases we have today are vastly larger than at any point in history and grow larger every day. The past is not so black and white.
- deleted 5y ago[deleted]