|
Literacy as in knowing basic user operations before going to programming. For instance, knowing what left and right click is. I, for one, had no clue when I wrote programs for first few months.
|
|
|
|
|
d@nish wrote: For instance, knowing what left and right click is.
There was no left and right click.
There was no mouse.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
There wasn't even a damn keyboard, half the time!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
That was my point, the concept of computer literacy has changed over time as computers have evolved.
I could do everything I needed to with my C64, so I was Computer Literate, but I wasn't for the modern definition that was in the mind of the OP.
For those of you who started off shoveling coal into the things whilst someone else opened and closed the valves whilst a third operator carefully monitored the weasel levels the question makes even less sense.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
Certainly no screen - teletype only.
|
|
|
|
|
One place I worked at - National Institute For Biological Standards and Controls, in the early eighties - had two "punch girls" who got a sheet of numbers from the biologists, punched them onto paper tape on an offline teletype, then used the screen based terminal to run them through the PDP 11. If there were any mistakes, the paper tape was carefully edited to fix it with a knife and sticky tape and it was retried. When the run was complete, the paper tape went back to the biologist who binned it.
Took me months to get permission to teach them to plug the teletype into the PDP11 and forgo the paper tape - with a box on the submission sheet saying "I want the tape!"
Then about twenty minutes to get them actual terminals, a week later - since they threatened to go on strike unless they did!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
At school we would often find that the paper tape would tangle as it was feeding into the reader on the ASR33 (no hopper to contain the tape) so we would clip the tape into the reader then lead the tape across the room and open a window and drop the tape out - the computer room was on the 3rd floor - so that it wasn't all coiled up.
As it fed out of the reader (low speed 110 baud phone line meant this was a tedious process) we would roll it back up by hand and store the tapes in pipe tobacco tins (conveniently, the computer science teacher smoked a pipe).
|
|
|
|
|
And as you hand fed the tape back into a roll you got paper cuts between your thumb and index finger!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Oh yes - initially. You soon learnt how to roll it without getting the cuts.
|
|
|
|
|
...until you hit a join and it shaved your fingers...
And the Mylar versions were worse: stronger, stiffer and sharper.
Would you believe I think I still have a tape repair tool in the attic?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Click? I wrote my first program on a Teletype creating a punched paper tape. It was done that way because it cost too much to develop it while connected to the timesharing service via an acoustic coupler. I think we had the high speed 300 baud version.
|
|
|
|
|
Yes, those there the good ol' days
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|
|
Same method - but on a ZX Spectrum 16K
Ger
|
|
|
|
|
Same here... only it was an Atari 400. I had a few programs written to audio tape that are lost to the ages. Probably taped over with White Lion or Def Leppard
So I was very computer illiterate - the personal computer at that time would have been maybe a Heathkit that you built from the ground up, but that was not my level of dedication.
First program? I remember staying up late getting my name to march around the screen in different ways. Good times.
Good times *sigh*
|
|
|
|
|
Nice musical references!
Ed Bouras wrote: White Lion or Def Leppard
I did mine on a TI-99/4a. It was great until the cassette interface/modem quit working. I could still write BASIC programs to solve physics and math homework problems...I just couldn't save them...and I couldn't create save points in the Scott Adam's Adventure games. SAV GAM
Damn good times!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Heh. Of course those was my musically misguided years... before I discovered the awesomeness of Rush!
I think there are a few Canadian CP'ers here who would agree with that assessment
I think my neighbor had a TI-99 that we used to play Tunnels of DoomClickety[] on. Loved that game!
|
|
|
|
|
Yeah I had NO idea.
PDP-8 at school in the late 70s. I got to "10 print <something awful="" about="" the="" vice="" principal="">\n20 goto 10" pretty quickly.
The big reveal was adding the ';' character to the inside of the string which would suppress the crlf (which, on the wide-carriage screenless terminal really was "carriage return, line feed".
It's all been downhill from there.
|
|
|
|
|
The old VAX eh? THats even before my time!
Sinclair Spectrum and the BBC were the first computers I came across. They were rare beasts before then, very rare.
|
|
|
|
|
The PDP was before the VAX, both by DEC.
The PDP was the processor that gave birth to the C programming language.
When I learned the MACRO-11 Assembler in High School, I did not realize I was learning C.
The best ASSEMBLY EVER.
Even though we had paper terminals. We had 3 "CRTs", which I quickly started using.
Learning that the OS was just a program. That was the moment the light went on.
We used RSTS/E Operating System, and by by the time I graduated High School, I had patched
the OS in numerous ways (Hidden Files, bypassing NOLOGON)
Crazy Times. But I learned how to do so much with that system.
Oh, and in homage to VB programmers everywhere, this OS used BASIC Plus for almost all of the system library programs (Login, Logout). They did this by using a weird concept of Interrupts called System function calls.
A$ = sys( chr$(6)+ "..." )
It took a single string, the first character was like the interrupt jump table byte (which function), and the rest of the string was parsed. So, 6 for system function, then like a 5 for Kill job, then the job number converted to a string. Really cool Radix50.
Wow, that brought back too many memories from 1984-1985...
|
|
|
|
|
That is pretty cool actually. I love this kind of stuff, digging round in the guts of the machine,. its why I write drivers, and why I prefer Linux to Windows, though I have done a lot more on WIndows, you are closer to the real machine.
User mode stuff just makes me angry. All you are dealing with is someone elses rules, someone elses wrapper, and someone elses limitations.
Working down with the hardware, having to take into account electrical states, ,that's where the fun is./
|
|
|
|
|
Very, very, very.
I didn't even see a computer until about six months after I started coding - we used punch cards in those days - being able to use a terminal and even an editor (poor by modern standards as it was) was a brilliant revelation!
"Turning the computer on" had to wait about another year and the 5th computer I used: a PDP8.
And starting that box was a bit harder than today:
Turn key to POWER.
Set all switches to 0
Click on EXTD
Set switches to 0x0018
Click on ADDR
Set switches to 0x0DE3
Click on DEP
Set switches to 0x0A19
Click on DEP
Set switches to 0x0080
Click on ADDR
Click on CLR
Verify HALT and STEP are up
Click on CONT
(I cheated and checked the exact values, but I remembered it pretty well: only one digit error!)
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I am proud to say that i have seen an punch card, never saw the machine (we are not counting the pictures and internet).
OT:
I have whole 2 boxes full of doughnuts from Dunkin Donuts (we have no other choice here for good doughnuts) but still i am very happy :P
Why i am sharing this ? Because when you are sending the lappie sleeve you need to add something extra in good packaging, choco is prefered
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
Punched card had big advantages over "Modern" editors and HDDs.
They taught you to write concise, efficient programs.
Otherwise you needed wheels to move your code around! We didn't have "copy'n'paste", we had "drag'n'hernia"! That stuff got heavy quickly
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
You left out "knocking over the card stack of the guy/gal you didn't like". My first program was a COBOL program, punched in, then fed to a 370/115. I was in my first semester of a Business Administration degree, fell in love with coding, transferred to a 2 year state tech, got an AS in coding and never looked back. Fortunately for me I never actually had to work on a Mainframe, PC's & 'Mini' computers were just coming into vogue, so that's what I've always worked on. C first, x86 asm, then C++.
|
|
|
|
|
Using punched cards taught me how to delicately fit a chad back into a mis-punched hole, and keep it in place with sticky tape. And clog up the card reader.
|
|
|
|