Who am I? How did I become a Computer Scientist? Science Fairs!

High School science fairs are largely to blame for me becoming a computer scientist, and not an industrial chemist or something else.

In year 6 (NZ school system) I entered the regional Bay of Plenty science fair with an experiment on zone electrophoresis (from memory it involved high voltage - the fun part - and other stuff. It was a live demonstration (always dangerous) with me not there, and I recall they had to shut it off because of smoke and maybe fire being produced - whoops). Fail # 1 for a career in industrial chemistry.



By year 7 (final year of high school) I was more interested in electronics, so I entered 2 things in the science fair (and won 2 prizes, 1st prize for electronics, and 2nd for general science entry).

The 1st was another "scientific" experiment, I build a simple nuclear magnetic resonance spectrometer (NMR) - basically a machine to wiggle water molecules.  It didn't have any "moving" parts just a large permanent magnetic, a sweep generator (high frequency generator), a test tube with water, a radio frequency receiver thingy, an oscilloscope, etc. It was a miracle that it worked (according to the judge, professor of physics at Waikato where I ended up studying the next year) but it did. 



In 1979 I also built a microprocessor based computer (which won 1st prize for electronics, even though I recall that it didn't work yet for the science fair, I had 2 wires reversed which took me months to debug).

It was based on the SC/MP chip. It was based on the Dick Smith Mini-Scamp kit (but I built if from scratch),  with 256 Bytes of memory. And it didn't have switches or LEDS for programming like this picture. Mine was a step up with a numeric keyboard from a HP calculator and hexadecimal displays. I actually got it to work as a music synthesizer. This was my 1st computer, the 2nd was a 6809 based computer I built in 1984 with a friend at university with 64KB RAM! Note that this was in the days when you had to build your own computer. My high school was still trying to raise sufficient funds to buy an Apple II (?) computer in 1979, I remember making and running a stall at the carnival for fund raising which rang a buzzer if you thew coins onto a playing surface and were lucky enough to bridge 2 contacts. The stall "selling" teachers to throw water balloons and tomatoes at made a lot more money.



So by end of year 7 at high school I had given up on a career as an industrial chemist, and decided on either physics or computer science. I had realised by then that electronics was a poor mans computer and that programming was the future. If you could program a computer you didn't need to mess around with circuitry and a soldering iron each time you wanted to change your program to do something new and different.

Comments

Post a Comment

Popular posts from this blog

Chapter 11: AWS Directory Service, Cloud Directory

Image
"Name or Number please?" So the 1st telephones systems were point to point, and then hub and spoke. You rang the local exchange, asked to talk to Auntie Jill and the "operator" (think the Matrix) would ring Auntie Jill's phone and connect you (literally with a patch cord) once Auntie Jill had answered. If you wanted to talk to someone not on the local network the operator would call another operator (how did they know which one?) and ask to them to connect and you would eventually get patched through. This was even more fun if you wanted to ring someone overseas, as you would hear the patchwork of operators, some speaking foreign languages (what fun), the the sounds getting fainter and weirder (lots of clicks, "undersea" sound effects like talking down a tube, echos, etc) until finally you heard Auntie Jill's voice saying "hello?" and you could talk to them (which was expensive, and the operators would sometimes break in and say...
Read more

AWS Solution Architecture Certification Postscript

Image
So I sat the exam today and past ok yippee. Guess there's no need to continue blogging about AWS certification stuff!? The AWS Certified Solutions Architect – Associate exam is intended for individuals with experience designing distributed applications and systems on the AWS platform. Some general observations. The real exam is somewhat harder than the practice tests and practice exam (about 10% harder?) NONE of the practice test questions appear in the real exam. The focus is only what I would call the legacy IaaS Amazon services. Almost no questions on managed services, Machine Learning, Data Analytics, Lambda, etc. Lots of questions on what I would call systems and networks admin stuff.  I spent a few months trying to learn this stuff but actually I don't think it helped, I'm not sure I got any of these questions right. E.g. the sort of qns were if you have this sort of set up (VPCs, subnets, ACLs, groups, EC2, etc) and this doesn...
Read more

Chapter 2: Amazon Simple Storage Service (S3) and Amazon Glacier Storage (for storing your beer?)

Image
Chapter 2: Amazon Simple Storage Service (Amazon S3) and Amazon Glacier Storage The Amazon Glacier Storage Service is designed for cheap long term archival storage, so you want things to stay put in it for a long time. It is a slightly odd choice of name these days given that global warming is a significant threat to Glaciers (Glaciers are "shrinking" and large dangerous chunks are falling off them as in the above image of the warning signs at a famous New Zealand Glacier (Franz Josef Glacier).  Maybe the Amazon "Glaciers" will be the only ones still around in a few 100 years. I initially found it "odd" that the AWS Solutions Architect Certification book introduced storage services before compute services.  However, in hindsight this sort of makes sense as S3 is one of the original services, is core to other services, and introduces many of the AWS concepts, and is a "managed" service so it simpler and more typical in some respects. ...
Read more