Live data from Hacker News

On Getting Older in Tech

corgibytes.com

61–70 of 440 posts

Re: On Getting Older in Tech

#61
post #38
post #19

Earlier quoted context omitted.

I find that - very broadly speaking - old guns are better at strategy and young guns are better at tactics. The energy and interest of the young lead them to find the local maxima more readily, and the experience of the old help you find the real maxima rather than the local. Or put another way, young'uns will get you out of the rabbit-hole more quickly, but old'uns will take you down fewer rabbit-holes. Both mindset…

Would you mind expanding a little bit more, from your perspective, on what falls into tactics and what falls into strategy?

Generally what marklgr said. By tactics, I mean being up to date with the latest lib for -foo- and being on top of what the cool kids are doing, chasing down the rabbit-hole to find that one setting to improve db performance. Individual, almost atomic tasks, especially those in a changing landscape.

Strategy is more about planning, forethought, and knowing ahead of time which avenues are worth pursuing and which aren't. As a very simplistic example, a tactician might spend a day down a rabbit-hole and improve a db's performance by a small but significant amount, and a strategist would not have spent that day, knowing that that db is going to be turned off in two weeks. Not the best example, really (and it implies that you're only one or the other, which isn't true at all). There is also overlap between the two.

Perhaps a military analogue - tactics is about how to take the forts (shorter timeframes, clearer objectives, obvious goals), and strategy is about determining which forts are worth taking (long-term timeframes, murkier objectives, sometimes unclear goals, concern for secondary effects). The difference is also in scope, I guess. Being a good tactician benefits from energy and focused interest, something which the young'uns tend to have more of (caveat, caveat), and strategy benefits from forethought and experience, something which the old'uns tend to have more of (caveat, caveat, &c)

Re: On Getting Older in Tech

#62
Related to fitness. I never went to the gym. However I was working on fitness related site for some years and as a lead there, I wanted to be reflection of this site I cared much about. So I did what I like, walk and running up the stairs.

Whenever there are stairs, I would run up them. Now, again I am not super fit, but I don't lose breath, everyone else kind of does. This gives me great pleasure.

I am older developer, it is getting hard, I will not lie. But, I am on top of latest technologies, enjoy my work, I am pain in the but.

Re: On Getting Older in Tech

#63
Well, if the author is almost 60, it probably won't matter which career he's in, he would likely suffer from some sort of ageism. It doesn't matter if you're a programmer, or in finance, or working at Costco, if you're getting close to 60, most people will be skeptical as to whether you can really work as well as a 25 year old.

Re: On Getting Older in Tech

#64
about the value of experience, I had it explained to me like this:

  If you see a toddler running after a ball that rolls under a coffee table, bending over to go under the table and 
  to pick up the ball... 
  You know what's going to happen next. That's experience.
  There are just different balls and coffee tables.

Re: On Getting Older in Tech

#65
Ageism is real in the Vally but it can cut both ways. In my current company we did a SWOT analysis and one of our advantages was "many old farts, and many former colleagues friends".

Yes, if you haven't been using AWS and GPGPUs you will be of minimal use to us but it's really valuable if you have already made a bunch of mistakes on someone else's dime. And in your 50s you're probably an empty nester, and can easily put in a 50+ hour week when necessary (which it often is, but not all the time, in a startup) and get more done in 40 hours than the squirts do in 60+.

You need a mix of ages and backgrounds. A bias to youth is as bad as a bias towards time-in-grade, or any other such bias.

Re: On Getting Older in Tech

#66
post #55

One of the things that has made me old (52) and crotchety is that I learned Lisp very early in my career. That gave me the ability to see that 99% of "new" technologies were really just poor re-inventions of (parts of) Lisp. Even today, Common Lisp -- despite (or, as some would argue, because of) the fact that it hasn't been officially updated in decades is still not only a viable language but one of the best choices…

Out of curiosity what flavor/dialect of LISP do you recommend? Common or something else?

Re: On Getting Older in Tech

#68
post #44

> let’s look at the average age of IT workers at well-established companies. Facebook: 28. LinkedIn: 29. Google: 30 I had an interview at Google a couple months ago and noticed that most people were pretty young. When I asked the person who was in charge of taking me to lunch about this, he said that it's probably because there are just much more graduates of CS now than there were before, and that Google would very…

His reply couldn't sound more scripted

Re: On Getting Older in Tech

#69
post #44

> let’s look at the average age of IT workers at well-established companies. Facebook: 28. LinkedIn: 29. Google: 30 I had an interview at Google a couple months ago and noticed that most people were pretty young. When I asked the person who was in charge of taking me to lunch about this, he said that it's probably because there are just much more graduates of CS now than there were before, and that Google would very…

Also Atlassian says the same. They said last week that they just can't get senior people in Sydney. Personally I feel older people are not as good at the little puzzles they set as an entry test.

Re: On Getting Older in Tech

#70
post #55

One of the things that has made me old (52) and crotchety is that I learned Lisp very early in my career. That gave me the ability to see that 99% of "new" technologies were really just poor re-inventions of (parts of) Lisp. Even today, Common Lisp -- despite (or, as some would argue, because of) the fact that it hasn't been officially updated in decades is still not only a viable language but one of the best choices…

Isn't there a good big comnunity in Clojure now?
Post reply on HN