The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
That reminds me of when we would get on the teletype to MIT over the ARPANET (pre-internet) and play ZORK! I think I still have some of the output! It was written in MUDDLE, a friend analyzed it and found some cheat like "Send for mail" which would get you a brochure in the mailbox and one point!
Keying in instructions on the front panel of a LEO/III (see below) in 1966, and then moving to creating self loading programs on paper tape. Worked on various different systems and languages in the intervening years.
Depends. First program was written for the HP-67 on magnetic strip to run analysis of gas chromatography data.
Second was PDP-11 assembly to analyse data from Inductively Coupled Argon Plasma Spectrophotomer for elemental analysis
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
1964. First year science at Monash Uni. Punch FORTRAN II cards on an IBM 026, submit to the CDC 3200.
The next year we did all sorts of devious things, based on fixed load locations and lack of array bounds checking.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
Do those turtle things that run around the floor count?
If not, then I think 2000. Some Turbo C++ thing in which I wrote the biggest switch statement of my life... you enter an album track number, and it prints out the lyrics for that song. The album was Slipknot (self-entitled).
1984 I took my first programming class, BASIC. I absolutely hated it, the immediate spaghettification of any 'code' I wrote was very off putting, unreadable and near impossible to debug. I mostly blame the instructor for condoning poor coding practices. My next class was FORTRAN 77, and the opposite happened, I loved it. Since I was in the EE program, I didn't concentrate on programming in school. Only once I started working did I need to know assembler, c, c++.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
Besides making a TI-994a say naughty things in an endless basic loop, my first real programming experience was on a pdp-11/23 running SCO unix, a cc compiler and the K&R book. That was in the late 70s if I recall. vi was the editor. Better than edlin though.
1971 university - IBM 360 Fortran IV on punch cards. I still remember the 026 and 029 card punches. Designing algorithms for the Universal Turing machine and using Facit machines to design number crunching programs. First time I got paid for a program was December 1971 as an assistant to a PhD candidate who needed some programs. Today, 48 years later, I am still earning my living writing programs. Gone through all the languages. Fortran, PL/1, Assembler, Cobol, Basic in numerous flavours, C, C#, php, CLipper with DBIV and probably a whole lot of others that I don't remeber. I am currently learning Python. It's been a wonderful journey and I wouldn't change it for anything.
1968, in final year of high school, I did a Fortran IV course at University of NSW (over university radio). Submitted coding sheets by mail which were punched, run and the printout returned. So one batch turn-around per week!
1969 I started uni and graduated in Computer Science after 4 years.
Spent next 45 years programming.
Fortran at school, cards sent to the Town Hall for processing but completely forgotten.
Then at the end of the 80s a ZX81 with Basic which swiftly proved to be so limiting so I moved rapidly on to z80, 6809, 6510, 68000 and 8080 assembler (actually with z80 and 6809 it was initially pure hand written machine code). 2 games published on the Dragon and Commodore 64 together with sound and speech hardware addons.
the book was in German, useless to me.
10 PRINT "YOUR NAME";
20 GOTO 10
i wanted to do something colorful with graphics. i used to peek and poke it's memory and found out the screen map at address 1024-2023 and the color ram at address 55296-56295.
c64 had a terrible basic. as soon as possible i moved to machine language.
i don't know what was my first program, but i'll always remember my effort to move a sprite from left to right on the screen in assembly.
it took me about 10 careful rechecks and restarts of the program to realize that it is working correctly and that it is moving the sprite soooo fast that i am unable to see it. it only appeared at the final coordinate.
for comparison, in basic to increase the X coordinate of a sprite in a tight loop as fast as possible would crawl the sprite from left to right.
assembly language was the kind of revelation you see in 2001: A Space Odyssey, when the monkey faces the monolith.