3 ms·
My first job in the valley I worked with a guy who had coded Cobol for the Air Force. He would write all his code and go over it for days executing it in his he
by strangattractor 3y ago
My first job in the valley I worked with a guy who had coded Cobol for the Air Force. He would write all his code and go over it for days executing it in his head not even a compile. He would then compile it. Fix the syntax errors - usually only a few and finally did some minimal debugging.
He did not have to work that way given that we had more modern tools. It was just his process from using punch cards.
- SoftTalker 3y agoI worked that way in my first job with a big consulting firm in the early 1990s. Better tools were available by then but a lot of client sites didn't have them. So you had a 3270 terminal and had to submit jobs for compiles. The queue could be several hours if the mainframe was busy, and fewer resources were available to developers than for running production. So time spent "desk checking" your code would often pay off in having to run fewer compiles.
- intelVISA 3y agoNot a bad approach, as even nowadays the job is mostly done by the time your keyboard is turning designs into binaries.