For developers who are ~35 and up, almost 100% true, once you get younger than that you’ll find that there are a large and growing minority of people who are very much in it for the money alone without any particular interest or affinity for computing. Their parents, advisors, etc saw how much money was being made and pushed them towards computing as something more like a high ROI trade.
You see the same done for specialized welding for smart, but not academically smart, kids. It’s hard work to get into, but if you get there it can pay very well, regardless of if you care much about the underlying metallurgic properties that you’re dealing with or not.
This is completely fine either way, but it’s important to realize that we’re not really the professional of child prodigies that it once was.
I'm 33 and I started programming in the 90s (I was raised by two geek parents a la Larry Page who were supportive), so I'm sort of in-between the two 'generations'. At age 37 and above, pretty much everybody is either a career switcher (in which case they've considered things that aren't money) or started before developing got big. I say 37 because that was old enough to already be coding and brought INTO the money with job offers in the dot com era. (I had a couple of offers from people who didn't believe I was 11/12, and I knew some people who were 16-19 who were leaving school to take REALLY well paying jobs none of us ever expected.)
After that, it was well known that coding could lead to a lot of money, and as the sector continues to grow and other opportunities to escape poverty shrink, it's pretty inevitable that people end up in coding for the money. Especially since that's how we teach them: All the tech courses are about employment, not playing. Kids don't learn tech as a joy or a tool to make their lives better, it's just another corporate hoop.
And then, rinse-and-repeat, we'll probably see the same cycle again in the 2020s thru the 2030s.
FAANG and dev positions in general, though, I think people are treating like they used to treat being a doctor/lawyer/accountant: It's a good, steady living and it will always be around. That's very different from the dot-com boom, which was way more a gold rush, even at the entry level. ("They're willing to pay HOW MUCH for the stuff I was playing around with?") Somebody who started at Google in 1999 (or Amazon, or even FB in 2006) is very different than most people entering those companies now. The dotcom was high risk high reward like modern web3/crypto, whereas modern swe positions are low risk medium high reward, which makes them great for people who are more risk averse for whatever reason.
I’d believe it’s true now (I don’t really know), but it’s likely more recent than the OP thinks.
Most of the people I know with the worst financial outcomes overpaid to study stuff they didn’t care much about (and isn’t marketable or often even valuable) because they thought it was what they were supposed to do.
1.) I was into computers and programming in the 90s but I was too young for the dot-com boom, so by the time I could work we were in the bust. So computers weren't a 'safe' ROI.
2.) So I went into languages and wanted to be a diplomat: I studied rare languages to be more valuable (Arabic and Chinese), went to the Middle East, and planned. Except that it turns out that basically required either law school or a bunch of unpaid internships I couldn't take since this was post 2008 and everything was hell/the competition was insane, so I dropped that plan and continued library work.
3.) I recovered from losing that dream and went to grad school for Library and Information Sciences. I did a focus on assessment/metrics/KPIs + tech (so databases, HCI, and UX research) with an intent on pursing an academic librarian career and building academic tech tools on the side. My first job out of grad school was at an Ivy. I got what ended up being MS my last semester of grad school and had to quit to see to my health.
4.) I finally managed to find decent employment and get health care (MS drugs cost 300k/yr)... in 2019. Then COVID. Luckily I'm still employed, but it did throw out ALL of my career planning post MS-diagnosis.
At this point, I've just given up on planning. It's worthless. The minute you or someone you love gets sick, or you get a divorce, or a disaster hits your house (which you won't get help for), you're going to lose it all anyway. I'm just picking up as many skills as possible and hoping one basket doesn't break.
I can't find any agreement on who first said that, but it appears that several great generals have said something like that.
> Same thing might have happened to me had I been there at the time, it's hard to make the right choice in that kind of environment.
I'd say for most people (but not most people at HN because the tech community is pretty unique in terms of labor relations), occupational planning is more akin the tech career planning in 99 where there are numerous big unknowns hitting people constantly (COVID, 08, etc.). Our informational environment is TERRIBLE to build a decent ROI model. Doing so would take the average person so much time to research and build that I think right now it's better to spend the time either:
a.) Planning outside of the current systems and their incentives. For example, I'm supplementing my conventional retirement savings by handing out a LOT of free money locally. Even if the stock market crashes in my 60s and I lose everything (which, based on my lifetime, will probably happen bc it always does...), hopefully there will be at least a few people/families/organizations around that view me kindly and will help (if 2000 people give me a dollar a month, I can make rent). This is also likely to be true even if society completely collapses, provided I'm alive.
b.) Focus on building better heuristics for reacting to sudden change and pivoting. Our culture and society doesn't care about being stable and will always change to chase the latest profit/dopamine hit, so instead of making plans that require and assume stability is possible and that the past is predictive, it's better to accept the future is NOT predictable and spend one's energy on building a great skill set to be flexible. Bending instead of breaking.
That CIA signing bonus was REALLY tempting, though, I'm not going to lie.
The crash my junior year and the resulting divorce of two of my parents means over half my undergrad debt was from my senior year. I had to choose between doubling my debt and dropping out with a year left.
And I also effed myself by working my way through school to try to keep costs down/take out less debt. It meant I had no money when I graduated so I couldn't even afford things like interview clothes for basic office jobs and I had to take the first thing I could get. In retrospect, working on tech projects in my spare time would have been a better FINANCIAL option than working a job for 7.25/hr, especially since this was '06-'10 and I was interested in things like NLP.
I just don't care anymore. I tried to be responsible, it didn't work, and now I just don't care.
One time I stopped at kinkos to print out some portfolio designs for an interview, and the cost was 6 dollars. I had to leave because I only had 3 dollars.
Things are much, much better now that I transitioned into tech. I kinda did it for money but I'm lucky because I do genuinely love it - I wish I had started it sooner in life.
I'm curious - where did you end up? If you're on here, I assume you're in a STEM field of some sort?
I just missed talking about tech and was sick of getting blank looks when I rambled about how Page Rank is a mistake.
Oh, and regarding HN, I've been here on and off lurking since it was founded in 2005, I just thought I was too stupid to contribute. Now I'm old, jaded, and realize we're all stupid.
It definitely left me, and likely most other people, wondering why on earth we shot ourselves in the foot with the monetary equivalent of a mortgage at the dawn of our professional lives.
I've taught three[0] people a little younger than me software that all wanted to do it for the freedom and financial security and two of the three transferred out of software to something else in tech like product management. It really bummed me out too, because it was the two women out of the three. Their lives are still markedly better than before, but I want more women in actual software.
[0] Well, more than that, but the others gave up on the first week or two.
Personally I think that's a flawed assumption. While there are certainly cultural biases at play still, there are also aggregate differences between the genders that most likely means the "natural" gender ratio will still be skewed towards men.
This is unfortunately a taboo topic to make note of, and is absolutely not up for discussion in most workplaces (see the Damore scandal), and so the fetishism you note persists.
Part of the reason that I don’t think your paragraph 1 assumption is flawed is that there is evidence that men and women were equally interested in programming before the 80’s, but that a combination of cultural and societal factors came into play in that decade that branded computers as a “boy thing” and resulted in women being pressured out of the pipeline from a young age.
But even if you can find some sort of counterargument for that, my overriding reason why I stick with this assumption is as follows: decade after decade, people insisted that women weren’t into $career. And one by one, women have found their way into those careers (factory work in WWII, the executive suite more recently, plenty of other examples in between). In each case, the people saying women weren’t into $career had an argument that seemed to make sense, often relying on some combination of status quo statistics and hand-wavy conclusions drawn from psychology. And they were wrong. So when I see those same arguments brought out again for this career (often with some exhortation that “this time is different”) I generally dismiss them, as the epistemology they’re based on has a bad track record.
With all that being said, when it comes to actions, I’ll be more likely to encourage women to get into programming if I get a sense they might be interested in it. However, when it comes to interviewing candidates, I will not grade people on a curve based on their identity, as it is my belief that men and women can in fact be equally good at programming and should be held to the same standard.
You're right in that it's important not to automatically ascribe any demographic disparity to fundamental differences between the genders, but it's equally important to not automatically ascribe that difference to discrimination without considering those fundamental differences.
Given how slanted these stakes are and how many times society as a whole has underestimated women as a whole, I think the right answer here is to err on the side of trying to get women and other underrepresented minorities interested into tech.
[0] bear in mind what I said about the particular way I’m putting my belief into practice and that I do not believe in “reverse discrimination” to even the scales.
Anything more and it becomes the individual(s) behind the movement projecting their desires onto others and is no different that the societal molding that's taken place for the past several decades.
I'm glad you don't discriminate (nothing "reverse" about it) against men, but many do, and since [your views are wrong](https://www.amazon.com/Essential-Difference-Female-Brains-Au...) it's tantamount to sex-based theft and redistribution.
I don't think your premise is wrong, but I think it does explain why computer science is particularly focused on broadening participation, compared to other disciplines like nursing, teaching, etc. Computer science is current (for better or ill) a golden ticket to economic mobility.
The nature of "programming" as an activity also changed quite a bit.
Implicit and explicit biases exist everywhere. My wife is in teaching, and would love to move into administration some day. The problem with that? Despite women being the dominant sex in the actual teaching position, men continue to fill administrative (i.e. principals, deans, etc.) roles at far higher rates than women. Why are men filling leadership positions more than women, when they have less experience and participation in the field overall?
I guess my rant/point is, each field will have their own unique battles with inequality and/or lack of participation from various demographics. We can't compare apples to oranges.
Some of these disparities can be traced back to social conditioning and discrimination, but its also in large part just due to inherit differences in the interest and abilities between genders. It's been proven time and time again that the genders are often fundamentally different in terms of abilities and innate interest. Neither gender is better than the other, but we are different and denying that does more harm than good.
I'm in tech, I work on fixing tech.
> the intentional push for more of any specific demographic seems strange to me I believe the skewed demographics is a reflection of actions and pressures I don't agree with. I think there is pretty-open discrimination and steering of qualified candidates away from the field. (Read the news, sadly.) I'm morally against that. The demographics are an imperfect measure of our progress, but in my opinion it's a useful indicator.
> Shitty people are going to exist everywhere regardless Yeah, and in my workplace I'm against shitty behavior.
Without speaking to whether this is true or not, the parent's argument seems to me to be a kind of "whataboutism".
I don't choose to spend my time working to improve the work environment in other fields, not because I don't care but because I can't do everything.
Is this "pretty open discrimination"? It certainly doesn't make the cut for news. But yes it's very uncomfortable to be the only woman in that situation, people wok look at you for approval for their comments.
People being regular-shitty, combined with context, like making comments about the appearance and intelligence of the only other woman in the office, can create an inhospitable environment that forces women out. Companies that wish to hire and retain women should proactively create a hospitable environment or situations like above will occur.
The bigger thing is that it seems like you don't see return on investment into creating these better environments. Do you feel that diversity initiatives are wholly unnecessary or just poorly designed/targeted?
Regardless, my original stance was more aimed at the societal push of "get x demographic into tech". I'm not going to retype my thoughts on that - go read the other comments of mine in this comments section to get a clearer picture.
Edit: grammar
The gender ratio isn't changing though. If anything it is becoming worse, it was decades ago that less women went into software engineering today.
The only thin that changed is that now every company tries to put their women software engineers front and center, in their marketing material, to go speak at conferences etc. So it looks like there are more women, but there aren't. Tech companies also tries to improve these statistics by bundling non programmers into this category, like product and project managers.
> 2008 Male: 72.33% Female: 27.67%
> 2013 Male: 73.44% Female: 26.56%
> 2018 Male: 73.82%. Female: 26.18%
The year by year numbers are too noisy to really mean much. 2018 being 0.3% percentage points higher than 2016 doesn't say much.
Anyway, the main point is that the gender ratio isn't really improving. At best you can say that it has stagnated, rather than getting worse as it did a decade ago.
Reference: https://jaxenter.com/wp-content/uploads/2017/04/women-in-com...
This was why I didn't get into STEM initially. It's not that I thought that engineering culture was toxic per se, but rather because the women I knew growing up didn't have careers, much less careers in technology.
Hate to say it, but 0 female engineers _is_ evidence...
The assumption going in changes from "this is going to be ok" to "what is wrong with this workplace?"
(Of course this depends on team size, etc., but this is my own personal read going in.)
How many of us started tinkering with programming at a young age out of pure curiosity or interest in how cool it is, without any regards for how viable of a career path it is later in life? It seems most of us who did just that were boys. At some point you have to consider that there's perhaps an innate aggregate imbalance in how interested each gender is in programming, or in how much each gender responds to financial incentives -- which would explaian both why countries that are more gender equal and more prosperous tend to have a greater degree of gender imbalance in STEM.
Perspective is valuable, and like it or not various demographics have inherently different perspectives due to a variety of factors. We need conscious effort to include more demographics because our industry is dominated by a very small number of them and therefore its culture is heavily biased towards them.
I disagree. I coded for fun once, as a kid, and have never felt the need to do it again. If I never coded again, I wouldn't even notice because I my passions lie elsewhere. But working as a software developer is still tolerable because I'm just sitting at a desk, typing on a computer. As long as I don't have meetings...
Sigh... if only there were a way I could get paid for actually doing math homework every day...
I don’t think this is particularly unusual either. Lots of people don’t code outside their day job, even the really good ones, IME. And look at other jobs - I doubt most plumbers, linemen, bricklayers, etc really find their job enjoyable. But they might still be happy with their career because they don’t hate it, they’re good at it, and it pays the bills.
If it turns out that hiring older developers gets you a much higher likelihood of getting someone who cares, this might change matters significantly (assuming of course that there actually is a problem in the first place).
I didn’t exactly have a broad view at the time, but it seemed like top ~20 Comp Sci programs were largely unaffected and kept growing the whole time.
Very few people truly have a passion for their work and for most , it's just a means to an end. This has been true for all other "high paying" professions such as law and medicine. One of my best friends is a lawyer and he happened to mention that no one really gets into law because to fulfill some higher purpose..
Further, I don't think it really has an impact on the quality of the work they produce, you don't need a spiritual awakening to build good systems. You just need to be vigilant and gain experience.
As an older engineer (is mid thirties old?..) I've grown out of this and now look elsewhere to nourish my need for numinous in things like philosophy, art, music, relationships, etc. When I was younger, I used to naively think my identity was a "Software Engineer"; now looking back I chuckle at that outlook on life.
On a final note, I would argue that more people joining our profession is a _good_ thing. It will create more jobs, increase demand and we end up with a stronger workforce.
I don't think gatekeeping a field yields to a healthy outcome.
I'll come up with one of the few exceptions to the rule, i.e. me. I'm in my very early 40s and I went in it for the money 20+ years ago, I hadn't even played with a computer as a kid or as a teenager for the simple reason that my parents couldn't afford to purchase me one (and I wasn't really thinking of becoming a computer programmer back as a teenager, I found the work boring).
Pretty soon though I discovered that I liked this, I even, in a way, avoided a career path that would have brought me into larger companies so into management (I think it's harder to remain a computer programmer in a larger company once you pass a certain age, I can't explain the reason for why that happens).
Either way, I'm almost 100% sure that no-one can spend 15-20-30 years in this job if they don't like it, i.e. only for the money alone, at times it can be really draining on one's mental condition.
That was true 35 years ago, and without the metric butt-ton of money being paid now (though programming has always paid well within my lifetime). I've worked with those folks. The reason you might not see it is because they either left the field they hated, or worse, they stuck around long enough to become managers of what they don't understand.
it’s important to realize that we’re not really the professional of child prodigies that it once was.
Mmm, I don't know that it ever "was". Ignore the Carmacks, Wozniaks, et. al., of the world and you'll find that most folks holding programming jobs had the standard four year degree (because you were unlikely to get hired in 1985 without one), working on internal LOB apps.
So what brought them to Silicon Valley? For a great many, love of the machine.
Just to add, during the dot.com boom there was a brief spike of people coming into software purely due to the hype of riches without much interest in software development. Thankfully the dot.com boom was relatively brief and it crashed hard, so from what I saw then most of those people got disenchanted right away (by the time they graduated the crash was happening) and changed careers.
This time the boom has been going on for basically a decade, so it is becoming more common and lasting.
I think this touches on an uncomfortable point that many people don’t acknowledge: our current system generally* pays people according to how much they contribute to the economy and not by how much they contribute to society.
The scalable nature of software means developers can disproportionately add value to the economy, even while sometimes simultaneously working on projects that could be arguably a net negative for society.
* yes, we can all point to people who get paid handsomely without adding anything substantive, but general rules are meant to be applied, well…generally
The U.S. often sends their best and brightest to tech, consulting, law, and medicine. Other societies send theirs to education. Both can occur under capitalism. I would argue it’s not “capitalism” but that the economy is most valued. Capitalism could just as well make social workers the highest paid individuals if there was a different value construct.
I think a balance probably exists, but we are badly missing the mark.
I think the problem is it becomes hard for some to take those jobs when they could instead work in, say, social media or finance for many multiples of the pay.
Right now the best devops people in New York City are making between $200 and $300 an hour. That's obviously good money, but in the 1990s I had older friends who were making $200 an hour as Oracle consultants. At the top, the nominal pay has remained the same, but adjusting for inflation, that is a 50% paycut.
Likewise, lower down, I know lots of mid-level devs who are happy to make $100 an hour right now, but I also had older friends who were slapping together classic VBA apps with VisualBasic, back around 1999, and they were also making $100 an hour, so, again, it's a 50% pay cut.
But it is absolutely true that pay has been surging since about 2014/2015, so I imagine the software developer pay is about to catch up to the highs of the 1990s.
It's also true that the picture only looks bad when compared to inflation. To your point, most other professions did even worse, so the benefits of being a computer programmer are more obvious if the comparison is to other professions.
All in all, after the peak in 2000, the USA economy had a difficult 15 years.
Only partially true:
1. High total compensation (not salaries) is limited to FAANG/Unicorn employees (awash with money)
2. That high compensation has been achieved by stock options multiplying in value, thanks to abnormal run of the stock market (thank you Federal Reserve), which is not going to continue with rising interest rates
3. Salary base seems to be stuck at $150K for mid-senior developers in bigger cities (except for NYC) for many years now
Very nearly every publicly-traded tech company, actually. The list of "tech" companies where mid-level engineers aren't breaking 200k TC is much shorter than the opposite.
> 2. That high compensation has been achieved by stock options multiplying in value, thanks to abnormal run of the stock market (thank you Federal Reserve), which is not going to continue with rising interest rates
Initial offers have been increasing; we aren't talking about golden handcuffs that employees have from stock growth. To give a very recent example: Amazon recently bumped up their pay-band for mid-level engineers and they seem to be hitting 350k/year (maybe more; have seen a couple reports of 400k). Their mid-level pay-band previously topped out at ~300k/year.
> 3. Salary base seems to be stuck at $150K for mid-senior developers in bigger cities (except for NYC) for many years now
...you mean "except the Bay Area", right? Though it's definitely not true either way; I live in a large city that isn't in the Bay, Seattle, or NYC, and 180k is a pretty common number for senior engineer base salaries, and I see 200k+ more and more frequently. (Not that I care too much about just base; given the choice why would I work for a company that only pays base salary, i.e. ~half of what other companies pay?)
Anyone can be a teacher. The certification requirements are low. The academic requirements aren't anything more than most kids are getting anyway (a degree in anything will qualify you in most US states). Most teachers need to work so their BATNA is "work someplace else doing the exact same thing for roughly the exact same amount of money." What's more (and I didn't really mention it above) is that you can't tie teaching directly to income. Not that you should be able to, but if you're a quant at an HFT shop you can probably draw a line with a pen from your code to tens of millions of dollars in profit that's there this year that wasn't there last year. Do that year over year and it's hard to argue against you getting paid $800k-1M/yr in cash and bonuses. Helping one of your students read a little better, or finally understand linear algebra, isn't going to increase your personal bottom line at all.
Many (most?) teachers are bad and the existing incentives don’t require them to be good. It’s hard to fire them and public schools have issues which limit selection and competition.
Perhaps harsh, but some of the dimmest people I knew in highschool became teachers and some of the meanest adults I’ve ever interacted with were teachers too. Obviously great outliers exist, but I’m skeptical they’re the norm.
Most jobs that have high demand, real evaluation of skill, and limited supply of people that can do it well (for whatever reason) pay well in capitalist markets.
The exception I can think of would be something like social work, where demand is high, costs are high and it’s mostly government funded.
The barrier of entry is way too low these days and therefore we have this hazing ritual for an interview process. It's absurd to think that after 12 years in the business, I won't be able to figure out what to do with those requirements. I'm sorry, we need 5 years of Java, not 4.
For those young developers, save up your money over a 10 year period and get out.
Likewise passing the bar isn't the barrier to entry to a good law career (at least not practically), it's getting through the interviews at a top law firm.
Many attractive industries have problems when it comes to deciding who's eligible to reap their rewards.
I would much rather click on a computer.
Medical field (being a physician) is not a walk in the park, but:
1. nobody questions you intelligence/knowledge after, say, 20 demonstrably successful years in the business
2. on your way home you can say "tough day, but at least I am making $600K/year"
This is one of the main reasons I'm a software engineer and shudder to think about doing anything else for a living, despite not even liking software that much.
> It's uncomfortable because many of us didn't understand this going in.
This is probably not as common as you think. Most of the SWEs I know switched over from other fields because it's an obviously easier gig. Epidemiology, architecture, electrical engineering, biomedical engineering, archaeology, public policy. People are painfully aware of how easy we have it and that's precisely why they're (we're) SWEs, not because of any interest in coding itself.
Thank gods while they're right - anyone can indeed write code - the valuable part of our labor is problem solving - and no amount of better tooling will change that.
Ultimately we are business people, we are accountants, we are tour operators and much more: our labor value is in the ability to transform these jobs into requirements and solutions, coding is how we describe our understanding of the domain, and it's production inconsequential once all the hard questions get resolved.
To bad today that gets a stench from the so called agile crowd, which would prefer us to tackle problem with aggressive randomness in the hope that infinite monkeys can be as cost effective as a single thinker.
Of course teachers who understand this also make money, see Miss Excel ( https://www.instagram.com/miss.excel/?hl=en ), who was/is making $100k a day with excel instruction videos on tiktok and instagram. It’ll all about leverage.
If teachers were paid a lifetime percentage of their students earnings teachers would make far more than software engineers. Barring some cultural revolution that’s not going to happen.
Software engineers simply make more money because the companies they work for have high margins.
Seems easy to prove wrong by trivially looking at high school dropout vs graduate incomes.
For example, they might be risk averse and a risk averse personality might lead to other decisions that make more money. (or the opposite)
It would be easy for a fad to arise calling education unnecessary and a waste of time, and for people to consider the option to drop out less risky just because it gets talked about more. So even if the correlation held statistically now, in any year it could change just because the subgroup of risk-averse people are more likely to consider it. So you still couldn't use it to make permanent decisions(like creating a school system for hundreds of years).
Homeschooling vs. high school graduates would remove "choice to drop out" from the student, but then "choice to homeschool" on the parents might carry down genetically or culturally and maybe "aversion to government authority" improves earnings on average.
I try to reject all statistics on "easily understandable" social topics. Leave that for scientists only. It's too easy to make a mistake and not get any warning that you made a mistake, and believe wrong things your whole life.
All observable evidence shows those who complete their schooling in any form make more money
I don't care whether schooling causes or doesn't cause a benefit: You called it "trivial" by looking at statistics, and that supreme confidence that there can be no other explanation seems unjustified.
> Seems easy to prove wrong by trivially looking at high school dropout vs graduate incomes.
There is an implied statistical argument here that by plotting "did X drop out" on one axis and their future income on another, that a correlation would refute a statement that "Schools cause students to earn less".
Specifically, you would be:
1. Gathering many examples of individuals(a "population") with boolean "did they drop out?" V1, some income metric V2, maybe some others.
2. Comparing and aggregating V1 and V2 across the population
3. Using it to refute a statement S
That is a statistical argument for ~S because it involves comparing population aggregates. You may not have explicitly used the word "statistics" or realized you did it, but you made a statistical argument.Time to get over ourselves people.
Thats a tautology, not analysis.
A teacher spending an hour in front of 300 kids might create 300 buisinessmen, so have you accounted for their contributuon to the conomy?
Why are we tech people so arrogant about our career? We already make good money, no need to think we're better than others.
If you write software in any given year that gets used by thousands or millions of others, you may also be enabling great things - either in capabilities or reduced friction shipped.
Also, successful software gets used for a long time, with additional work adding value on top of previous value.
So software work is leveragable without fundamental limits across both space and time.
This space-time leverage is true of all automation design.
In contrast, well done online courses can "automate" learning, but not as completely. The highest quality teaching involves meeting many students individual needs. And there is nothing automated about most teaching.
Poor teachers: when I was teaching it was more like 20% of the time, and the other 80% was breaking rocks. Planning, marking, parents, discipline, pastoral care, sports, and straight up babysitting.
That’s a big part of why the pay is so different, in my experience. Teachers have to put in a lot of time and effort to make a diff[erence] and the rest of the work is completely unskilled labor.
For SWEs, the next pull request is only limited by your ability to focus and type.
I’m a full time SWE these days, and enjoying the 10x pay.
I think the bottom line is that everybody should be able to earn a good living wage, regardless of their line of work. It feels broken that one would need to seek a specific job or set of jobs to have a hope of living comfortably.
There's plenty of suffering on top of that time and money too.
https://web.archive.org/web/20201112012023/http://www.medica...
You are also confusing our broadly speaking "professional" jobs with some of those other examples and firefighters have early retirement and DB pensions in the UK
Software development is heavily skewed towards the young demographics. We just don't think about it when we are young and still in love with computers. In the immortal words quoted by Steve McConnell over 20 years ago: "Wanted: Young, skinny, wirey fellows not over 18. Must be expert riders willing to risk death daily. Orphans preferred. Wages $25 per week."
If you get to your 40s as a dev and want that without leaving development, become a public sector (direct government, not contract) software developer.
That's why careers have a stock comp. Jobs don't.
> accumulate experience that's valued by their employers all the way to retirement
Real engineers do get that.
> don't need to emigrate/move to SFBA/NYC/London/Berlin > speak foreign languages > be surrounded by aliens from distant lands
I can't help but hear a dog whistle here...
I don't know about that. Software scales almost infinitely. Impossible to double the number of billable hours or patient load of a cardiologist outside of an herculean effort, but software folks can easily 10x the number of people they bring value to in a short amount of time.
> We didn't spend a ton of $ to go to medical school and 3 years of residency. We didn't go to law school and take the bar. Most of us went to 4 years, or less, of school, and here we are making great money by utilizing the greatest tool of all time: the computer.
Honestly, medical school isn't really the correct example to use because it's not efficient at all.
The big reason medical schooling is so hard is because they have to get a completely unrelated undergrad before even thinking about applying to med school. That means racking up serious debts before even knowing if you are going to get admitted. You can imagine how that fosters a culture of diversity and inclusion and help poor, often non-white, applicants reach medicine when the first step is to get into 6 figures debts with absolutely no guaranteed income.
Other countries with similar health outcomes for their population simply admit freshmen into med school right away.
Residency is something else. It's overworked since the total number of residents is capped by the AMA (also you have to fly-in to your residency interviews on your dime, so much for underrepresented applicants!) and honestly there's a lot of cargo culting. 48 hours shifts with no sleep because it's believed that it's impossible to correctly handover patients from one medical professional to the other (hint, this is a solved problem in a lot of high stress cognitive disciplines outside of healthcare). It's a culture of always working harder instead of working smarter, and the people take pride in that strangely enough.
All it really does is create a moat and allow AMA members to charge more because they made themselves scarce.
> Meanwhile, our friends who are teachers, firefighters, child-care workers, etc. are doing tough work daily for less pay, perhaps simply because they didn't use computers much or didn't like them. And yet, their jobs are ESSENTIAL and we need people to do them even though they're grueling and underpaid.
Firefighters tend to have nice pension funds in a lot of cities.
Teacher's pay is incredibly interesting. Engineers are paid on results (this is even more true at serious tech companies where a significant portion of ones earning will be stock comp) while teachers are paid a government approved rate no matter the results.
I know a lot of parents that would pay serious money to teachers based on results (if their kid can get into Stanford/MIT for instance) if said teachers could show a track record of having previously mentored alumni for instance. Instead, the premium is now captured by real-estate since parents that care will pay extra to get into a good school district.
14. Those who code for a living make good money.
I have a lot of friends who went into various fields, and it seems relative to the number of buttons we press daily, anyone who works on software makes great money. We didn't spend a ton of $ to go to medical school and 3 years of residency. We didn't go to law school and take the bar. Most of us went to 4 years, or less, of school, and here we are making great money by utilizing the greatest tool of all time: the computer.
It's uncomfortable because many of us didn't understand this going in. We liked computers for a long time, we had a penchant for working with them, and it turned out that made us great money. Meanwhile, our friends who are teachers, firefighters, child-care workers, etc. are doing tough work daily for less pay, perhaps simply because they didn't use computers much or didn't like them. And yet, their jobs are ESSENTIAL and we need people to do them even though they're grueling and underpaid.