Hacker News new | past | comments | ask | show | jobs | submit login

When he bought a computer, I asked my grandpa to show me how it worked. He said it wouldn't be interesting to me: it was all in English (which I didn't speak or read), and there was nothing more than letters and numbers to see, on a green and black screen. I told him that didn't matter. He took a book and we spent an afternoon typing Rabbit.BAS into the machine, then we played some.

That was 30 years ago this year, today I design aircraft simulators and automated test systems for aircraft computers. The methodology has never changed: aim high, with a goal you will enjoy a lot.

edit: to your second question, I have this to offer: there's nothing more I wish I had known when I started. I'm actually very glad I didn't consider theoretical questions too early. "Programming" is no different a language than Spanish, Japanese or Russian (maybe a tad more formal). To program you need to learn to give directives to a machine. Designing a system is something else, which uses a completely different skill set, and the entry point to that is being able to talk to the machine.

So my only advice could be: if you really want to be a hard-core computer nerd, stay with "programming" for 7-10 years, then learn (at least at overview level) all the important design principles. You'll then be able to choose according to your personality.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: