3 ms·
You could have a highly proscriptive spec, or almost none. It depended what kind of s/w shop you worked in. I interviewed candidates for a sw position who fron
by ggm 4y ago
You could have a highly proscriptive spec, or almost none. It depended what kind of s/w shop you worked in.
I interviewed candidates for a sw position who fronted with serious lisp experience on live deployment: traffic lights control systems. (We wanted C. But it stuck in the mind)
Compile-Edit cycles could leave you time for lunch.
SCCS was still in use, RCS was just better.
You had to understand byte/short/word/longword behaviours in your compiler. Unsigned was tricky sometimes.
FP error was common. Not all the bugs were ironed out of libraries (NAG aside. They were really reductionist)
Use of global variables was not yet entirely anathema
The CPP could run out of #defines still.
Pdp11 were getting more uncommon but not dead. VAX were common. Sun's were 68000 mostly.
There was a gulf between IBM and their seven dwarves and everyone else. UNIX was not quite ubiquitous off campus but becoming so.
- pencilguin 4y agoRCS was worse than SCCS on every axis except marketing. It was claimed to be faster but was slower. The code quality was abysmal.
- ggm 4y agoCan't deny, but not what we believed at the time.
- pencilguin 4y agoI was fooled too.
- jansan 4y agoCompile-Edit cycles could leave you time for lunch. Database queries at my father's company were started on Friday afternoon and were finished on Tuesday. Those same queries take milliseconds nowadays.
- PaulDavisThe1st 4y ago> You had to understand byte/short/word/longword behaviours in your compiler. Unsigned was tricky sometimes. For some of us, this is still the case.