First Programs
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
I remember the excitement. Nowadays, almost every new "great advance" is just the same old stuff with flashier (or stupider) graphics.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
The first time I programmed a computer was at university - an ICL running George 3 - and we programmed on punched cards. Unfortunately, there were about 6 punch machines (a huge box with a keyboard that made physical holes in the card, and printed the character at the top so you could read it) and several hundred students to use them. They broke - a lot - the ran out of printing tape all the time, and the queues were immense! You could use coding sheets and submit them to "the punch ladies" who would do them for you, but the turnround time was in days, not hours, and they typed what they saw, not what you wrote (which is why I "bar" my zeros and sevens to this day:
*** *****
* ** *
* * * ***
** * *
*** *So I soon learnt to read holes myself, and to use a hand punch where you pushed the pins through the card to make the letter columns. Then you put a rubber band round your cards, and submitted them to the Computer Operators for computer processing - which took about 8 hours on average to get a printout of your compiler errors. And the operators hated students - heck they hated everybody! They would drop the cards, shuffle them, add a few from the next pack, add a little lettuce and mayo (no, seriously - one of my desk can back with half a sandwich in the middle). So the whole process began again. Things have moved on: next time you complain about a VS compilation taking too long, remember that a edit-compile-run session when I started was probably a whole day...to get told you missed a double quote and it couldn't run!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
figuring out I could send a page full of CTRL-G's to my buddy
Back in the day we wrote a program that we could do things like open my bosses cd-drive during meetings. Of course we had to 1st access his machine to drop a listening app on there to do various neferious things, but it was worth the effort.
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
Breakout - that game where you batted a ball against bricks - in Sinclair Basic on a 16k Speccy. I'd love to see the source code now, I'd probably have forty fits over my variable names.
Slogans aren't solutions.
-
The first time I programmed a computer was at university - an ICL running George 3 - and we programmed on punched cards. Unfortunately, there were about 6 punch machines (a huge box with a keyboard that made physical holes in the card, and printed the character at the top so you could read it) and several hundred students to use them. They broke - a lot - the ran out of printing tape all the time, and the queues were immense! You could use coding sheets and submit them to "the punch ladies" who would do them for you, but the turnround time was in days, not hours, and they typed what they saw, not what you wrote (which is why I "bar" my zeros and sevens to this day:
*** *****
* ** *
* * * ***
** * *
*** *So I soon learnt to read holes myself, and to use a hand punch where you pushed the pins through the card to make the letter columns. Then you put a rubber band round your cards, and submitted them to the Computer Operators for computer processing - which took about 8 hours on average to get a printout of your compiler errors. And the operators hated students - heck they hated everybody! They would drop the cards, shuffle them, add a few from the next pack, add a little lettuce and mayo (no, seriously - one of my desk can back with half a sandwich in the middle). So the whole process began again. Things have moved on: next time you complain about a VS compilation taking too long, remember that a edit-compile-run session when I started was probably a whole day...to get told you missed a double quote and it couldn't run!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
Yep, always seemed much more exciting than these days :) This is where it all started for me back in 1981 when I was 8 years old.. [Commodore VIC-20 User's Manual](http://www.classiccmp.org/cini/pdf/Commodore/VIC-20 User's Manual.pdf) Happy days! :)
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
I think it was one of those silly "list some prime numbers" things, in z80 assembly. I'm not really sure, it's too long ago to really remember, but I was into prime numbers at the time and one of the main reasons I got into z80 assembly was that listing primes in basic was too slow. But my "good old days" aren't that old.
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
Oh yes I remember those things. Not too hard, because I had my old computer running just yesterday. :-)
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns. -
The first time I programmed a computer was at university - an ICL running George 3 - and we programmed on punched cards. Unfortunately, there were about 6 punch machines (a huge box with a keyboard that made physical holes in the card, and printed the character at the top so you could read it) and several hundred students to use them. They broke - a lot - the ran out of printing tape all the time, and the queues were immense! You could use coding sheets and submit them to "the punch ladies" who would do them for you, but the turnround time was in days, not hours, and they typed what they saw, not what you wrote (which is why I "bar" my zeros and sevens to this day:
*** *****
* ** *
* * * ***
** * *
*** *So I soon learnt to read holes myself, and to use a hand punch where you pushed the pins through the card to make the letter columns. Then you put a rubber band round your cards, and submitted them to the Computer Operators for computer processing - which took about 8 hours on average to get a printout of your compiler errors. And the operators hated students - heck they hated everybody! They would drop the cards, shuffle them, add a few from the next pack, add a little lettuce and mayo (no, seriously - one of my desk can back with half a sandwich in the middle). So the whole process began again. Things have moved on: next time you complain about a VS compilation taking too long, remember that a edit-compile-run session when I started was probably a whole day...to get told you missed a double quote and it couldn't run!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Back when you relied on yourself for syntax errors and not Intellisense or the compiler. :thumbsup:
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
I remember when I was in High School, I was out sick for a few days. I wrote, by hand, a two-person cowboy shooter game for a Commodore PET. My biggest problem was one of the variable names: BULLET. When I typed it in, I got SYNTAX errors.. and that is when I found out "LET" was a reserved word. Still, the program was fun to play.
-
The first time I programmed a computer was at university - an ICL running George 3 - and we programmed on punched cards. Unfortunately, there were about 6 punch machines (a huge box with a keyboard that made physical holes in the card, and printed the character at the top so you could read it) and several hundred students to use them. They broke - a lot - the ran out of printing tape all the time, and the queues were immense! You could use coding sheets and submit them to "the punch ladies" who would do them for you, but the turnround time was in days, not hours, and they typed what they saw, not what you wrote (which is why I "bar" my zeros and sevens to this day:
*** *****
* ** *
* * * ***
** * *
*** *So I soon learnt to read holes myself, and to use a hand punch where you pushed the pins through the card to make the letter columns. Then you put a rubber band round your cards, and submitted them to the Computer Operators for computer processing - which took about 8 hours on average to get a printout of your compiler errors. And the operators hated students - heck they hated everybody! They would drop the cards, shuffle them, add a few from the next pack, add a little lettuce and mayo (no, seriously - one of my desk can back with half a sandwich in the middle). So the whole process began again. Things have moved on: next time you complain about a VS compilation taking too long, remember that a edit-compile-run session when I started was probably a whole day...to get told you missed a double quote and it couldn't run!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
In High School, we were introduced to a language called HYPO - it was a hypothetical language that talk programming principles. We used mark-sense cards to write our programs, shipped them off to the local college, and then waited for the printed reply. All 'keywords' were numbers, including mathematical functions. So, 5 may mean subtraction, etc. Fast forward two years - in college now. One of the professors asked us to write a program in HYPO to read in a deck of cards (number unknown) and print them in reverse order. When he asked if anyone (100 students in the room) had completed the assignment, I put my hand up... and looked around to see I was the only one. He asked me to write the solution on the chalkboard, so I did.. a stream of numbers. The only way to accomplish the request was to have the program modify itself - change the card count indexer function from addition to subtraction. After that, I got along well with the professor...
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
The only good memories of the old days, was using an HP Apollo computers and the old Silicon Graphics workstation beasts at University. Other than that, nothing, really.
I'd rather be phishing!
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
Yes. Which is why I have a small collection of OpenVMS sytems here.
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
Repeat after me: Feed . . . register . . . release. Feed . . . register . . . release. Feed . . . register . . . release. Feed . . . register . . . release.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
The first time I programmed a computer was at university - an ICL running George 3 - and we programmed on punched cards. Unfortunately, there were about 6 punch machines (a huge box with a keyboard that made physical holes in the card, and printed the character at the top so you could read it) and several hundred students to use them. They broke - a lot - the ran out of printing tape all the time, and the queues were immense! You could use coding sheets and submit them to "the punch ladies" who would do them for you, but the turnround time was in days, not hours, and they typed what they saw, not what you wrote (which is why I "bar" my zeros and sevens to this day:
*** *****
* ** *
* * * ***
** * *
*** *So I soon learnt to read holes myself, and to use a hand punch where you pushed the pins through the card to make the letter columns. Then you put a rubber band round your cards, and submitted them to the Computer Operators for computer processing - which took about 8 hours on average to get a printout of your compiler errors. And the operators hated students - heck they hated everybody! They would drop the cards, shuffle them, add a few from the next pack, add a little lettuce and mayo (no, seriously - one of my desk can back with half a sandwich in the middle). So the whole process began again. Things have moved on: next time you complain about a VS compilation taking too long, remember that a edit-compile-run session when I started was probably a whole day...to get told you missed a double quote and it couldn't run!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
SNAP! BTDTGTTS The good old days 8)
-
I remember a long, long time ago writing programs out, longhand, on paper just for the fun of it - this was 2 or 3 years before I even had access to a computer, taught myself basic, fortran and cobol by reading books at the library (books! Remember them?). As an apprentice I remember an old SBC from a machine tool at work, state of the art it was at the time (68000 I think), I programmed it hex byte by hex byte on the bench to sequence a row of LEDs in a flashy pattern, how amazing was that at the time! Best of all when the company had it's first network with UNIX workstations and figuring out I could send a page full of CTRL-G's to my buddy in the next office and the look on his face as he hammered on the keyboard to try and stop it beeping, with the boss howling at him to shut it... Anyone else remember the good old days?
Yeah I remember typing programs from magazines into my ZX Spectrum. They never ever worked and I was always left scratching my head. My first program on the ZX Spectrum was a D&D character generator. Had I the wit to sell it, or port it to another platform, I could have made a bit of money out of it. Always thought I was going to write my own game. Forty years on, having worked as a software developer in more companies, projects and technologies than I dare to remember, I'm still chasing that dream.
-
Repeat after me: Feed . . . register . . . release. Feed . . . register . . . release. Feed . . . register . . . release. Feed . . . register . . . release.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Reminds me of my favorite class in college: CEG 431, Introduction to Concurrent Programming. Labs were on PDP-11/05's, programmed in PDP-11 assembly language. The machines had a board with magnetic core memory containing the bootstrap for the O/S. The bootstrap was 80 words. Unfortunately, if your program got out of hand, it could wipe the core. You then had to fat-finger the bootstrap in through the front panel switches: [^] I had to do that once or twice. One guy in our class got so good at it, he could re-enter the bootstrap in under 60 seconds. Of course, that doesn't say much for the quality of his code, that he needed to acquire that skill :rolleyes: .
Software Zen:
delete this; -
The first time I programmed a computer was at university - an ICL running George 3 - and we programmed on punched cards. Unfortunately, there were about 6 punch machines (a huge box with a keyboard that made physical holes in the card, and printed the character at the top so you could read it) and several hundred students to use them. They broke - a lot - the ran out of printing tape all the time, and the queues were immense! You could use coding sheets and submit them to "the punch ladies" who would do them for you, but the turnround time was in days, not hours, and they typed what they saw, not what you wrote (which is why I "bar" my zeros and sevens to this day:
*** *****
* ** *
* * * ***
** * *
*** *So I soon learnt to read holes myself, and to use a hand punch where you pushed the pins through the card to make the letter columns. Then you put a rubber band round your cards, and submitted them to the Computer Operators for computer processing - which took about 8 hours on average to get a printout of your compiler errors. And the operators hated students - heck they hated everybody! They would drop the cards, shuffle them, add a few from the next pack, add a little lettuce and mayo (no, seriously - one of my desk can back with half a sandwich in the middle). So the whole process began again. Things have moved on: next time you complain about a VS compilation taking too long, remember that a edit-compile-run session when I started was probably a whole day...to get told you missed a double quote and it couldn't run!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
And you had to put those JCL cards on top which generally I got wrong and after several hours waiting for the print out all I got was some incomprehensible error code in hex.
