I got a Commodore 64 when I was eight and after the mandatory gaming I started to look at (Simon’s) Basic and the assembler. This time also involved lots of programs typed from the magazines. Next computer was Amiga 500 and with that I started getting into the intro/demo scene as I also had a 2400bps modem. I tried my wings as a graphics artist and as a music composer, but wasn’t too good at either, so what was left was coding.
Philosophy as a Programmer
Finding the actual problem from all the crud and solving just that with the simplest and most effective way possible is a skill that’s hard to teach. Having the guts to refactor a solution to best solve a given issue without resorting to countless kludges takes nerve. These are things I strive for. The assembler background also makes you care about performance and efficiency.
I made a promise to myself a long time ago: if someone shows me an easier or better way to do something, I will at least listen. I have seen so many people sticking to very old practices not because they’re the best but because they have never tried anything else. Things evolve all the time and if we’re afraid to evolve with the times we’ll be left behind. This doesn’t mean that we should be on the bleeding edge all the time, but at least be aware of what’s happening around us.