|
I started programming in 1984 (standard 4 / grade 6 - age 12) on a Commodore VIC20. I just always enjoyed it. Couldn't believe that one could get paid to do something so enjoyable 
|
|
|
|
|
It was year 1999. There was huge incentive before Y2K and market was prospering and shedding money who could code HTML. But to make my fundamentals strong I started with C language and fell in love with it. I then wrote code in C, C#, Java, JavaScript, Web languages and frameworks, windows app development and Silverlight, etc.
// ♫ 99 little bugs in the code,
// 99 bugs in the code
// We fix a bug, compile it again
// 101 little bugs in the code ♫
|
Tell your manager, while you code: "good, cheap or fast: pick two. "
|
|
|
|
|
1982.
I was 10y old. In primary school. My neighbor got a British made ZX Spectrum microcomputer. I consider the day he brought it to my place the luckiest in my life. That night, knowing only five BASIC commands - LET, INPUT, PRINT, GOTO (yes!), and IF - I wrote my first code. On paper, using graphite pencil, of course. And I knew this was what I wanted to do.
Why? Were you ever asked by your girlfriend or your wife (or both?) why you love her ( of course you were -- it's a standard let's have a fight trap ) Not an easy question to answer. I suppose it is the creation of new, the individual self- dependency, the freedom to do whatever you want and the responsibility to fix bugs, the adolescent loneliness, the instant gratification of software - simply a good match to our characters.
Later in life I met a lot of people who never found themselves. Never knew what they want to do in life. It lead to realization of how lucky I was. Life gives you many boons and bones. But it's all easier if you have passion for your work. We, who do, are the lucky ones. We are the privileged few.  ![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
modified 23-Feb-18 4:38am.
|
|
|
|
|
We are indeed privileged. I look forward to working, and like others have said I am amazed I get to be paid (well) for it too.
|
|
|
|
|
Back in 1976 I took a FORTRAN course at Georgia Tech. The first time I saw that I could make a machine do THAT the lid was off. I was hooked on it and still am.
If you think hiring a professional is expensive, wait until you hire an amateur! - Red Adair
|
|
|
|
|
1979 on Commodore PET 8k computers. Why? Because it was interesting. I went to college for computer science because I had no idea what else to do.
Looks like it worked out for me. 
|
|
|
|
|
When: In 1980, our high school was picked as one of the 'test' high schools in the province to have computers: 3 Commodore PETS - 16K models.
Pretty much self-taught on Commodore BASIC and then 6502 Assembler.
Why: I had taken a data processing course before where we studied the history of computers, then, in the last term, we wrote programs using mark-sense cards. That peaked my interest.
From there... it was college and over 30 years of professional work.
|
|
|
|
|
I started in high school back in 1979 when I was a junior. We had three teletypes connected via modem (rotary dial phones and acoustic couplers) to the minicomputers across town at UND. The actual computers were a PDP-8 and a PDP-12 and we were learning BASIC. They wouldn't let us save anything on the computers but the teletypes were able to punch holes in paper tapes and read them. In my senior year they actually got an Apple II. I spent a lot of time in the computer lab and found that I really liked working with the computers. After I graduated from high school we moved down to Florida and I went to college. I just really enjoyed working with computers and I was able to get paid doing it as well. It's always nice when you can get paid for doing something that you like doing.
|
|
|
|
|
I saw a computer at a trade fair when I was a child and even it was green letters in black background I had it clear I loved that...
I started at an academy when I was 9... since then I've never stopped.
I started professionally at 1998 (some years before I did small jobs in different companies but the first serious thing was 1998). I specialized in the industrial/mechanical environment where robots and special machines live...
|
|
|
|
|
I started learning to code in 1977, when my stepfather bought a COSMAC ELF[^] single-board computer. It ran a 6502 processor with 2K of RAM. Our ELF was a deluxe model, and included a hex keypad for program entry. We found a Tiny BASIC interpreter that only took 1.5K of RAM. Adding a KSR-33 teletype gave us text I/O, and we were in business. I learned BASIC and wrote a lot of programs on that thing.
For the "WHY", we have to go back a lot further to the early 60's. We always watched the Gemini and Apollo launches. While the launch itself was great, I was mainly fascinated by the control room video and the idea that such machines were controlled by people pushing buttons on a panel. I eventually learned about computers being at the heart of things, and it's been all downhill ever since .
Software Zen: delete this;
|
|
|
|
|
About 1975 and I thought it would be a useful skill as computers were going to be everywhere. Started on a dial up to the local university, with BASIC. My school had a teletype that we used to communicate with the HP mini at the OU.
Later we built a Nascom.
modified 23-Feb-18 9:05am.
|
|
|
|
|
1980, Commodore 64s and a TRaSh-80 in math class, 11th grade. It was fun. Wrote an Asteroids style game on the 64. It was crude and sooooo slooooow but cheaper than 25 cents for the real thing!
Now I do programming for the money and it's still fairly fun. Outside of work, I don't much like computers.
|
|
|
|
|
1981 - Montana State University, CS 151, Pascal, Honeywell mainframe. Always like solving problems. Almost 40 years later, I still enjoy the challenge and the creativity.
|
|
|
|
|
When I give a computer something it doesn't like, it tells me clearly and plainly what I did wrong, and when I fix it, it doesn't hold a grudge.
I'm (a bit) autistic, so this is the only time I really feel like I have some sort of connection with something.
|
|
|
|
|
1973 - HP 2000C timeshare on an ASR-33 terminal.
I loved the Star Trek game and wanted to learn how to create my own.
Went over to the University Bookstore in LaCrosse, WI and bought the programming reference manual.
We had 8k of ram and 100k of program storage and kept our own programs on punched paper tape. Still have the Star Trek game on a roll of punched paper tape.
|
|
|
|
|
When: 1979, High School
What: Ohio Scientific Challenger II microcomputer, BASIC
Why: Video games were COOL even if the best that could be achieved was a CARET firing a PERIOD at an X!
Result: College degrees, but never published a game. I'm more DBA than coder these days, but it has been a fascinating journey that I have loved and continue to love everyday!
|
|
|
|
|
I wrote a FORTRAN program in high school to calculate chess moves. It was an eight-level nested loop. My Dad had to punch it in cards to run on an IBM 360. Somehow, he came up with the program needing more seconds to run than there are atoms in the universe. From there I went on to learn IBM 360 machine and assembly language and got access to a large mainframe to make the bell ring.
My WHY is that computers were cool, and might somehow help me with physics to build my flying saucer. Later, the WHY was changed to helping our country be more of a democracy than a republic, then changed to simply manage work flow in offices. Now, my WHY is to keep my health care after retirement.
|
|
|
|
|
I started with a commodore 64 and basic, moved to a Tandy with basic. Maybe 1980? I was fascinated and took all the basic programming classes in Junior High and High School. Majored in Math in college and took all the programming classes they offered, all the guys in the class were spending 20-30 completely the Pascal coding assignments at one point and it was just so easy for me. I loved it! In those days I was the only girl in the class, but I grew up on a construction site working for my dad. I was in my zone! Programming was a big puzzle and still is, and yelling at the code when it doesn't do what I want is a bonus... because that just means I need to figure out what I am actually telling it to do. I stay a programmer because I love the challenge!
|
|
|
|
|
In 1978 at college I made my first contact with a computer and programming language, BASIC. I didn't get it, failed. Then in 1980 at a different college I took a FORTRAN class, got the technical aspect of it, aced all the tests, but had to use punch cards to produce programs, which was a pain, so I 'borrowed' punch card stacks. Again, didn't really get into the whole computer and programming thing. Jump forward to 1986, after changing schools again and changing majors from Aeronautical Engineering to Electrical Engineering to Architecture to Art to Forestry then to Jewery/Silversmithing, thru a few part time jobs, in and out of college then back in, I came to the realization that my brother graduated in CompSci and was making good coin. So my whole reasoning for jumping back into CompSci/programming was "If my brother can do it and make money then I can to." No other reason. So I reluctantly jumped back in, had courses in BASIC, Pascal, Assembler on DEC-PDP11 w/ giant floppy disks, C, but what really REALLY hooked me was a graphics class using Turbo Pascal on a PC. I could visibly see results from my coding efforts. So after 10 years of wandering the planet I finally graduated in 1988 in CompSci, and now 30 years later, I still code C/C++, creating data entry tools that generate code for others so they don't have to. Which is really sad they miss out on programming but that's a whole new topic...
|
|
|
|
|
I learned to program on a HP 2115 minicomputer whose primary IO methods were paper tape and a teletype. One evening while trying to get something to work, I typed "why" at the command prompt. The computer replied "Why not". Since HP published the source code for the basic OS (HP Assembly Language), I dove in to see if I could find where "why" was being parsed as a legal command. As I remember, it was very well obfuscated using octal constants for both data and executable code.
I guess I'll have to go with the HP2115's answer to the question Why? Why not!
|
|
|
|
|
Started on HP 2116B, 8K memory, ASR33 TTY, 75 IPS tape drive, 200 channels slow speed DAC, 12 channels of 100K high speed DAC.
One manual covered hardware and software.
|
|
|
|
|
I designed and built a ADC card. We were recording nerve signals on a high quality multi-channel analog tape recorder, playing it back into the computer at 1/16 speed and doing FFTs and correlations to see how the nerves encoded information.
|
|
|
|
|
|
They were manipulating a cat's knee joint with a swept sine wave and measuring the activity on a nerve in the upper leg. They found that there were sensors in the knee that were sensitive to both position and velocity, with a hint that there was some sensitivity to acceleration.
The data processing was all done in HP's Fortran and took a long time. After they upgraded the computer to a HP 2100, which gave you access to the micro-code, I created a couple of new machine instructions that sped the FFT up by 15%. The 2100 systems also came with a disk drive that has both a fixed and removable cartridge. I am guessing that the platter was 14" in diameter and held maybe 2MB.
How was the HP being used in your situation?
|
|
|
|
|
Apple ][ with Apple BASIC -- Why? Because there were almost no useful programs then; it was the pre-VisiCalc era. Then I added a CPM card and a roaring-loud hard disk drive the size of a shoe box. Followed that with Compaq PC, Borland's Turbo Pascal and Turbo Prolog.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
