Live data from Hacker News

Pervasive myths about older software developers

lessonsoffailure.com

71–73 of 73 posts

Re: Pervasive myths about older software developers

#71
I'm 58, doing arcane mainframe systems stuff, mostly in my sleep. Pays well and got the kids through college, but I've been doing it for a long time.

The days are past when I could routinely wrap the clock on an interesting problem. If I did that now I'd be a zombie for a couple of days. Oh well: there aren't all that many interesting problems that come along in the day job anyway, so I make up interesting ways to solve the mundane problems. I wrote some REXX code not so long ago that builds and traverses trees to process an obscure many-to-many relationship in our database schema. One of my comments said that I was trying to see "how much of TAOCP I can remember".

If anybody ever looks at that code I'll bet a buck they won't know what TAOCP means.

None of the people at work my age know what HN is, and only one has ever even heard of Slashdot. Hell, I run the only Linux desktop in the whole enterprise - everybody else is plain vanilla MS-Windows. The kids who run the MS-Windows server farm, 20-somethings, have their own set of blinders on and if studying something doesn't lead to a Cisco or Microsoft certificate they won't bother with it. Young mercenaries, harumph. One of them admits to having heard about tomshardware so there may be some hope for him.

Sigh... nobody to talk to. I checked out a hackerspace in my area, but the kids there (don't mean that to sound pejorative, but I do have 30 years on them) were doing odd web hacks and Makerbot tricks and drinking cheap beer, none of which I found very interesting.

So I take out my creative frustrations at home, hacking at my personal machines. My darling this past year has been Clojure, and going to the Conj back October was an exciting thing. I kept up pretty well and discovered I wasn't quite the oldest guy there, so I haven't gone completely stale.

Have to pay a bit more attention to my body than I used to; I was immortal when I was 24, but now I've got those wrists and my liver to take care of.

(Man, they can't get those telomere therapies going fast enough.)

Re: Pervasive myths about older software developers

#72
post #14

One thing that I think hasn't been recognized by popular engineering culture is that the guys who started programming in the 1970s had a lot less to work with, and had a harder time. They often worked in assembly, and a soldering iron was a legitimate debugging tool. Those who started programming in the 1980s had compilers but languages were something you went out and bought, and they were sold like enterprise softwa…

I half agree with you. We are working at a much higher level of abstraction these days and the skills required have changed, but I don't think its any easier.

Part of my electronics degree (in the early 90's) involved programming a controller in hex through a 18 key keypad. Not quite card punching, but the screen display was just 2 characters. There was no editing - you had to start from scratch if you made a typo. It might sound a bit geek-macho but actually it wasn't difficult - just awkward. And you didn't need to worry about which text editor you used, whether the source control plugin was compatible - you just worked with what you had.

In the 80's it was still possible to thoroughly understand the electronics, the assembly language AND write your own programs in C.

Now, a web developer has to understand networks, databases, multi-tier architecture, ui design (not to mention the complex dev tools). It's still a big spread, but each of the fields is much deeper so we have to make do with a working knowledge in all these areas rather than "complete" knowledge.

Today's graduates probably dabbled at high school with web page design, photoshop, powerpoint and spreadsheets at high school rather than circuit boards and assembly.

Re: Pervasive myths about older software developers

#73

The one point of contention I have with the article is about older programmers 'thinking more slowly'. This is again reiterated in the comments below the article. This is not true, we actually learn faster as we get older as long as we stay mentally active. In other words, we 'learn how to learn'. There are things that I can grasp now so easily that eluded me when I was 20. If you can't think faster and learn easier…

(I'm nearly 40)

Sometimes "thinking more slowly" is just "thinking more" before diving in. And often, past experience makes it a lot easier to grasp similar new ideas.

But ignorance can also be an asset sometimes - it can allow you to evaluate ideas on their own merit without decades of baggage.

Like the OP said, you want both on your team (just like lawyers have).

Post reply on HN