|
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.
|
|
|
|
|
I was stationed in Italy from 86 to 90 (Vicenza, airborne infantry) when I found Tandy computers at the PX. I bought one with two floppy drives and the disk had gwbasic on it. I started messing around with it and reading everything I could about working with computers and programming. I haven't stopped yet. Being able to get the computer to do something makes it worthwhile.
|
|
|
|
|
I was in college to become an EE (back in the 70s) and came across Byte magazine. Started reading about these new things call microprocessors and decided I could build a board with one of these, so I did (with a z80 processor). It was finished the day after my last final senior year. All I did for the next 3 weeks (until the start of my new job) was learn to program it. I had a whole 4K of RAM and a 2K EPROM containing the Zapple monitor program. There was no programming language so I was programming machine code by the numbers, poking values into memory, executing code at specified address, dump memory, etc. It was fascinating! At the new job, they were just starting to design a microprocessor base (Motorola 6800) smoke detector tester/calibrator. When they found out I had a computer at home, they asked me if I wanted to work on that project (of freaking course!!). I've been designing/programming ever since, mostly embedded systems.
|
|
|
|
|
I taught myself BASIC from a book my dad had on Dartmouth Basic back in 1978. Why? Why do you do anything when you're 14 -- because I wanted to.
|
|
|
|
|
My first coding was was in 1981 when some office donated a boatload of Commodore Pet 2001 Series computers to the school district I was in. My middle school math teacher ended up with them in his room, and offered to stay an extra hour after school every day to give anyone access to them that wanted it, in exchange for $20 a head, while letting us all know he knew nothing about them. One of my friends manages to get his hands on a manual from his dad's office, and we all started teaching ourselves Commodore Basic.
The next year, we all signed up for the "all new" computer class at the High School. They didn't really teach us anything. The teacher just came in and told us to do whatever we wanted, as long as we each turned in one "educational game/program" each quarter that could be handed over to the grade schools in the district so they could do something with the donated computers.
My Sophomore year, I consulted for the district to put their 5x7 index card attendance system into a database program. They bought the database program, and I designed the system (with its amazing 5.24" floppy based data transfer system) and trained all of the attendance secretaries in the district on how to use it.
That was also when I learned the value of getting signed contracts before doing any work.  They originally promised me $2000 for the job, but when everything was done, they told me that as a government entity they could not legally pay money to a minor as an independent contractor, but would make sure that I received an A grade in the computer class as compensation for my efforts (as if I wasn't already getting one). Lesson learned.
Money makes the world go round ... but documentation moves the money.
|
|
|
|
|
You mean something like:
y:=0;
y=0;
y<-0
set 0 as y
Y is in there somewhere.
Oh something else. I start in 1983 in High School with an Apple IIe. From there onto Pascal, C, C++, FORTRAN, Lisp, Java, VB.NET, C#, SQL, JavaScript, Python and the list goes on.
Of all the WHY in CODING:
WHY: FORTRAN code must start on specific column (older one).
WHY: VB.NET required _ for line break.
WHY: Python code blocks by indentation.
WHY: JavaScript "this" is the most confusion of all.
|
|
|
|
|
I took a programming class at Cal Poly when they got their 1st computer (1964-an IBM 1620 w/20K BCD bytes memory), and I got hooked (there was no way I was going to make a living as a Math major). Fortran II and assembly (I still have the instruction set manual-it was small). If you put a handheld radio up next to the console and ran a particular program, it would play 'Flight of the Bumble Bee'. 
|
|
|
|
|
I didn't want to work outside. Long ago. Still don't; unless it's warm.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
At the right age, I got to hear my father on the phone talking to an operator. Changing cards (JCL) in a deck to rerun a job that had thrown a OC7, and that he would be on his way back in. Oh, the mind puzzle.
In high school, 1980, we had an IBM 127 card punch. Our teacher would take our deck to the local community college and bring back the green-bar. We were NOT to: 10 I = 1, 20 PRINT I, 30 I = I + 1, 40 GOTO 10. And yet, someone in the class did. I would love to have seen the operator kill that job.
Why? Puzzles. From both sides - user wants to do what? ok, now how do I get it to do that. And the world keeps turning, the technology changing
|
|
|
|
|
Learned basic back in the 70s by reading books in the library, don't know why it just captured my imagination. Had a notebook filled with hand written programs but didn't get my first computer (zx81) until 3 or 4 years later. I remember as a teenager being really angry at my dad because they were throwing out an old mainframe at the place he worked and he wouldn't let me have it to keep in the garage!
|
|
|
|
|
I learned in 1966 because I wanted to know what those newfangled computer machines were.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
10GB/sec - wowser...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Must be the 'Ax effect' 
|
|
|
|
|
The only downside is that if you have it at home, it's only as wide as the pipe that feeds it. Standard coax-powered cable modems are stuck at 10mb I think, but streaming in-home from a media pc to the home theater pc would be fantastic.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
