No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
1–10 of 65 posts
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#2Maybe not 80s, but I vaguely remember visual basic 4 having autocomplete...
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#3> Debugging, back then, was an almost physical thing. Comparing character by character what was on screen against what was printed on the page. Realizing that the "1" that looked like a lowercase "l" had tricked you for half an hour.
And the 0 and 8. And this was used by some copy-protection to try to prevent reverse engineering. Back then real debuggers (by "real debugger" I mean not just "debugging in your head": but an actual, although very minimal, debugger) were very simplistic too, and so you'd read everything line by line, keeping in your head what the program was doing, was the register contained, what subroutines would do etc. And then you'd have "tricks" by the copy protection where that line with a '0' you just analyzed a few commands before would turn, sneakily, into a '8' (maybe by a function or a side effect of a command etc.).
And when we'd spot it we'd be: "Wait dude, did you notice how sneaky it is, this actually turns the 0 into an 8, so the next this execute, everything shall be corrupt" (or something like that).
And so debuggers got enhanced: for example if anything on screen got modified, the modified value would flash than stay in green. Stuff like that.
Our tools were much more basic.
But then we learned to eat 68x00 and x86 opcodes for breakfast.
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#4Maybe not 80s, but I vaguely remember visual basic 4 having autocomplete...
Which is why when being on UNIX, and having only vi, Emacs and XEmacs available, with basic tools like ctags, unless being lucky to work at some place paying for really expensive UNIX IDEs felt like a downgrade for folks raised in Amiga/PC world.
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#5I had a project at a private bank where we couldn't use the internet - we had to turn our phones in when we checked in, had to use their computers on their network, couldn't access the outside internet... we did have access to api documents electronically thankfully. If we wanted to update a library it had to go through a big security review that took weeks.
It slowed work down a lot but was totally fine - the bank was paying us tons of money hourly.
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#6[flagged]
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#7Grab BBC Basic manual (supplied with the computer) off the shelf, switch my Model B on (later Master). Within milliseconds a fresh working environment is created (ie a cursor starts flashing next to a “>”) and I’m off to the races.
Hope the tape recorder works to save my work every hour or so. Switch on my Epson fx80 to dump hard copy.
Simpler, happier times.
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#8I did an independent study of C in high school in 2003.
I sat at a non-internet-connected terminal in the back of the TechED room and typed examples from the provided book into a very simple editor. Sometimes they compiled and worked. Sometimes they did not work despite being to all appearances character for character the same as the book, and I was often left with no idea why.
It was not an entirely unfamiliar experience. I had a Mattel Aquarius as a young child and spent countless hours typing games in from the back of the manual before attempting to save them to cassette.
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#9Copying scripts from books is still the best way to learn, and still the only choice in some areas.
Re: No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s
#10[deleted]