Live data from Hacker News

Do You Really Want to be Doing this When You're 50?

prog21.dadgum.com

171–180 of 260 posts

Re: Do You Really Want to be Doing this When You're 50?

#171
post #118
post #112

Earlier quoted context omitted.

Well, I'm going to get into the work of a real life programmer in a year or so, finishing my degree. Quite frankly, I wouldn't want to be sitting in front of a desktop for 33 years of my own life. Not to criticize you or anything. But coding my entire life, just doesn't feel right, well as of today and the classic cubicle/desk/chair environnement, maybe I didn't pick the right job, it just feels like a very individua…

1. Critizing # "Not to critize you or anything." 2. open source # the only way to contribute My quick & easy response is #137 of my ebook (see my profile): 137. How do you put your skills to good? I’ve always thought that the best way to put your technical skills to the greater good is through your day job, not instead of it. Some of my days jobs have been to write software to ensure that: - people get the right pres…

It is _tremendously_ inspiring to see that you can find such joy in things which are so very important (all of the things you listed) but which so many people would consider boring. It helps me put my own work in a better persoective. Thank you for sharing your insight and experience.

Re: Do You Really Want to be Doing this When You're 50?

#172
I'm 60 and have been programming for 44 years. This year I'm working on election maps for Google. I still like learning new languages - this year it's PostgreSQL and PostGIS, Go, Autohotkey (a very strange language!), and now TypeScript (not quite a new language).

One thing I get an odd pleasure out of is when other programmers use phrases and styles I came up with years ago. A recent example is the $ prefix on a JavaScript variable containing a jQuery object:

    // Set $test to a jQuery object and test to the DOM object
    var $test = $('#test'), test = $test[0];
I just saw someone explaining that on reddit last night and it gave me a smile.

Much longer ago, I coined the phrase "fire an event" back in the 80's when I was designing the VBX interface for Visual Basic (then called Ruby). Alas, not all the names I coined for that project survived: VB Controls were originally called Gizmos, which I thought was a much more fun name. But still it's neat to see people talk about firing an event.

Re: Do You Really Want to be Doing this When You're 50?

#173
It really depends on what you mean by "programming." Following some dullard's waterfall plan to put sludge data in one server into a database of sludge on some other server would make anyone depressed.

Writing books, consulting on multiple interesting projects, and being well-remunerated is a very rewarding way of making a living. Can't complain.

Re: Do You Really Want to be Doing this When You're 50?

#175

Earlier quoted context omitted.

23, programming for, what, 14 years, maybe? And I hope I still have as much fun when I'm 57. I can certainly imagine myself doing so, for much the same reasons; it is partially about the happy dance feeling when something I built works, but long-term happiness and satisfaction come from seeing it getting used. It's really, really cool to see someone's masters thesis and think "I helped make that!" or drive by an elem…

I think it makes more sense to start measuring from the time you started professionally programming ... so if the 57 year old parent has been programming for 33 years that suggests that he's measuring from when he left full time education (24). My apologies if you've been coding professionally since you were 9 though :)

Good point, but I'm not really sure how to judge that. I've been getting paid for it for about 5 years, but that doesn't encompass all the stuff that I've built that other people have found useful, which is the metric that I care about. So, 8-ish, maybe?

Anyway, the point is that I don't have 33 years under my belt, so maybe I'm wrong about how I'll feel in the future, but based on the experience I do have, I just don't imagine it ever getting old.

Re: Do You Really Want to be Doing this When You're 50?

#176

I know and have worked with coders in their 50s, even 60s. They were very much what I'd call 9-to-5 coders though. They were never given big, important or new projects but as a consequence were never expected to burn the midnight oil. The main thing that looks unappealing to me about being a hacker decades from now is the constant cycle of learning. I'm on probably my 3rd generation upheaval. I've worked on a daily b…

It's the learning new stuff that keeps it fun. (54)

Re: Do You Really Want to be Doing this When You're 50?

#177

I know and have worked with coders in their 50s, even 60s. They were very much what I'd call 9-to-5 coders though. They were never given big, important or new projects but as a consequence were never expected to burn the midnight oil. The main thing that looks unappealing to me about being a hacker decades from now is the constant cycle of learning. I'm on probably my 3rd generation upheaval. I've worked on a daily b…

It's the learning new stuff that keeps it fun. (54)

Re: Do You Really Want to be Doing this When You're 50?

#178
post #147

Earlier quoted context omitted.

It's OK, one day you will get over your insecurities and inferiority complexes, and not fear people who are capable and comfortable of working on a team.

Be sure to thank your employer for their insecurities and inferiority complexes with your next paycheck.

Being smarter than everyone else is awesome while it lasts. Be sure to come back in 20 and let us know how your plans worked out.

Re: Do You Really Want to be Doing this When You're 50?

#179
post #134

Earlier quoted context omitted.

Pretty cynical? You can have more or less autonomy in your life, that's very important. You don't have to be King to be your own boss; you don't have to be poor to be a cog.

I am a natural cynic, yes, but people tend not to pay you unless you are doing something that makes you a cog for some period of time. It's not a criticism you can just fling at someone when you don't know their context. An experienced software contractor who is picking and choosing their own jobs is still pretty autonomous. It's more about whether you can pick where you are a cog and for whom you are a cog, than whe…

Although I don't really use the word 'cog,' you are being uncharitable here; the word isn't completely meaningless and using it isn't "screeching".

The poster seemed to be distinguishing not on the basis of interdependence but on the basis of who has control over your life and the context of your work, and where the resulting profit would go. (This is, of course, my reading).

One part is your freedom. If you want to take a trip for a couple weeks once a year, or change your hairstyle or get a tattoo, and this is impossible because of company regulations unrelated to workload, this is coggy. Of course, everyone acknowledges that you have to work a certain amount of time and that if you are facing employees it helps not to have a swastika tattoo on your forehead, etc.

Another part is the alignment of what you are doing with your interests. If you are putting in 60 hours to pay the bills and learn a lot about SOAP on the way, that's coggy; it is not the same as choosing work that involves SOAP because it gives you a hard-on, which is less coggy.

Another part is what determines the broader role your work plays. Yes, everyone is doing work which fits into other people's wants (even the arctic explorer is playing to an audience somehow). But if you work for 8 months on something and it fails because customers hate it, you were still the one who chose that context - less coggy. It was trying an idea. If you work for 8 months and then it is permanently scrapped because the company came to a deal with Microsoft and your project was just a bargaining chip, that's coggy.

For the same reason, profits - if you are working in Hollywood and get paid an incredibly tiny amount for a hit movie because they got you with Hollywood accounting, that is coggy; it's less coggy if your profit is tied

Of course, this also means it's less coggy if you are taking on greater risk (financial, reputational, whatever). If you are very risk averse then you may prefer a coggier position. If you are very focused on one specialized skill, a less coggy position might force you to pick up other ones, so again certain kinds of people will rationally prefer coggier positions.

If the norm is for employees to be hired at low rates, dominated in every way possible, artificially hampered from building useful things, and fired on a dime, that is pretty coggy. If you are happily choosing your own jobs, leaving when you want, dictating terms, that isn't very coggy. Which is why you used it as your example.

Post reply on HN