4 ms·
I think I was happiest as a developer, as far as how we did software, when I was working at a company that made utility software for DOS, Windows (3 and 95), an
by tzs 6y ago
I think I was happiest as a developer, as far as how we did software, when I was working at a company that made utility software for DOS, Windows (3 and 95), and Mac back when most computer users did not have internet.
The way people got our software was by buying a box containing a CD-ROM or floppies and a manual at their local Egghead, CompUSA, Best Buy, or similar or ordering it from a mail order place like MacMall, CDW, or similar.
There was no good mechanism to widely distribute updates, so if we wanted to get more money from a customer after that initial sale we had to do it by making the next version of the product compelling enough that they would go the store and buy another box.
Furthermore, our cut on a sale after the store and the distributor had taken their cuts was pretty small. If someone called our toll free support number with a problem that wasn't trivial for support to handle, it would wipe out all that we had made from the sale to that customer and more.
Without internet, malware only got onto a system via physical media. It wasn't like today where almost everything we do involves the internet and a potential attack. If you were happy with your OS and the programs you had, there was no reason you could not continue with them for many years.
To make money in that environment, what management wanted out of us developers was software the did what it box said it would do, reliably and without the need for the user to work around bugs and glitches, with good enough documentation that the user would never call support, and that would leave the user happy enough that when they need software for something else and see a box with that kind of software with our name on it, they would buy it.
If we did a new version of an existing product, management wanted all of that and they wanted the new version to have enough new features so that people with the prior version would be willing to pay full price for the new version.
There was no "ship it...we can fix that with an update later" attitude. It was more "we've got one shot at this...so let's do the best we possibly can".
- sjaak 6y agoAligned incentives are a beautiful thing.
- jacquesm 6y agoThis mirrors my own experience perfectly. Stuff I wrote three decades ago is still used unchanged in production in plenty of places. It doesn't need to be upgraded because it was built right the first time around. The fact that people would lose limb or life if I f'd up also really helped to focus and to get management to understand that I simply wouldn't ship if I felt it couldn't be trusted.
- badsectoracula 6y ago> There was no good mechanism to widely distribute updates, so if we wanted to get more money from a customer after that initial sale we had to do it by making the next version of the product compelling enough that they would go the store and buy another box. This is also something the article points out though... > The problem is that the tech companies have only one big tool to entice you to upgrade each year: piling on new features. More, more features. Microsoft Word was once a word processor. Today it's a database, and a Web-layout program, and a floor wax. > Eventually these companies have no choice but to add features that nobody asked for. Meanwhile bloated, overwhelming technology has a very real emotional effect on us; we feel like idiots when we can't master it. Though overall i agree with you that i prefer the way you mention. If nothing else i felt more in control on what goes into my PC.
- hinkley 6y agoYou can blunt this effect if you list performance as a feature. And reimagined features with fewer corner cases aka bugs. You don’t have to go feature factory if you don’t want to. Trouble is, too many people want to. I think it’s Conway’s Law after a fashion. The organization hasn’t set me up to be able to integrate closely with the existing code, so I write new code. Or I put other people in that position because the company ties my worth to old code too tightly so I feel threatened by changes.
- sokoloff 6y agoI don't recall feeling any higher level of work-related stress than when about to send out the golden master for our Sony PSX (original, CD-based) title. One shot, no patches ever.
- andrewmcwatters 6y agoInterestingly enough, for those of us mature enough to have experienced the former "ship it" attitude second-hand as consumers know these companies often only really have "one shot," because I'm sure as hell not going to pay to be QA at my age. Reading articles about products that crash day one tells me all I need to know. I don't consider the product even after it's been patched.