Ask HN: Software development after 40, how do you keep the fire?

#1

Post by m3mpp » Mon, Aug 20, 2018, 2:46 PM UTC

Experience is a nice thing, most of the time. We can see through the BS and concentrate on important things to make up for a slower brain, less stamina and decreasing memory, to a point where I think I am as productive, maybe even more, than I was 20 years ago.

The negative consequence of experience though, in my case, is I'm less excited about new ideas, more skeptic in general, which makes it more difficult to find the motivation that is needed to build something really significant.

And I mean, it's not very surprising, if you haven't made it big at 40+, that means you worked on a lot of failed projects, that makes it harder to believe you can change that.

Maybe some older folks here on HN, but younger people comments welcome too of course, could share their point of view on that question?

Re: Ask HN: Software development after 40, how do you keep the fire?

#2

Post by itamarst » Mon, Aug 20, 2018, 2:52 PM UTC

I'm 38, but started working young, so probably equivalent.

1. These days I care a lot more about what the software is for, what makes it useful. So I don't need to get excited about trendy technology, I get excited about e.g. building a completely new kind of gene sequencing device that will help disease research and diagnosis. (Write about this here: https://codewithoutrules.com/2017/08/07/do-something-useful/)

2. Teaching is great, because it means all those failures weren't for nothing. Someone else can learn from them (I write a weekly newsletter of my mistakes and how to avoid them - https://codewithoutrules.com/softwareclown/), and I can learn from them (https://codewithoutrules.com/2017/10/10/lone-and-level-sands...).

3. At this point you can hopefully get better sense of _why_ project fails, and avoid things that are likely to fail, or try to prevent them from failing. So hopefully % of failures goes down.

Re: Ask HN: Software development after 40, how do you keep the fire?

#3

Post by PaulHoule » Mon, Aug 20, 2018, 3:21 PM UTC

It is a common story to see a bunch of young brogrammers on the west coast build something big and ambitious and then have it fall flat on its face. (For instance, GE Predix)

You might have to fight every bit of the way, but with experience you can save this kind of group from itself, or at least help them have a plan B that works when plan A fails.

Re: Ask HN: Software development after 40, how do you keep the fire?

#4

Post by m3mpp » Mon, Aug 20, 2018, 3:30 PM UTC

itamarst wrote: post #2

I'm 38, but started working young, so probably equivalent. 1. These days I care a lot more about what the software is for, what makes it useful. So I don't need to get excited about trendy technology, I get excited about e.g. building a completely new kind of gene sequencing device that will help disease research and diagnosis. (Write about this here: https://codewithoutrules.com/2017/08/07/do-something-useful/ ) 2.…

1. definitely a great advice, work on something greater than oneself.

For 2 and 3, not so sure, it's so difficult to say, I've seen a lot of shitty things becoming successful, and some real good things never amounting for anything over the years, that I'm real cautious about doing any kind of prevision nowadays... The old "the more I know, the more I realize how ignorant I am" thing.

Re: Ask HN: Software development after 40, how do you keep the fire?

#5

Post by dmitripopov » Mon, Aug 20, 2018, 3:32 PM UTC

I'm 39, still as excited about new ideas as 20 years ago. Or even more. It's so simple to implement new ideas nowadays, just pick a matching tool/framework and you are good. Back in 1998 you were forced to write a lot of things from scratch long before you get to your idea implementation and it was actually demotivating, at least for me.

Re: Ask HN: Software development after 40, how do you keep the fire?

#6

Post by m3mpp » Mon, Aug 20, 2018, 3:41 PM UTC

PaulHoule wrote: post #3

It is a common story to see a bunch of young brogrammers on the west coast build something big and ambitious and then have it fall flat on its face. (For instance, GE Predix) You might have to fight every bit of the way, but with experience you can save this kind of group from itself, or at least help them have a plan B that works when plan A fails.

Yes, save some, destroy inspiration in some others too, experience can do both, don't you think?

Re: Ask HN: Software development after 40, how do you keep the fire?

#7

Post by shove » Mon, Aug 20, 2018, 3:41 PM UTC

"I'm always angry" -- Hulk

Re: Ask HN: Software development after 40, how do you keep the fire?

#8

Post by edw519 » Mon, Aug 20, 2018, 3:46 PM UTC

...to make up for a slower brain, less stamina and decreasing memory...

This is NOT normal and should not be accepted as such.

I'm 63 and have been programming professionally for 40 years. I'm currently working on several projects that are as complex as anything I've ever done. I honestly feel that that I get better every year, build stuff I never imagined a few years ago. I know this is subjective, but I feel like my brain is faster, I have more stamina, and better memory than ever. I still do newspaper jumbles and crossword puzzles without a pencil and plan to continue that way indefinitely.

Unless you're managing a serious medical condition, I suggest you do something differently: eating, exercise, lifestyle, medical care, something.

To you kids out there (under 50), do not despair. The best could be yet to come if you make it that way.

Re: Ask HN: Software development after 40, how do you keep the fire?

#9

Post by alex_lod » Mon, Aug 20, 2018, 3:47 PM UTC

Have you heard of the concept “beginner’s mind?” It’s an attitude that can be developed with practice that helps you see otherwise ordinary things with awe and curiosity. Here’s a bit more about it: https://en.m.wikipedia.org/wiki/Shoshin if you’re curious I can share more references.

Re: Ask HN: Software development after 40, how do you keep the fire?

#10

Post by return_True » Mon, Aug 20, 2018, 3:55 PM UTC

I think you have a lot of questionable assumptions, which leads to your original question.

First, at 50 my brain has not 'slowed down'. Nor has my zeal for new tech, learning or stamina.

Made it big? Not sure what you mean by that, but I've had a very rewarding career (almost 20Y in the same place) that has provided me consistently with challenge and success.

Last thought, I'm part of a team of devs in our early fifties. I feel like with our experience, maturity and honed skills we could wipe the floor with a team in their twenties if we wanted. Might just be us. Just MHO though.