3 ms·
At my first professional software job, where we wrote C, because that was all you could realistically write commercial software in, there was one person on our
by tptacek 2y ago
At my first professional software job, where we wrote C, because that was all you could realistically write commercial software in, there was one person on our floor who could do software builds. He used some commercial build tool the company had licensed and he was the only one who knew how to use it or would be allowed to learn how to use it. His customers were every product team in our division --- about 12 of them. We had to petition to get beta releases done. The builds took hours.
I think we're doing fine.
- dgb23 2y agoThis cracked me up. I love hearing those stories, also from my father, where he would talk about "we already did that in the 80's and it was called...", and then he would tell me about some obscure assembler tricks to patch binaries, in order to keep them compatible with some system I never heard about. But still, I think we can do better. That story you shared highlights a gross inefficiency and diminishing of agency that comes from dependencies.
- phendrenad2 2y agoI kind of agree. I think software has a certain amount of "badness" that will always exist, it's a mathematical equilibrium. There are a myriad of things that can make your process bad, and if you fix all of them, you'll never ship. The list Pope gives here are the most common issues, but not all teams will check the whole list.
- skydhash 2y ago> I think software has a certain amount of "badness" that will always exist It's fitting a messy, real world process, to the virtual, reduced (because formalism) computing world backed by failable, messy hardware components through an error-prone, misunderstanding-prone of programming. So much failure points, and no one is willing to bear the costs to reduce them.
- YZF 2y agoWhat year are we talking about here? Circa 1982 or so (and some years before) IBM was shipping mainframe software written in Assembly that anyone could build or modify. They had a bug database that customers could access. Around the same era Unix was shipping with source code and all the tooling you needed to build the software and the OS itself. So maybe compared to some of that we're doing worse.
- tptacek 2y ago1998.
- YZF 2y agoCirca 1999 I was with a startup. We wrote C and C++ for Windows and embedded platforms. We used source control. Every developer could build everything on their PC. We used Visual Studio. Also from 2000: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s... So I think we knew around that time what patterns were good ones... But sure, lots of software organizations didn't even use source control and failed Joel's test miserably. EDIT: And sadly enough many orgs today fail Joel's test as well. We forgot some things that help make better software.
- tptacek 2y agoThe shop I was at was Network Associates (you'd know them now as McAfee).
- pvg 2y agowe knew around that time what patterns were good ones The source control system I had at one job around that time was a dvcs! At a different one, the source control system had its own filesystem was generally insane. It had its own fulltime maintainer sort of like tptacek's build person. The big difference, really, was that all this software cost a lot of money compared to now where it mostly does not.
- dilyevsky 2y agoSame here except Motorola circa 2007. The build took hours and compiler was licensed from Windriver. We had to schedule time to do builds and test runs using some Rational pos software and we had a dedicated eng in charge of doing merges on release branch
- aqueueaqueue 2y agoWe are doing badly. I bet he was paid enough to buy a good house and it was a low stress issue Job!