|
I think it was 2300 B.C. I wrote a grain inventory program for the Abacus system using Cuneiform++. 
|
|
|
|
|
In 1975(?) I took a Saturday morning course for high school students at the local community college in FORTRAN on a Burroughs minicomputer. As I recall, I never did get a program to work. My first working programs were in Tiny BASIC on my stepdad's COSMAC ELF-II[^] single board computer, based on the RCA 1802 microprocessor. I also wrote a lot of programs for the TI-59[^] programmable calculator my parents bought me for high school graduation.
My first professional programming in 1980 was on an HP 1000[^] series minicomputer in FORTRAN 66. I was a sophomore in college and was paid the whopping sum of $6.00 per hour.
Not to be cliché, but - good times.
Software Zen: delete this;
|
|
|
|
|
TRS-80 Model 1 level 2 BASIC. Was barely in 1st grade. My dad had built and modded a second one so I got the first one with a cassette player, some games, and a library or magazines to "play". I managed to code a couple really simple games, choose your adventure, and a failed attempt at a Pong like game. (Graphical programming was hard for my 8 year old brain) One program I had was a menu for programs on a cassette. Menu program was at beginning of tape and had a directory of the apps and their tape counter location. Fast forward the tape to counter nnn and CLOAD.
Fast forward 5 or so years and I got a 2nd hand 286 IBM compatible PC. Played around with GW-BASIC and actually started digging into Batch scripting. During high school I tinkered with QuickBASIC and DBASE (yes i consider it a programming language) but had found that all i would do is make menu and UI shells for the batch utils i made. I took more to the hardware/networking side of things.
It wasn't until a few years out of college that I got my first professional opportunity. VB6 and Office VBA migration to .NET solutions. And here I am.
Its sorta funny how I find myself doing the same sorts of things over a 30 year span.. Like little scripts and utilities and then building simple menu based UIs to navigate those utils.
|
|
|
|
|
Around 1980 - Commodore Pet at high school. 4K and 1MHz, I believe. Came complete with cassette recorder so we could even save our programs.
Outside of a dog, a book is a man's best friend; inside of a dog, it's too dark to read. -- Groucho Marx
|
|
|
|
|
My high school in the early 80s had these TRS-80s from Radio Shack. There was one course offered, BASIC.
We saved our homework on cassette tapes. Each of the four or so computers had an old-style cassette tape recorder connected to it somehow. I remember a friend of mine and I were curious about what would happen if we played them as audio. I think it was just kind of random static.
Off to college, various courses, starting with Fortran and assembler on a VAX 11/780.
First professional experience was in EDL on an old IBM Series/1. This was very much like assembler; to debug, you'd get a printout of your program, on the left-hand side of which was the compiled machine language. Setting breakpoints at addresses, inspecting memory directly, etc.
I feel like that was a good experience, made it easier to understand how software is actually executed by seeing some of the under-the-hood post-compilation results.
Through COBOL, C, java, C#, blah, blah, blah.
|
|
|
|
|
First program in 1964 on a Univac Digital Trainer in binary - no assembler or other gewgaws.
Many commercial computers later, I built a Heathkit H8 in 1977 and used it to compute golf handicaps and other simple tasks.
Now, I play with Raspberry Pi, WeMos D1 Mini, etc.
I also placed in the age category.
|
|
|
|
|
1969, FORTRAN via punch cards on an IBM 370. The procedure was:
1. Punch cards
2. Submit deck
3. Wait somewhere between 5 minutes and several hours
4. Pickup output listing
5. Find typo or logic error
6. Repeat
I think the program had something to do with using Simpson's Rule.
Later on I did a lot of programming on a HP 2100 mini-computer via paper tape on a teletype machine. I remember trying to get something working late on day and out of frustration I randomly typed 'why' at the prompt. The computer responded with 'Why not'.
HP published all the details on the machine, include the assembly language source code for the OS. I decided to figure out where the 'Why not' was coming from. It was extremely well disguised so it took a couple of hours to find it. It's pretty easy to disguise stuff in assembly language.
|
|
|
|
|
Back in the 70's I got this educational thingy called "CARDIAC". Was a cardboard tool to demonstrate the workings of a computer. Had sections for memory and registers, and you would write in with pencil your program, and execute the instructions, etc. Very simple, but showed me enough to get me hooked.
High school we had access to an old HP computer. Had a 80 character, single line LED display, card reader, plotter, thermal printer, and 4K of core RAM. Lots of fun doing plots and such. Also the school had an 1802 kit that I would do assembler coding on.
First real computer was a TRS-80, and first computer job was during the summer when I was 15, writing some office software on a UCSD Pascal system. And I haven't stopped since 😉
|
|
|
|
|
January 1974. FORTRAN, punch cards, IBM 1130. Loved and hated it.
|
|
|
|
|
Also FORTRAN and punch cards on an IBM1130 (4K RAM). In high school, might have been around 1972.
|
|
|
|
|
Lots of interesting replies. Here's mine. We had a Computer Club at my grammar school in 1966 run by one of the science teachers. We learnt about binary numbers & how computers (at that time) worked. We had some type of primitive system that was collectively programmed to solve simple math/logic problems and show the answers in binary using lights on or off. My first real programming experience was learning Fortran at the end of 2nd year Civ. Eng. degree in 1969. For some unknown reason, after the exams we had a 2 week course each morning waiting for exam results to be published. Needless to say, we spent most of our time partying & so often had less than clear heads in the morning. For the first couple of days of the Fortran course I couldn't make any sense of it. How could i = i + 1? Then it suddenly clicked & I was hooked. The next year I did my 3rd year project programming a simulation of a water resources system to optimize withdrawals from different sources to meet the demand from a nearby city. It was punched cards which were delivered to the Computer Dept. on the other side of campus. If you submitted by 11am, you got your print out the next day. If not you had to wait until the day after. From there I moved to Canada to do a Masters including a thesis developing/programming a deterministic conceptual hydrologic model. This led to a 40+ year career as a water resources consulting engineer doing computer modelling. At first, we did lots of programming but eventually pre-packaged models took over so I kept up my interest as a recreational programmer with a C64, etc. learning various languages, etc. continuing up to today.
|
|
|
|
|
Wow. In all my years of programming (since 1974), I never had a problem with I=I+1. Maybe it was the way it was taught - as an assignment, not as a mathematical identity. When I read your post, my first reaction was, why didn’t that bother me at the time? Not enough imagination, I guess.
modified 4-Nov-19 9:42am.
|
|
|
|
|
1964, IBM 1620, 20K bytes memory, assembly and Fortran II (I'm 80). 
|
|
|
|
|
From the first line of code to transitioning from an Auto Mechanic to a professional Software Developer.
1977 (ish): Writing Basic code on a Bally Entertainment System, wrote a simple Multi-Die + Adjustments dice rolling routine for D&D. Had to load and save via cassette tape.
Late 1977: Followed shortly thereafter by an Apple II+ that my dad received for his office. Wrote several D&D applications where I could run a random campaign pretty easily. Unfortunately, it was at his office most of the time.
1982: A KayPro II luggable continuously borrowed from a neighbor who didn't care to use it (it was supplied through his emplyer). I finally had something I could use on a regular basis. Ported all of my D&D code from the Apple II+ to the KayPro and wrote even more stuff for our D&D campaigning. 
1983: Life happened... Didn't touch a computer for 5 years.
1988: Discovered BBS's via a friend of mine who ran one. Rented to own an 10Mhz IBM XT clone, taught myself QuickBasic and Pascal. Quickly acquired 2 80286 machines. Taught myself C. Picked up an 80386 machine. Ran a BBS of my own, wrote BBS Doors, other utilities.
1990: I was hired as a programmer writing billing and management code for a company (now defunct) in Carrollton Tx. The journey begins!
|
|
|
|
|
IBM 709 in Machine Language then assembler then FORTRAN in early 1961. Still writing code but in higher level languages.
|
|
|
|
|
The first actual programming I did was on a Apple II sometime in the early 80's. I programmed generating and storing character sheets for D & D. I programmed in Apple Basic, but I THINK the actual Basic program code was written by Micro-Soft, if I remember correctly.
What got me interested in programs themselves was my first computer, a TRS-80, from 1978. I had a game called Pursuit of the Graf Spee. You had to load it from a cassette tape using a standard player connected to the computer by an audio patch cable. I discovered if you hit the Break characters (don't remember if it was Cntrl-C or not) the program would stop, you could see the code that made up the game, and you could alter the ship's performance.
You alternated sitting at the keyboard/screen. The German Player would enter his move/speed, then the British would enter theirs. The British had more ships, but the fast ones were out-gunned by the Spee and the big gun Rodney was too slow to catch it in a race. Unless like me you hit the Program Break and altered the code before starting the game for real. You could change it so that you had incredible amounts of fuel, travel at 99 knots and have a ridiculous number of guns and armor. You could only have 2 digit numbers for turrets, armor and guns per turret on the ship, but that let you put 99 turrets, with 99 guns each. And 99 inches of armor.
It was a fun trick to play once on someone, but the game alterations weren't saved so you had to alter the code each time, and you had to do it without the other player knowing you did it. But it was fun looking through the code and figuring out what commands/code did what, and how they set up the situation and what percentages they assigned different actions and what they did to keep track of the 5 or 6 ships the 2 players controlled.
When I went to school the beginner languages taught was Fortran and Pascal, with C being what was pushed for advanced language. COBOL still was taught but it was an optional class.
|
|
|
|
|
1969 assembly language on a Varian Associates 620i 16 bit computer with 4k of core memory. Teletype punch paper tape to load program, after manually entering bootstrap program from front panel switches. System used to control and record data from a Farrington Electronics OCR page reader.
|
|
|
|
|
I would have been four in 1960, OP. Still interested in magnets, toads, bicycles and bunnies. I could already read comic books by then, so my fate was sealed. First real was Fortran and BASIC in whatever year Reagan was elected President. I think Windows 1.0 was still about seven years away?
Reading all the replies, I have to say it's nice to have someone my own age to play with.
|
|
|
|
|
No punch card machine at the high school I attended; our 'punch' cards had to be filled in by hand using Sharpies, sent out 2x a week to the one high school in the area that had a computer we could get some processing time on, and we got to do a field trip every two weeks to that school so that we got a total of 5-6 tries maybe in a 2 week period to get our FORTRAN programs correct.
That inspired me though, so over the next summer I spent my babysitting money on a COSMAC Elf (RCA 1802) kit, taught myself assembly language and eventually abandoned my plans to become a veterinarian even though the state university I attended starting that fall didn't quite have such a thing as a degree in computer anything.
~ janet
|
|
|
|
|
Fortran 4 in high school in 1972. 026 keypunch. Lame IBM "programmed learning" course. IBM 360 at the Seattle Public Schools central office, approximately three week (!!) turnaround via US Mail round trip. Favorite error message "Expecting operator but , before J was found"
|
|
|
|
|
First professional experience was PL/I on IBM 360/95 modeling heat flow through a nuclear reactor core section and Assembly language on a HP 2116 at Argonne National Laboratory in 1968 for data collection.
Then went to work for GTE after Nixon got elected and axed R&D budgets where I was programming the IBM 1800 in Assembly and a touch of Fortran II. Modified the be-dickens out of the 1800 MPX operating system including writing a printer spooling system, developing support for the 2314 disk drives, bi-sync communications to IBM 370/158 and 168, and developing real time multi-programming/multi-tasking OS'es including assemblers for Data General Nova and GTE Tempo II computer, all while going to night school at IIT and studying languages such as Lisp and Univac 1108 assembly language.
Managed to get married, buy and remodel a house and have 3 kids. I'm not sure if I ever slept.
|
|
|
|
|
Please don't repost if your message doesn't appear immediately: all three got sent to moderation by the automated system and required a human to check and approve them. And then follow you around and clear up the spares ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Sorry about that. We've been having ISP problems with intermittent outages. I thought maybe that was causing the delay in seeing the post.
Thanks.
|
|
|
|
|
Not trying to top you all but in 1963 I went to work at the University of B.C. as an operator on an IBM1620. I learned to program in assembler and FORTRAN 1a. FORTRAN was a 2 pass compiler. you would load pass 1 by cards followed by your program followed by pass 2 followed by your program again. I also monitored the ALWAC III a machine with mercury delay memory. We finally upgraded to an IBM7040 with mag tapes and a disk drive the size of a commercial refrigerator. By then I was a systems programmer. I've been through many languages such as algol, B, Basic(several), C, C++, COBOL, JAVA, Lisp, Pascal, PL1, and many assemblers. Worked with various machines from IBM, Honeywell, Intel(Microsoft et al), Digital Equipment, RCA, CDC. I'm now retired and write in C for my own pleasure for windows, Raspberry Pi, arduino. Fortran was the most fun.
|
|
|
|
|
A PC games magazine published readers' games on the pack-in-CD. Some of them were written in QBasic with the QBasic interpreter attached. That got me started (and I even got a creation of mine published).
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
