One thing we've seemed to regressed on though is the professional stature of our industry - back then private offices were the norm and the Orwellian open-office hellscape of today was no where to be found.
One thing we've seemed to regressed on though is the professional stature of our industry - back then private offices were the norm and the Orwellian open-office hellscape of today was no where to be found.
This was all because the turnaround was so slow.
Another fun card fact was that most people drew diagonal lines on their card decks, so you could more easily put them in order if they got scrambled.
The consequence of all of this is that debugging cards was actually not all that common, because you were doing checks at all the preliminary steps.
This was all quite fun, actually. Think of driving a standard-shift car, compared with an automatic.
This sounds a lot like how I work when writing new code that's not just a quick throw-away script, but built to last. If implementing a new feature takes me one week, then the first one is usually spent just reading the existing code and thinking about the other parts of the application and environment are going to interact with the new feature.
It takes more time initially, but it saves me a ton of pain down the line, and luckily my managers appreciate that trade-off as much as I do.