Live data from Hacker News

Letter to a young programmer

neopythonic.blogspot.ca

21–30 of 32 posts

Re: Letter to a young programmer

#21
post #14

As a young programmer, I cannot be more lucky than this. Right now, you can learn virtually any programming language (such as Python), online, so the fact that I'm not old enough to get a college degree doesn't matter.

And that you can actually communicate via email/twitter/g+ with the creators or the core developers of those languages and expect to even get an answer is pretty awesome as well :)

Re: Letter to a young programmer

#22
post #10

Python was my third language; I wish it had been my first. It's just so fun to write and wonderful to look at. C (my first) is also fun to write, but not when you're young--not as much as Python is.

I remember having lots of fun with C as a teenager. This was in the early 90s. We wrote games and demos using mode 13h (320x200 1 byte/pixel) in DOS (thus pretty much bare metal).

Those were the days. I think it was the perfect way to get started with programming :-)

Re: Letter to a young programmer

#23
post #19

When I taught Python to my kid and a few other kids that live around my house a coupl of years ago, Guido was gracious enough to sign these head-shots for me to give to each kids as their graduation present. https://plus.google.com/photos/108306457281321389001/albums/...

Can't see the photo on mobile - Google tries to push some download, then muffs up the URL, resulting in a 404.

Try https://lh3.googleusercontent.com/-SCL-9OjK6NM/TBJJmht0dPI/A... , I am not sure if that is an expiring link.

Re: Letter to a young programmer

#25
post #24

Point of fact: computers aren't really getting faster anymore. Well, phones and tablets still are, but desktops and servers? Not so much.

Single CPUs don't, but the number of cores does grow. GPUs are also worth considering here.

What does not get faster is programs written for old architectures. 20 years ago the best way to optimize a program was waiting a decade. That won't work today, and to make programs future-proof they have to scale to a lot of threads.

Re: Letter to a young programmer

#26
post #14

As a young programmer, I cannot be more lucky than this. Right now, you can learn virtually any programming language (such as Python), online, so the fact that I'm not old enough to get a college degree doesn't matter.

And before then, we had the public library! Good ole ANSI C FTW

The only Programming book in Coventry City library (where I'm from) was a 10 year old COBOL book.

I now know COBOL.

I've always known COBOL; before I knew linux, I knew COBOL.

not sure how that effects my mentality be, but, I would say that it's lack of structurability has rubbed off on me largely.

Re: Letter to a young programmer

#28
post #10

Python was my third language; I wish it had been my first. It's just so fun to write and wonderful to look at. C (my first) is also fun to write, but not when you're young--not as much as Python is.

I remember having lots of fun with C as a teenager. This was in the early 90s. We wrote games and demos using mode 13h (320x200 1 byte/pixel) in DOS (thus pretty much bare metal). Those were the days. I think it was the perfect way to get started with programming :-)

You can still play around with computers like that! In fact, just `pacman -S qemu` and you're set! Mode 13h is awesome. I wrote a little quine[1] in x86, using mode 13h.

[1] https://github.com/jdiez17/quines/tree/master/bootable_quine

Re: Letter to a young programmer

#29
post #27
post #24

Point of fact: computers aren't really getting faster anymore. Well, phones and tablets still are, but desktops and servers? Not so much.

What makes you think they aren't getting faster?

Software is slowing down faster than hardware is speeding up. My work desktop takes somewhat over 5 minutes to boot; at 3.4 GHz and 4 cores, 5 minutes equates to almost exactly four trillion operations, which accomplish nothing at all WRT productivity. Of course most of the time is spend waiting for IO rather than actually calculating anything.

Years ago, four trillion instructions processed would have accomplished something powerful, something business critical. Now all it means is you've booted up.

The end user doesn't care about a waveform inside a box, all they know is computers are slower and less productive than ever.

Re: Letter to a young programmer

#30
post #25
post #24

Point of fact: computers aren't really getting faster anymore. Well, phones and tablets still are, but desktops and servers? Not so much.

Single CPUs don't, but the number of cores does grow. GPUs are also worth considering here. What does not get faster is programs written for old architectures. 20 years ago the best way to optimize a program was waiting a decade. That won't work today, and to make programs future-proof they have to scale to a lot of threads.

s/threads/cores/g
Post reply on HN