Do you want to be doing this when you're 50? (2012)
162 comments
·February 22, 2025rnd_dude428673
tailspin2019
I want to be you when I grow up :-) (And I’m not that far behind!)
I don’t ever want to stop learning and building interesting things with technology, and helping people use that technology for productive and useful outcomes.
The thing I definitely don’t want to be doing when I’m 50, or even next year, is work for a large morally corrupt organisation or a tyrannical boss who’s values are not in alignment with mine. And I guess that also means not working for a company where the work implicitly takes priority over living a balanced life (as described in the article with the 2am working to a deadline fuelled by Starbucks).
I don’t mind working until 2am on my own projects - where I have the autonomy to decide to do that - but not “under duress” for someone else, not like that anyway. And not in a team where the culture promotes that, such that I might get absorbed in that way of working and fool myself into thinking that I have chosen to live and work that way (a mistake I’ve made in the past).
I think self-employment therefore is the way for me. I’m there now, not making as much as my previous employment, but not compromising my values as much either - and right now at least the latter feels more important than the former. I just get to build cool things with people I choose to work with. I think that’s sustainable.
ralphc
I'm 63, retired in 2017 when I was 55. I now work on projects that interest me in languages that interest me. As a senior senior I'm excited by AI in my editor, it's automating the boring parts and I mainly just get to think of solutions.
I'm loving it, I get to do the fun parts of my old job without the bad or boring parts. The main thing I miss? Office building cafeteria food, oddly enough. I don't even know if that's still a thing post-pandemic.
As for mega corps, I've worked in a couple, and although I've never served I compare it to doing the work and making the sacrifices for your platoon, not the whole army. You get to know your immediate team and are in the trenches with them.
kj4211cash
Loved this comment. I'm 46 and dislike my job at a mega corp, especially as compared to my previous startup job. There are way too many cooks in the kitchen on every halfway interesting project. But the mega corp job pays too much to leave. Do this for a few more years and I'll reach financial independence. Then I can go back to a startup or ... something else. Part of me wishes for the layoff and severance that more and more of my colleagues are getting. Sorry to be such a downer. Most days are enjoyable and I can tune out the mega corp nonsense.
tailspin2019
If you’re only a couple years off financial independence I’d consider quitting that job now and doing something that will make you happy!
You’ll reach your goal either way, but you probably won’t regret it even if it takes a year or two longer - if you’re working on something more fulfilling during that time!
At least reconsider what options you have right now. You probably have more than you realise.
jmathai
There’s truth to this comment.
I was 4 years away from the financial number I had in mind while working for a big company. 2023 was a pretty miserable year and I got laid off in 2024.
The severance was nice (4 months of pay) but if you’re a few years from financial independence then that shouldn’t be what’s stopping you.
I wouldn’t have left on my own. And it wasn’t more tolerable I would have preferred to stay for 4 more years. But given what I had control over - it didn’t turn out too bad and I am not looking to return to a big company for the next few years - I’d rather semi-retire for 8.
grandempire
> Do this for a few more years and I'll reach financial independence
This is always the plan. Then a few years go by, life happens and you say eh, a few more years of saving would really help me feel secure.
On bogleheads I’ve seen 65 year olds with 15 mil saying they aren’t sure they can retire yet.
jebarker
The most important part of FIRE is avoiding lifestyle inflation, otherwise you're just treading water.
On the other hand I've also seen folks retire early and then return to big tech because they didn't have anything to retire to, i.e. you need to make sure you also have a life.
julianeon
I've always thought this was an extreme response to managing the fear of death. By postponing retirement with that much in the bank you're saying: who knows, I could live so long I could run out of money - a flattering thought.
If I could talk to those people I would say: like it or not, you're going to die, sooner rather than later. If you're 65 you'll probably die within 30 years: use that as your reference point. It's death that makes your savings excessive, since you'll die before you can use it. You'd be better off accepting this truth and spending some of it now.
YZF
I'm the same age and I'm an engineering manager. I never thought I'd be working for a big company and most of my career I hadn't but now I am. At least where I am I think the engineers have more or less equal contribution to killing creativity and sucking life out of your soul. There's a symbiosis there. I have to deal with engineers that over-complicate everything, make things drag forever, apply philosophies they don't really understand, argue about the dumbest things in code reviews etc. As was mentioned in one of the other comments, many people that are in software development today aren't there's because they like it or have aptitude (those things often go together), they're there because it seemed like a good career. There are still some great people though.
At the end of the day culture is created by the people. Big companies are the way they are because of a combination of people and the business. Management maybe has a somewhat bigger influence but it's really not fair to put the blame squarely on management. I've also seen big companies that were much better (mostly where I am now) and much worse. I've also experienced a pretty bad startup. A middle manager can have it worse because [they are] stuck in between- I often take care of a lot of crap for my team.
For my part as a manager I try to make things better where I can. I never stopped doing technical work. I have deep technical roots and a lot of startup experiences to draw on.
I've always lived frugally and have done well financially. I'm still working for the challenges and the money and maybe it's just inertia ;)
wkat4242
Yeah I'm at a mega corp and I'm 50.. I have started really hating my job the last couple of years.
I wanted to earn more and moved into an architect role. This was fine for a while, I really enjoyed smoothing our internal IT experience for our users and bringing all my technical expertise to the table. But then we got an idiot director who wanted to separate architects from technical work.
But now I no longer spend my time with the nuts and bolts but I'm supposed to lay out the work for the operations team. While not having any access to anything. This is a major problem because I learn by doing and Microsoft's documentation is often an outright lie. So my knowledge is withering away, I'm not happy because I'm not doing anything technical and I spend half my day with pencil pushers talking about policies and governance which I don't give any f### about.
And our security team has gone full BOFH and making everything purposely difficult without considering the user experience. In fact sometimes I think they forcefully want to make sure things are difficult for everyone because people associate difficulty doing their work with security ("if it's so difficult to do my job it must be impossible for an attacker to get into it!"). But many of the measures they put in place make no sense. For example for some systems I have to authenticate to the same MFA method 3 times in a row.
And we're now forced to log our hours in Jira (our new director thinks that just logging hours in Jira somehow makes us 'agile'). So I'm being much more micro managed by people who don't have any clue what I do. And just bitching to me about time spent on tasks.
But I'm kinda stuck now :( I wish I could just leave but I need the money :'(
fifticon
I could have written this verbatim comment, but you saved me the effort. We have "2FA" which becomes 3+FA on the most random stuff at work. So whatever you have to do for the day will contain lots of sprinkled arbitrary 2FA games. Sometimes you can check a box "cache this for a while", other times it's grayed out. Meanwhile, the actual applications we keep running are full of unpatched security holes, for .. reasons. So it is all theater, but my boss and bosses' boss (6 layers last I counted) gets to claim in some review that we are "encryption at rest" etc., so "all is well". My development machine is unable to build executable files, because crowdstrike flags them as suddenly appeared malware. I have got a crowdstrike security exception for a single folder, where I can place my executables.. We have trouble interacting with web services, because the company web filter classifies web api URLs as "newly appeared/unknown website". Our stratosphere one-way-communication management layer are clueless about these issues, as someone have explained to them we "just need to do git push CI/CD to the cloud".. News flash, 80% of our software is NOT cloud or web based.. I "manage" some of these issues, by unplugging the ethernet cable and instead work off wireless HotSpot from my company-provided smartphone, but I am well aware that if the clueless management ever figures any of that out, it is no doubt firing offence :-/. But then again, a new job would be a breath of fresh air, I am unfortunately just paid too well for a cozy, if mindless, job.
grumpy_coder
This sounds far more real to me than the original post. All the technical issues in the world don't bother me unduly, it really is the managers who make you hate work.
Money wise these corps are a system of their own, they pay enough to make you not quit. The more they pay, generally the more they suck.
Just need to wait till my 401k doubles one more time, my kids finish college, and the house is paid off.... just 10 more years
erikerikson
You can change your need for large amounts of money. There are many efforts to keep you too overdrawn so you stay stuck in place. It turns out you need to use your freedoms to have their advantages. Consider what you truly want.
wkat4242
I'm not overdrawn. I don't have any loans. But I would like to buy a flat and those are really expensive. You also have to do a 30% down payment here. I'm saving money but against the rising prices it feels like I'll never get there.
scellus
I'm 57, a data scientist and just can't keep my hands off concrete problems, which means I need to write code as well. Although I enjoy good modeling most, right now AI makes even mundane parts of the work fun again.
kleiba
I'm not much younger than you and almost everything you've written about your life applies to me too. Except for this sentence:
> I don't even have to work if I don't want to anymore.
I'm in awe of IT professionals who have really made good money. I worked in academia for most of my life, and have always been of the opinion that we are paid really, really comfortably. But to able to pretty much retire in my mid-50s? That's science fiction.
lamename
Do you feel that your technical skills, people skills, or luck have helped you to avoid any ageist treatment you've encountered over the years? Especially in scenarios where "deciders" are younger than you.
karmakaze
After reading many of the other comments, I've come to realize there's a big difference between the trajectories of those who are doing this now at 50 vs those earlier in their career now contemplating it. The biggest difference I can see is that in my era, people went into programming because they loved it and wanted to know everything about it. Once there was high demand and great starting salaries compared to anything else, things changed and many get into it for the lifestyle without the innate interests.
> It's about the constant evolutionary changes that occur in the language definition, the compiler, the libraries, the application framework, and the underlying operating system, that all snowball together and keep you in maintenance mode instead of making real improvements.
This paints a very different picture of software than how I perceive it. Most backend work is basically making plumbing and applying domain logic from one consistent persisted (or in-memory) state to another. My understanding of operating systems, programming languages, and databases hasn't changed for the most part in decades, only additional details being filled-in as I encounter them. I learned far more early in my career doing embedded C programming as a co-op, then later C++ multi-threaded programming for OS/2 and Windows NT, and lastly using a number of SQL databases. Programming languages, frameworks, and APIs were the least of my concerns like using some other plumber's toolbox while fixing a leak.
dehrmann
I had a colleague who's in his early 30s talk about management and matter of factly told a story about his mentor saying "you don't still want to be programming when you're 40, do you?" That thought had never even crossed my mind.
neilv
> But large scale, high stress coding? I may have to admit that's a young man's game.
If you're not up to it, or it's something you don't want to do, or you're just going through a low period, then that's OK, speak for yourself.
But this piece is being read by a lot of still-in-school and barely-out-of-school aspiring founders. And you're feeding ageism, to their detriment, and to the detriment of everywhere they'll work.
It's not unusual for teenagers with no real world experience to think they have all the answers, that their parents and adults aren't as smart or capable as them, etc. Fortunately, they grow out of it...
Unless a startup incubator, that historically favors impressionable young boys, hands them a bunch of money, and tells them they are the best people to do a startup. And when said impressionable young boys are exposed to ever so slightly outside that messaging bubble, they see articles like this.
And so the illegal, yet nigh-institutionalized, ageism persists.
Sometimes, when I see one of these articles, I think at least it's a blessing that we're not seeing more self-appointed representatives of other groups who are discriminated against in employment, volunteering themselves, to go out of their way, to feed that, and screw over everyone else.
prhn
I've really changed my perspective on this type of thing as I approach 50.
Great art is always made under great constraints. Software is no different.
It's always the weaker engineers that are constantly complaining about the things listed in this article. Complaining about all the "stupid code" and "stupid decisions" that were made before they arrived.
There is no realistic scenario where you can spend infinite time developing the perfect solution. And I say infinite because there is no amount of time that will allow you to achieve perfection. Perfection does not exist.
It's true in art, and it's true in engineering.
anonzzzies
But like in art and so also in programming you can definitely strive for perfection.
There are plenty of writers, some famous, most not, who keep rewriting and rewriting because it's not perfect and still get annoyed because it's not good enough when published. Software generally is a job to make money : who give a crap if it's perfect; not your boss or your company clients. But personally, is another thing. I definitely have software that is perfect in my eyes. I don't care if others don't think so but I worked decades on it and using and updating it makes me happier than other things. I am well over 50 and I do not see this change for me.
There are well known examples too in software, for instance Jonathan Blow, who estimates stuff and then overshoots by a long shot because he does not like the result enough and Arthur Whitney who keeps rewriting his 'perfect' (in his eyes) software (k) to just a little perfect-er.
MrMcCall
> writers, some famous, most not, who keep rewriting
My favorite, William Gibson, is like that.
I was 50 when I first realized that I am an artist, too. Shame it took me so long to figure that out.
'The Art of Software Design and Implementation' ~ that's my niche.
zahlman
When I think of "great art under great constraints", I think of the demo scene, not dealing with the legacy cruft in someone else's million-line codebase.
afpx
I'm curious what your career trajectory was like. I'm surprised that your experiences are so different than mine (see my comment below). In the early years, we had tons of time to just play around (e.g. Paul Graham wrote Hackers and Painters in 2004).
pipes
My theory is agile turned software writing into a production line, well it attempted too. Hard to fit experimentation into the everything must be a ticket process/mentality and endless ceremony meetings. Also I think the quality of developers decreased, not sure if agile caused this or it's some sort of work around for it.
zahlman
I always understood that Agile was supposed to reduce the bureaucracy, not increase it. It seems to have been embraced, extended and extinguished by the sort of people who were pushing Waterfall in the previous era.
>Also I think the quality of developers decreased, not sure if agile caused this or it's some sort of work around for it.
I think it's mostly a function of developer quantity and the pervasive "anyone can do this" attitude. (My assessment: most people probably could, but fundamentally aren't comfortable using their brains the right way.)
Atreiden
Quality has definitely decreased, and I think it's the natural consequences of specialization. Most modern devs I've worked with (even/especially those from big tech companies >1B val) know their on particular niche well, but flounder when faced with a different kind of problem. They have a hammer, so everything is a nail. The power of modern infrastructure and orchestration systems has eliminated their need to understand the full stack in order to "deliver value".
From my POV, hacker culture is going away. Because it does not Scale in the way capitalists want it to scale. And the same capitalists are foaming at the mouth at the notion that they might be able to replace expensive engineers and developers with AI.
Our niche has been captured by global stakes, and those stakeholders are all too happy to believe that they can scale innovation without all of the previous "cultural baggage" that, IMO, is the only reason we have the systems that we have today.
Or maybe I'm just getting old too. Hard to say.
goodpoint
It's not just your theory. agile/scrum was designed to take the artisanal aspect out.
imjonse
There is a large variety between perfect code and code people usually complain about. Not only weak engineers complain about crappy code and stupid decisions.
pydry
As I got more senior it wasnt the crappiness of the code that frustrated me as much as it was the intransigence people that created the circumstances that made it happen.
Im totally happy with crappy codebases I can fix, I just get fed up coz because management wants 34 new features delivered by next tuesday or a junior with an attitude doesnt want to pair or be trained to TDD.
closewith
Sounds like you might be the intransigent one, refusing to accept the nature of the job.
spacecadet
As an Artist and an Engineer, too many engineers are perfectionist in a reality where it doesn't exist. To the people here who quote artists and works of art as if they are "perfect"... you. were. not. there. It's only perfect to you in your perfection biased brain. Art is very much imperfect. Concessions were made, pieces restarted, plans changed. Creation is messy and painful. Art or Engineering.
MrMcCall
OTOH, I'd say that software perfection doesn't exists because of all the slackers who accept their crap as "good enough", leading to enshittification.
On the most important level, software is either pefect or it fails.
ETA: I mean for functionality in the above. That's why I don't like web design: too many style choices. It's also why I stick to the commandline nowadays.
spacecadet
Enshitification is the result of businesses choosing profits over ethics, not the result of software engineering being inherently messy.
wslh
> Great art is always made under great constraints. Software is no different.
I don't agree that great art (or software) is always made under great constraints. If you have an intrinsic drive, having enough time can yield a compound return. For example, in research, the "publish or perish" mentality often forces people to focus on shorter-term problems rather than pursuing more ambitious, long-term breakthroughs.
hnthrow90348765
>Great art is always made under great constraints.
It's sad, the Mona Lisa never quite reached its peak because da Vinci didn't have a Jira board and a scrum master /s
Some of these constraints are not truly necessary and often stifling and once you've done work without them, you can't go back. Usually that's when you're older.
blindriver
I’m in my 50s. I still code and I still love it. I got hired into a FAANG in my 50s and I’m still better than most of my team. I told the recruiter I didn’t want to interview or work as a staff level I wanted to be an IC at the senior level despite my 30+ years of experience and I’m happy.
This past weekend I’ve been coding a couple of side projects that has been using OpenAI to classify a bunch of things and I’m still having a ton of fun.
FrustratedMonky
"I got hired into a FAANG in my 50s"
That is unique isn't it? I'm kind of curious.
I'm programmer in 50's and want to switch industries to try something different. Any advice on the journey.
blindriver
I wouldn’t say it’s unique but usually people my age get hired at higher levels but I purposefully didn’t want that.
I studied my ass off, I did I think 400 LC questions and did many other interviews before this interview so I was at the top of my game. Systems design comes naturally to me, but also required practice. I arranged things so that I had all my interviews over the course of about 6-8 weeks and ordered them so that the companies I was least interested were at the beginning and the ones I cared about most were at the end. I also explicitly told them that I wanted to be interviewed at senior software engineer level, not staff or higher based on my years of experience.
This worked in 2021-2022 but I don't think it works these days because this is probably the second worst job market I've seen since the dotcom bust.
yodsanklai
My story is almost the same as yours. Contacted out of the blue by a couple of FAANG (maybe after referrals from acquaintances, but not even sure), despite having little experience (started my career in academia). Took me a couple of attempts over the span of a few years.
Interestingly, first attempt at one of them, they said I was ok for IC4, but wouldn't hire me at that level with my seniority. I'm also glad I eventually started at senior level rather than staff (and I'm happy to stay at that level too).
null
ArlenBales
I imagine they had some very good referrals, probably a friend in the company.
yodsanklai
It should be pretty easy to get a referral. Most people should be able to find someone who would refer them (acquaintance, friend of friend). I already referred alumni from my school just because they reached out to me on linkedin. It's just a form to fill... After that, you never know what the recruiters will do with that. Sometimes, the person you recommended gets contacted soon after. Other times it seems recruiters skip promising candidates.
blindriver
No referrals, I got contacted through LinkedIn and truth be told I had interviewed there a couple of other times in the years previous and was rejected.
closewith
It it was unique, it would result in heavy enforcement actions for age discrimination in the civilised world.
yodsanklai
I'd be curious to know the age distributions among SWEs at FAANG, but from what I see in my company, it seems to be centered around 30. My guess is that are very few people older than 50.
So maybe the world isn't as civilized as you'd hope too :) I'm curious about the legal implications too.
fjfaase
I have asked this question myself when I was younger, but I never had the ambition for some leadership role or to do something else than software engineering. Now at age 63, I am still a software engineer. Last year, I have started a new job as an embedded software engineer at a small company, and I am very much enjoying it, learning new things about electronics, clock domains, and how peripherals work (like I2C peripheral of the ESP32-S3). I am drawing flow-charts for the first time in my career and developing unit tests to make sure the software works as desired. I am learning many new things and I am enjoying it. I am still working on becoming a better software engineer.
afpx
It's interesting that this article was written in 2012. I can totally relate.
Back in 1991 when I started my computer science degree, I just wanted to create new things - I liked to reverse engineer, take things apart, hack code and build stuff that never existed before. My friends were going into chemical engineering because the average salary was like $45k / year whereas programming was something like $38k / year. They thought I was short-sighted because I didn't go for the money. But, it didn't daunt me that I got paid less. I thought it was awesome that someone would even pay me to do the type of work I was doing. I earned $33k in my first year. In contrast, I had a friend who managed a Barnes and Noble and was making 45k, but I didn't care.
The early years were pretty awesome. In the 90s it was exhilarating to be working with your brainy hacker friends late into the evening. No chaos or rush - we'd release every 3 months on a regular schedule. We had tons of slack time to just play around. After work, we'd go out and have beers and talk philosophy and art and culture (It was during this era that Paul Graham wrote Hackers & Painters). But, then the salaries started going up, and up, and up. I knew the field wasn't sustainable when my salary greatly exceed my chemical engineer friends. It was sometime in the mid 00s that I realized I needed to make an exit plan. While my collegues were out there buying giant houses and fancy cars, I doubled down on the minimalist lifestyle and dumped everything into investments.
By 2010 I was making 30% more than my boss, and I could see the discontent. I was making more than some of the executives. The expectations became super high, and I could see the end was nigh. The field became flooded with people who didn't care about anything but the money. It diluted the creativity and energy. The status-seekers viewed programmers as blue collar, and they weren't going to let blue collar guys make more than them without some punishment. The consultants made fortunes teaching the 'boss class' how to turn programming into a factory. Programmers weren't allowed to create anymore - we would get a 'Program Manager' who would give us a 'backlog'. It was super demotivating and not fun anymore.
azinman2
> The field became flooded with people who didn't care about anything but the money.
This is what ruined SF. All the people who made fun of me growing up for being into computers were all of the sudden working at Twitter as a product manager. They don’t give a shit about the craft, potential, OG hacker culture that’s an offshoot of counter culture movement, the history… it’s just let’s monetize the iPhone since everyone has one and I can understand that.
afpx
I felt things got to peak silliness when a friend of mine (who had gone on to make a fortune) bought his first $20,000 watch. I mean watches are cool. I'm not a watch hater. But, this was a guy who had never cared about luxury things for all the years I worked with him.
I used to get a little jealous of my friends who went to the bay, got connected, and made it big. But, nowadays I feel very, very fortunate to be able to spend the rest of my life being a dilettante - painting, reading, writing, cooking; learning about quantum mechanics, math, cosmology; and watching as Kurzweil's predictions come true. It's bittersweet, but what an amazing experience and time to have lived.
When I was kinda depressed a few years ago after I stopped working, someone recommended that I get into 'Web 3.0'. My brother called me yesterday to tell me "it's amazing, man - they figured out how to update websites in realtime because they use blockchain." I'm not joking. lol. The search space has been exhausted.
morning-coffee
Man, you nailed it. I finished EE degree in 1992 and was having so much fun by 1994 writing C for a small software company. That led to a job with a FANNG (actually a MAMAA) where I've been ever since. I'm still lucky to be writing the kind of code I like writing, but the process is way more frustrating than ever due to what you've described. There are way too many people involved now who picked the field because it was high-paying, not because they were inspired by the Apollo program, or tinkered on a TRS-80 when they were 12 and were hooked.
I'm also lucky I went full time remote in 2014, and had managers who supported me taking a part-time side gig as a paid-on-call firefighter/EMT for my local small community. This has transitioned into a great opportunity to "retire" from software and still have something very fulfilling to direct my energy towards. It's just that I'm not ready to ditch the code-writing habit.
ergonaught
If anything I think I like programming more in my mid 50s than in my teens/twenties/etc.
It’s my desire to be exploited by uncaring corporate greed that has starkly diminished over the years.
Maybe that’s what the author meant about “large scale, high stress”.
JohnDeHope
I'm 50. Yes. "It's about trying to come up with a working solution in a problem domain that you don't fully understand and don't have time to understand." This has been my trick for staying engaged and excited about my work. Do try to understand the problem domain. It makes a world of difference in what you code, how you're perceived, the kinds of roles you can be promoted in to, etc.
sumanthvepa
I'm 52. I absolutely love building software find customers for it and building businesses on serving them. It's the most intellectually challenging and financially rewarding thing I can think of for myself. And programming is one of the joys of the job.
The reason I find it more enjoyable than others might, is because I have considerable autonomy on how I will build my software, on what timelines, and who I'll sell it to.
The real problem with software development is not the complexity of our tech stack. It's the lack of agency that most programmers are forced to live with.
2pie
I fully agree with you. After a few happy experiences in development, I started to work as a developer for an ERP service company. I was served functional spec that I had to implement. I only had to look at the technical of things, and I quickly became bored.
So I transitioned to a client-facing role which was more interesting in a way, but with too much stress and too much management to do.
Now I try to find my niche in between, staying client facing but still handling the technical tasks. I find it's a really interesting position, it's very efficient since it reduce the amount of necessary communication, and it's very satisfying.
It does not work for big projects though.
randcraw
I've been a programming pro for 40 years, enjoying it for the first 35. But after covid the bloom has faded. My home for the past 20 years has recently become a production shop in which jira, github, confluence, process workflow, and now copilot-driven templatization have taken over, replacing our old mission to invent whatever it took to rock the world of the customer.
I suppose I should have expected this in a fortune 100 IT shop. For 15 of my 20 years in R&D, our mission was to deliver the goods and let the laughably misdirected IT fashion of the day be damned. But since covid, IT's love for processes surrounding the delivery of software products has trumped all else. How insanely BORING. And I work in AI. These should be the BEST of times.
I prepared for this day for decades, by taking a bunch of AI and computer vision classes part-time and adopting a variety of AI tools and libs. But until covid, we only danced along the fringes of building smart software without quite immersing in it. Then with AI's maturation during covid (and esp since), after 60 years of gestation, AI's day to bear fruit is nigh. But rather than embrace the dizzying possibilities of how AI could reinvent R&D from first principles, I find we're supposed to be happy just turning the crank -- adopting someone else's turnkey AI system to perform the same old task and with the same old objectives, hoping only to be a bit 'better'. Blah.
It's time to shed this old skin and let myself evolve. Adieu corporate America.
linotype
Sitting in an air conditioned room mentoring engineers and writing code? I mean, it beats what most people did for the vast majority of human existence to survive.
ramblerman
> Every age, every culture, every ethos and tradition has its own style, its own varieties of gentleness and harshness, of beauty and cruelty. Each age takes certain kinds of suffering for granted, patiently accepts certain evils. Human life becomes a true hell only when two ages, two cultures, and religions overlap. Someone from the Graeco-Roman world, forced to live in the Middle Ages, would have died a miserable death, just as a savage would in our civilized world. There are times when an entire generation is caught between two eras, two styles of life, so that it loses all sense of morality, security, and innocence. A man like Nietzsche had to endure our present misery more than a generation ahead of his time. Today, thousands endure what he suffered alone and without understanding.” — steppenwolf
morning-coffee
As a bit of a stoic myself, I appreciate the appeal to the "some people have real problems" argument.
I think a big part of the frustration or unhappiness of some subset of this generation of software engineer who cut their teeth in "The Golden Age" is lamenting or longing for "what could have been...". Maybe it's our slow realization of Sturgeon's Law and wish that we would have discovered this seemingly universal truth ages ago. Software, being mainly a construction of the mind, has the potential to be truly great (and some is), yet the state is basically "All Software is Shit". Squaring the expectations of my junior self with the realities of my senior self is... disappointing.
askonomm
I'm sitting at my home office, able to play with my dog during breaks, while simultaneously having a lot of autonomy at my job. I love it, and would not trade it for anything. People seem to really get used to their way of living and lose perspective, then becoming unhappy. We've got it really really good.
closewith
It's more comfortable, for sure. But comfort is not the only aspect to life.
It might even be a negative given how miserable software developers tend to be compared to those with much less comfortable jobs.
megadopechos
Yeah, I'll take it all day long. I'm not even done with my first year of my first software engineering job so perhaps I'm full of optimism and hope. But in a previous life I was cooking on a line and moving tons of gravel with a wheelbarrow with my brother. I much prefer my situation now.
goodpoint
Absolutely not. Human happiness is a tad more than having air conditioning.
gorfian_robot
spoken like someone who has always had AC
riehwvfbk
... and it sucks that this is the most excitement you (or I) can muster. This means that our sense of agency is dead, along with the ability to innovate.
linotype
What should I be doing instead? The company I work for is paying me to learn and work on machine learning while mentoring software engineers. They’re also paying machine learning engineers and data scientists I can learn from. It’s hard for me to understand what better a situation I could have.
selimthegrim
I wonder if they’re hiring…
madeofpalk
That's a very uncharitable reading.
I took it to mean that's the floor. That's a pretty good floor - it's up to you to do the rest.
louthy
The comments in the article are all ‘glass half empty’ comments. Many of the issues listed are opportunities to innovate. Use them!
I’m 49 and just sold the first company I founded. I’m already building my next idea (although this time without financial constraint) and continue to work on my open-source projects.
I started coding as a hobby when I was 10 years old. I still love being a maker and the process of making. Now that I’m financially free and working on my own ideas, for my own reasons, it feels just like it did when I was 10 years old.
I’ll stop when I’m dead.
I'm 56. By far the oldest person on my team and older than most of the managers and executives. I've done it all since starting with computers when I was probably 12. I work for small companies where they let me work largely by myself on large problems. I love the challenge of learning new things and am all over AI tools to automate out the redundant boring parts of the being a programmer.
I have been fortunate and successful and managed my finances. I don't even have to work if I don't want to anymore. I do it to keep my brain challenged.
But if I was stuck in a boring mundane programming job for a mega corp then I would retire in a second. I've never stayed at a company once it's grown too big. Middle management kills creativity and sucks the life out of your soul.