3 ms·
What a great read. I've lived all of my professional life (2014-) shipping productive code by just pushing to repos or specific branches. I avoid getting into m
by jcmontx 1y ago
What a great read. I've lived all of my professional life (2014-) shipping productive code by just pushing to repos or specific branches. I avoid getting into mobile app development due to what a pain it is to get to the stores and stay compliant with ever-changing policies. I can't even imagine what was like delivering software in a cartridge or CD without a chance to update afterwards. It feels like such a titanic endeavor
- illys 1y agoIt requires a different way of coding: bug-free is a serious target, as far as it can be approached. It is a permanent concern while coding, with a lot of testing, and releases are hard releases, not agile output. No titanic effort there, just being serious and focused with quality.
- MarkusQ 1y agoIt was...easier? If your intent is ship-once working software, you write towards that goal. You use fewer dependencies, and they are all effectively version locked. It's like putting books in a box. You put them in the way you expect them to ship, rearrange as needed, and when they're all securely in, you ship. The current update fast and furiously free for all is like trying to bundle a few dozen kittens in a bed sheet by comparison. Often with a bunch of random chaos monkeys you've never met "helping."
- aaronbaugher 1y agoI remember playing a Commodore 64 game back then, maybe Pool of Radiance, and seeing a long list of play-testers in the credits. (And thinking what a cool job that would be.) They really had to put a piece of software through its paces back then before shipping it. And bugs still made it into the final copy, but if they did the job right, they were annoying or amusing bugs, not anything game-breaking.