8 ms·
Do you want to be making this much money when you're 50? (2012)
- sombremesa 5y agoTFA is commentary, the real article I was looking for is the first link in TFA. The original question isn’t about money at all. In any case, what I want to be doing when I’m 50 is rather irrelevant. When I was 10 I wanted to be a pilot, but that desire went away before I turned 15.
- reidjs 5y agohttps://prog21.dadgum.com/154.html https://prog21.dadgum.com/154.html
- mikestew 5y agoStill choosing shitty places to work when I'm 50? No, hopefully I have exited that phase in my life. Or did the author mean something else when they typed "doing this"?
- milesvp 5y agodadgum is a treasure of insight. I think I’ve read every blog post on the site (and was sad when he stopped posting). I highly recommend you read the article, he’s talking about software development and the types of headaches you’ll find at just about every level of the stack.
- reidjs 5y agoI wish I read this article in 2012. I enjoyed programming, but never considered it a career. It was my passion, I didn't have any expectation or desire to make money from it. "passion burns out, whereas greed is sustainable"
- JohnFen 5y ago> "passion burns out, whereas greed is sustainable Boy do I hope this isn't true. I'm driven in my career by passion, not a desire for income (I've never been particularly money-motivated -- not saying that's good or bad. It's just how I am.) If the passion burns out, so does my whole career.
- mikewarot 5y agoThe thing that scares me about jumping into programming today is that you realistically can't know all the layers any more. My programming experience was writing a program, and a few libraries that went with it, from scratch, in Turbo Pascal. I knew how my code worked, and the run time libraries were simple enough that they really never caused any issues. I also spoke with most of the users of the program, personally. Now you're expected to write "apps" that run in some random mobile platform, with almost no feedback when things break. You're depending on layers upon layers of abstraction to make everything work, it's like building on sand. On the other hand, as pointed out, it's like that in other occupations as well. We programmers do have a choice, however. It doesn't have to be, though. We could simplify things and remove some of the cruft.
- mips_avatar 5y agoThere was always some layer of abstraction. It’s just the ISA is a more elegant abstraction than a mobile platform is.
- commandlinefan 5y ago> with almost no feedback when things break It was kind of like that back in the days of "shrink-wrapped" (even if it wasn't really shrink wrapped) software, too, though - I remember trying to debug problems that were specific to a particular environment on remote computer users computers before the internet. At least with apps you can build in some sort of telemetry. But yeah, things are way more complicated than they used to be, and it takes a lot longer than most people appreciate to go from zero to productive.
- oconnor663 5y agoI think there's a lot of truth to this, in that it's good to understand all the layers below you. But there's also some truth to the opposite: Did anyone ever really understand all the layers, or even most of them? Even if you knew all the details of how your microchip worked (weren't those details usually proprietary?), you might have wanted your code to work on other chips, or even on future versions of your current chip. At some point, we always have to close our eyes and abstract away parts of the problem behind the contract we believe those parts will follow.
- wil421 5y agoNot sure I want to be programming forever but I’d like to manage software engineers until I retire. Hopefully in the near future I’ll be able to do it and my boss recently asked if I still wanted to manage people. Still love programming and will continue to do some python programming around the house and tinkering with my Raspberry PIs but I’ll probably say adios to JavaScript.
- whoomp12342 5y agomake sure you keep a foot into dev in case you change your mind!
- zwieback 5y agoI'm 55 and still a programmer. However, in my job I also do other stuff like mess with sensors, cameras, motors. Early on in my career I realized I loved programming but not in a pure SW company. I did make the conscious decision to never become a manager of any sort, that's really hard and I wouldn't be very good at it.
- Koshkin 5y agoAlas, I have been promoted to the rank of the "clueless,"[0] but I am happy that I am able to continue doing mostly programming work as before. [0] https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-or-the-office-according-to-the-office/ https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-...
- giantg2 5y agoSome of this isn't necessarily true. There can be health risks. This is a very sedentary job with a lot of eye strain and stress. There can be legal risks, like with HIPAA or even other more basic things. You do generally need a college degree for most places to even consider you. I don't make money to the point of it being addicting. I do dream of quitting, but there's not a lot of interesting stuff out there.
- jvik 5y agoI quit programming after 3 years because I can't stand the leetcode interviews which all programming jobs suddenly require in my area.
- zsmi 5y agoI'm a bit confused. If you had a job, why were you interviewing? Or did you resent giving them?
- jvik 5y agoMoving closer to family so I need to change job. Applied to quite a few programming jobs in the nearby city. After probably 10-15 unsuccessful technical interviews with leetcode I've decided to go back to IT. Now that I have kids and a house I don't want to spend hundreds of hours to learn this completely separate skill (leetcode) that I rarely if ever will get to use in my job and get no joy from.
- vmception 5y agoI had a similar experience in my last dance with interviews. Even when I got good enough to solve some easy/medium problems in interviews efficiently and faster than the average, I was still getting rejection letters. Kind of a waste of time when you can make so much solo these days, but interviewing is distracting because its like a full time job, while competing against the most driven people from Asia who trying to stand out against a very large population, while I'm just casually looking for a signing bonus for the year. Basically the only data I have is that there is just a cap on what people are willing to pay me as an employee. Like they think much harder about approving me, than seems warranted. I start to think hmmm maybe I shitposted something on social media that nobody will tell me about. But when I go down in asking comp range, the whole experience is completely pleasant and familiar again. That's kind of annoying. Makes me want to pay fees to professional groups under the hope that they can bus me though. Seems similar to stories I've read about random athletic clubs at Stanford all joining the same team at Facebook.
- 5y ago
- suyash 5y agoIf you love programming for the sake of programming, better to keep it as a hobby or side thing. When it becomes full time job, specially in a legacy code base, all the fun goes away.
- lliamander 5y agoProgramming actually started as just a professional activity for me, and then only became a hobby after I was good enough in it.
- heleninboodler 5y agoI disagree with this, from the perspective of someone who really just loves the constant learning and puzzle-solving aspects of programming. I've been doing it for over 30 years and I feel incredibly lucky to have people throw heaps of money at me to do what I enjoy, plus I still work on side project code a few times a week minimum. I even procrastinate programming tasks I don't want to do with programming tasks I do want to do. It's pretty amazing.
- the_only_law 5y agoUnfortunately the thing I enjoy and the thing people pay me to do are radically different
- allenu 5y agoI'd love to see a survey of what developers do as they age, how many leave the industry, why, and to do what. I'm 43 and I'm the oldest person on my team by around 5-15 years. My manager is younger, my coworkers are younger, even my manager's manager is younger. Earlier in my career, most people I worked with were older than me, which makes sense, but what happened to all those people? Did the industry just expand so much that I can't find them? Or did I just join a company that attracts younger devs? I know for me, I'd like to still be programming when I'm 50, but I'm already souring on the "working in a medium to large company" aspect. The coding is still fun, and the money is great, but the process of making software in the context of a corporation isn't.
- teddyh 5y agoThere is a case to be made that since the number of programmers are increasing to the point of approximately doubling the number of programmers every five years, every old programmer could still potentially be active in the field, but constantly be more and more obscured by the ever-increasing mass of new programmers, and all the programmers you see around you should have on average less than five years’ experience. In other words, nothing happened to those older people, except that they are now dispersed among an ocean of new programmers.
- lliamander 5y agoA lot of the economics around software and programming are going to change as that rate of growth slows.
- jonfw 5y agoWe will see. One thing programmers have always seemed to be really good at is producing more work for programmers :)
- codetrotter 5y ago> the number of programmers are increasing to the point of approximately doubling the number of programmers every five years Like a Moore's Law but for computer programmers.
- hereforphone 5y agoI'm a middle-aged programmer. I read only the beginning of this article and I didn't want to continue. "- little or no required education": maybe, but only for the rare prodigy. "Software engineers" without an understanding of math and some amount of formal computer science are necessary evils rather than assets. Or are doing low-level, low-thought work. "- No health or legal risks": a software engineering career will mess your body up bad if you don't intentionally work against that. For those of you who are young and don't believe me (and are programmers, sysadmins, devops, or otherwise spend all day on a computer), come back to me in a decade or so.
- paulpauper 5y agoI have been doing computer work for over a decade. no discernible health effects. That could change, but I would say it is less risky than a manufacturing job. The data clearly shows that some jobs have a higher risk of occupational injury than others.
- hereforphone 5y agoAre you 1) pretty young or 2) pretty physically active otherwise?
- Koshkin 5y agoGood for you, but wait till it's been 25.
- heleninboodler 5y agoIt can come on quickly. I'm at over 30 years experience now and once, about 11 years ago, my shoulder just started having this shooting pain almost immediately whenever I sat in typing/mousing position. It was kind of terrifying. At times, it was so bad that I legitimately thought that I might have to give up sitting at a computer. I ended up investing in a better chair, focusing on better posture, taking breaks, doing exercises, and also switching my mouse to the left side for about 6 months (the pain was in my right shoulder and was particularly bad in the mouse position, so I thought learning to left-mouse would be a good idea). Ultimately, it worked out, but I had to make some pretty serious changes to make that happen, and now that I'm in the better habits, I wish I'd made the change much earlier.
- lliamander 5y agoI definitely want to keep making this kind of money, and if anything problems like stress have actually become less of an issue as my pay increases. Jobs that value programmers tend to understand how best to extract value from them (and death marches generally aren't it). I also agree that the lack of older programmers has more to do with the growing number of new programmers than with attrition of older programmers (though certainly that does happen as well). The main problem I think programmers face as they approach 50 is the "half-life" of their knowledge and skills. So much of the frameworks, platforms, etc. that we use will become obsolete in 5 years. Very little of what we have learned now will still be relevant in 20-30 years. Other professions have this problem as well, but I think few have it as bad as programmers. It is possible to stay on top of the latest trends, but that requires some degree of fluid intelligence, and that begins to decline after your mid-twenties (though you can delay that decline somewhat by staying physically active). Crystallized intelligence, on the other hand, lasts well into your 60's. It's therefore in our best interests to make sure we learn knowledge and skills that have a longer half-life.
- robotnikman 5y agoAnecdotal, but where I work, I noticed most of the older programmers are working on systems like AS/400. Makes sense though, many such systems are still running and functional in many businesses, and they have a skill that few have nowadays. From what I've gathered from talking to them, IBM still provides regular updates for these systems, and while change is slower than would be experienced by a web developer, they still are learning and adapting to changes made in these updates, and have to adapt to interfacing with new technologies adopted by other areas of the business.
- lliamander 5y agoI tend to leverage the Lindy Effect in determining which skills and technology are worth learning: if it's been around for a long time, it probably will continue to be around for a long time more. There are other reasons why I personally might not choose that route, but that longevity is an advantage.
- 5y ago
- mberning 5y agoThe money is addictive. But so is the “working on cool new shit” aspect of it. I know quite a few engineers that bounce around from place to place to scratch that itch.
- mberning 5y agoI realized about 5 years ago that I definitely don’t want to be doing this when I’m 50, and I don’t want the money to be the reason I keep doing it. Started getting very serious about income investing aside from my 401k/retirement account. My hope is over the next 15 years I will hit a point where “pretirement” will become a very real possibility.
- zz865 5y agoI always thought there would be a huge surplus of programmers soon. The recent wage stagnation (outside SV), lots of h1bs and bootcamp craze seemed to bring on a new wave of people that was going to prove my view. But right now there is still a shortage of devs and pay is growing, I dont understand it. It has to stop some time.
- teddyh 5y ago“The market can stay irrational longer than you can stay solvent.”
- deleted 5y ago[deleted]
- AnimalMuppet 5y agoSay you have 5 years of experience. Bootcamps can't create people with 5 years of experience. (They can five years from now, but by then, you'll have 10 years of experience.)
- DangitBobby 5y agoBased on purely anecdotal experience, I think bootcamps aren't necessarily putting out productive entry-level developers. We briefly hired someone as an entry-level web developer who would talk a bit about how he was teaching some web programming classes in the evenings (at the bootcamp he just graduated from). He did not have the knowledge to be to be teaching classes. We had to let him go. We have hired several entry-levels from state schools who have been very successful with us, by comparison.
- paxys 5y agoBy 50 my ideal career would be "retired", with enough savings and passive income (from investments or whatever else) to sustain a good lifestyle for me and my family. Plus, who knows how long this software gold rush will actually last for. It may not remain as lucrative a career as it is now. While I generally like my job, I sure as hell hope I don't have to spend the next 20 years of my life attending standups and updating Jira tickets.
- mikestew 5y agoPlus, who knows how long this software gold rush will actually last for. I make no claim of knowing, but developing software has paid well at least back to the late 70s, certainly into the 80s when I started. Not the ridiculous amounts some make now, but it has always (always == "within in the working years of those reading") financed an upper-middle class lifestyle in the U. S. I have no reason to think it won't continue to do so within my (albeit, short) remaining working years. As for the topic at hand, many of the comments strike me as not appreciating what we have. You want to know what I don't want to be doing when I'm 50? Being an auto mechanic, which is what I did a long time ago. At least one person complained that writing software wrecks your body or some crap. Man, go talk to anyone that does any kind of physical labor for a living and see how much sympathy you get. I mean, those complaining aren't wrong, but go talk to a mechanic, nurse, or any similar job that folks will work well into their 50s, see how much sympathy you get. Complaining about Jira tickets sure won't garner much. :-)
- jjav 5y ago> spend the next 20 years of my life attending standups and updating Jira tickets What's frustrating is that this is self-inflicted damage from agile. The first not-quite-20 years of my career there were no standups, no jira-centric workstyle (we had bug trackers of course, but day to day work didn't revolve around that the way it does with jira). Work was so pleasant, solving interesting technical problems and making the product better, just like hacking at home on personal projects. Work doesn't have to be sprinting from status report meeting to status report meeting. It never was that way before agile. I've largely opted out of day to day programming just to avoid that unpleasant madness. But I miss it and wish I could go back to exciting hands-on programming every day, without the agile headaches.
- deleted 5y ago[deleted]
- _ah 5y agoIt's not the making of money that's addictive, it's the spending of money. It's easy to forget, but remembering this fact results in a wider range of life options.
- mooreds 5y agoOne of the things I love about being a developer is the sheer variety of tech adjacent jobs. I've been a developer for about two decades (in my mid 40s). In the last half decade I've worked through some other adjacent careers. Since 2016, I have: * been a startup CTO (a pre-seed startup) * a technical trainer (to help pay for, well, eating, as I was building the startup * an engineering manager (player-coach, too small a team for me to only do people things) * developer advocate (writing, speaking, documented, example apps) * book author (don't do this for the money, but writing deeply on a technical or engineering related topic is a fantastic experience, as it forces you to justify things that you might have been handwavey about in your mind) All of these involved some programming, but none of them were 40+ hr/week of development. This is one of the other reasons to love software development. I know a few developers in their 50s and 60s that are programming near full time. Some have moved from company to company, but a lot more have hunkered down at a place where: * the work is steady, but not glamorous * they trust the management That's where I suspect many of the older devs have gone: to quiet, safe jobs where they can do their work and trust their management to do theirs.
- indigochill 5y ago> * they trust the management For me this is the silver bullet. I'm only in my early 30s, but corporate management is a mixed bag so if there was a company where I actually had faith in the management, they'd have me for life. That said, I'm coming up on a 10-year tenure already (not always programming, but different roles within the same company), so it's not all bad.
- totally 5y agoI started reading and thinking that 50 is old, and then I realized that I'll be turning 41 soon enough. So, yeah.
- PeterWhittaker 5y agotl;dr/BLUF: 55, recently returned to full time programming, loving it, going to keep at it quite a while. Longer version.... I was sort of a programmer 30ish years ago (programming was a small but vital part of my job, at best I was OK at it). Moved into management, then, about 20 years ago, cyber security consulting (PIAs, TRAs, governance structures, policies, PKI auditing, some bizdev, some product management, all in the cyber space). Just over a year ago, I converted back to full time wage slavery, primarily as a programmer, with a few other duties (hey, startup), and this after spending about 6 months mostly programming for the same co as a consultant. One month it's React and Node and graph DBs (for the compliance product), the other it's shell and C and C++ and SELinux (for the unidirectional gateway), rinse, lather, repeat. Lots of customer interaction, lots of iterating, no face-to-face or bum-in-seat unless I want to (or it's required for security purposes), lots of learning, lots of interesting problems. This stuff is great. Will I be doing this at 60? That will depend on the right balance between three things: My health, status of the profit share, and my ongoing interest. Just having too much fun right now.