5 ms·
I get this same feeling when looking at some of the code people commit the day before a release.
by meibo 3y ago
I get this same feeling when looking at some of the code people commit the day before a release.
- belter 3y agoProbably pushed by some recently rotated manager or new CEO dropped out of a recent acquisition...sometimes the code pushes the system over critically, sometimes it's just a code broken arrow event. Something to tell in the privacy of your next off the record interview or in your biography...
- The_Colonel 3y agoThe solution to that problem is to release every day. I'm not even kidding.
- makapuf 3y agoCritical staging code amount. Like that.
- quickthrower2 3y agoAnd release branches. Commit away to main all you like!
- fouc 3y agoGuess that doesn't apply to places with peer code reviews & continuous integration and continuous delivery/deployment (CI/CD).
- avgcorrection 3y agoIt doesn't for release but it does for merging things to the main branch and seeing if it fails or not (cf. “not rocket science”[1]). [1] https://graydon.livejournal.com/186550.html https://graydon.livejournal.com/186550.html