News for hackers. Stuff that matters.
Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @07:54AM (#43600769)
I was talking with friends at a party last night about their white collar jobs, and yeah, SWE was the easiest and cushiest job in the room by a mile.

One friend had just finished a 3 month program to certify to fly a certain type of airliner. They probably had more intense study and testing in 3 months than most people do in a 4 year undergraduate program, SWE included.

Re:The Insanity of Being a Software Engineer by saurik on Sunday April 06, 2025 @07:57AM (#43600787)
> I was talking with friends at a party last night about their white collar jobs, .... One friend had just finished a 3 month program to certify to fly a certain type of airliner.

An airline pilot is "grey collar".

https://en.m.wikipedia.org/wiki/Grey-collar

https://www.forbes.com/sites/jackkelly/2024/02/01/gray-colla...

Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @07:59AM (#43600796)
I don't think anyone in that room would have agreed with that term.
Re:The Insanity of Being a Software Engineer by trallnag on Sunday April 06, 2025 @08:08AM (#43600851)
Why?
Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @08:12AM (#43600888)
Frankly, trying to claim their jobs, which all require more education and have much higher pressure and consequences for error than mine, aren't white collar would have been rude and insulting to everyone.
Re:The Insanity of Being a Software Engineer by goda90 on Sunday April 06, 2025 @08:33AM (#43601001)
Did you read the Wikipedia article? Grey collar is work that takes both intellectual and physical skill. It even includes surgery as grey collar. Thinking white collar indicates more education and pressure is the issue. There's white collar jobs that can be done by high school graduates, and blue collar jobs where life and death are literally a split second away most of the time.
Re:The Insanity of Being a Software Engineer by marcusb on Sunday April 06, 2025 @08:58AM (#43601131)
I get that people want to Categorize All The Things, but this doesn't seem like a particularly useful category. If you look at the list in the Wikipedia article, it includes "skilled tradespeople/technicians". That alone represents a pretty big chunk of work traditionally considered "blue collar."
Re:The Insanity of Being a Software Engineer by goda90 on Sunday April 06, 2025 @09:01AM (#43601141)
Whether you want to use a "grey collar" category or not, it's still best to avoid putting white collar on a pedestal over blue collar.
Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @08:43AM (#43601052)
The Wikipedia article that comment linked to in a later edit says it's a controversial definition and says that such professions are typically described as white collar. That seems to support my statement?
Re:The Insanity of Being a Software Engineer by nkrisc on Sunday April 06, 2025 @08:50AM (#43601087)
It's equally insulting to insinuate that some blue collar jobs don't also require more education and have much higher pressure and consequences for error than many white collar jobs.

There are many blue collar jobs that require a lot of education and the consequences of errors is loss of life.

Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @08:58AM (#43601132)
Most of the people in that room had worked blue collar jobs, worked through school, and retrained in white collar professions.

I would have been incredibly rude to tell them "No, your job isn't _really_ white collar, and you haven't changed your social standing as much as you thought."

Re:The Insanity of Being a Software Engineer by jart on Sunday April 06, 2025 @12:24PM (#43602660)
In the US about 60% of the workforce is "white collar".

Being proud of that is like being proud of a six figure salary in California.

Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @03:04PM (#43604026)
A person cannot be proud of their individual achievements, self improvements, working at a job they wanted, or providing for their families? Simply because many others have done the same?
Re:The Insanity of Being a Software Engineer by robocat on Sunday April 06, 2025 @04:44PM (#43604819)
Are you saying 60% of California workers earn minimum six figures?
Re:The Insanity of Being a Software Engineer by tanjtanjtanj on Monday April 07, 2025 @11:48AM (#43612796)
White/Blue collar, while correlated with income, has nothing to do with social standing.

A friend of mine is a construction foreman. He lives in a mansion in a suburb of a suburb, is a member of a highly regarded country club and makes more money than me. He’s blue collar.

Re:The Insanity of Being a Software Engineer by p3rls on Monday April 07, 2025 @05:39PM (#43616246)
Some weird caste-based thinking straight from the subcontinent you've got there
Re:The Insanity of Being a Software Engineer by nkrisc on Thursday April 10, 2025 @09:36AM (#43643642)
I don't know what country you live in, but social standing in the US typically has more to do with wealth, not the color of your collar, so to speak. It is not hard to find wealthy blue collar workers who have high social standing in their communities and beyond. Take for example a master plumber who owns their own business, or a general contractor who's grown their business in a large city. I suppose you could argue their roles tend to transform more into white collar roles of managing the business, but it's blue collar work and work that they did and probably still do themselves.

On the contrary you can absolutely be a white collar worker with low social standing in the US. It's not hard, I'd even argue most white collar workers fit that description. Think of a customer support representative working in a call center for wages. Their job is definitely white collar but it does not pay well and is the type of job you typically associate with someone struggling financially. Not someone of high "social standing".

In the US blue collar/white collar does not directly correlate to low/high social status. While it is probably true that white collar work is correlated with higher wages or salaries, it's the money that drives social status, not the color of your collar.

Re:The Insanity of Being a Software Engineer by saurik on Sunday April 06, 2025 @05:20PM (#43605051)
I find your definition of "insulting" really confusing, as pretty much all "white collar jobs" are "I sit on my butt all day and think lazily about things with very little pressure" jobs. They push paper and write reports on things, maybe doing some annoying math at times, but the entire concept of a "high pressure" job with "consequences for error" seems entirely at odds with white collar, and I'd personally have expected people who actually do something important on a daily basis (unlike, for example, me) might would find being categorized as "white collar" insulting?
Re:The Insanity of Being a Software Engineer by robocat on Sunday April 06, 2025 @04:49PM (#43604859)
That's foolishly confusing.

It breaks the original metaphor, and nobody knows it or the confusing borders of the definition - bad for communicating.

Most people seem prideful to self-identify into blue-collar or white-collar.

What's the meaning of the obviously next step pink-collar or black-collar?

Re:The Insanity of Being a Software Engineer by eszed on Monday April 07, 2025 @04:40AM (#43609229)
A couple of decades ago I heard "pink-collar" used for jobs that were female-coded (nurse, teacher, personal assistant). <shrug>

Yah. Profusion of terminology is confusing.

Re:The Insanity of Being a Software Engineer by grandempire on Sunday April 06, 2025 @08:07AM (#43600840)
> a 3 month program to certify

Industries with difficult certifications tend to protect those when awarded. It’s a grind to get in but then the employment is easy and lucrative.

This is the promise of a career as a pilot or doctor. (Inb4 doctors do hard things)

In contrast, industries that are lucrative but have a low barrier to entry (sales, real estate, etc) tend to have direct performance competition.

Re:The Insanity of Being a Software Engineer by Ygg2 on Sunday April 06, 2025 @08:05AM (#43600835)
> One friend had just finished a 3 month program

In software by the time you finish your 3 months course the tech is considered obsolete.

Not just Frontend. Backend can change on a dime.

Elastic/MySQL/CockroachDB is using different license that's incompatible to AWS. We have to switch our stack!

Kafka is out. It's all about Iggy! What do you mean it's different language? Learn it!

Things can be hard in different ways. After coding for whole week doing garden work can almost come as a relief.

Re:The Insanity of Being a Software Engineer by grandempire on Sunday April 06, 2025 @08:10AM (#43600871)
> by the time you finish your 3 months course the tech is considered obsolete.

This is a meme that’s just not true. Nobody outside of the most junior applicant or most transient contractor is paid for the skills they learned this year.

The most important skills last forever. Getting a good CS or EE degree is still the best way to get started.

Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @08:16AM (#43600905)
Exactly. In the past ten years the main differences in my professional tech stack are that I write Go instead of Java and my software runs in containers on Kubernetes instead of JAR files on CentOS. My friends have all had much more significant changes and retraining in their careers.
Re:The Insanity of Being a Software Engineer by grandempire on Sunday April 06, 2025 @08:23AM (#43600942)
Yep even within internet technology this is ridiculous. Imagine we time machined a Perl old-head from 1995 only knowing http, Unix, networking, etc. They could be invaluable at any company in a month.
Re:The Insanity of Being a Software Engineer by FirmwareBurner on Sunday April 06, 2025 @12:46PM (#43602831)
>They could be invaluable at any company in a month.

That's a made up fantasy. They wouldn't get hired at all in real life. Ask me how I know. Where I live recruiters only check that your recent experience and stack match the ones on the job, otherwise your resume goes in the bin.

Like Ygg2 said below, employers don't want generalists with generic CS knowledge, they want people they can immediately slot in and start crushing Jira tickets.

Re:The Insanity of Being a Software Engineer by grandempire on Sunday April 06, 2025 @01:34PM (#43603198)
> employers don't want generalists with generic CS knowledge

That's not true. Like I said, this is more of a problem if you are trying to break in.

> people they can immediately slot in and start crushing Jira tickets.

This is representative of the only the most precarious software contracts.

> They wouldn't get hired at all in real life.

I have hiring capability and I would hire them.

The poster said their skills would be out of date. I think you're confusing a sales problem for a skill problem.

Re:The Insanity of Being a Software Engineer by FirmwareBurner on Sunday April 06, 2025 @01:40PM (#43603257)
>That's not true.

It's the case wherever I applied, which makes it true for me.

>This is representative of the only the most precarious software contracts.

Same argument as above.

>I have hiring capability and I would hire them.

Where are you located? Do you hire fully remote?

Re:The Insanity of Being a Software Engineer by grandempire on Monday April 07, 2025 @03:25PM (#43614931)
> Do you hire fully remote?

I think this may be the real problem you are facing.

Re:The Insanity of Being a Software Engineer by Ygg2 on Sunday April 06, 2025 @08:26AM (#43600956)
> In the past ten years the main differences in my professional tech stack are that I write Go instead of Java.

Ten years isn't enough time to standardize something and make it a job requirement.

Re:The Insanity of Being a Software Engineer by dharmab on Sunday April 06, 2025 @08:41AM (#43601034)
Do you want the list of things that haven't changed since I started programming as a kid?

I still write a lot of Python and shell. I still use Linux, mostly systemd. (I did have to use initscripts early on and do not miss them at all. systemd's way easier.) The entire networking stack has changed only minimally, with only early versions of SSL/TLS becoming obsolete. All the software I use to do my job is the same (A terminal, Vim, Firefox, GNU coreutils, and a smattering of other tools). I still use the same cloud services and databases. The skills I learned in school are equally as useful today as they were then, especially math and CS theory.

The only major shift during my career has been migrating from Linux VMs to containers on clusters (first on Mesos, then Kubernetes). Having administered both at scale, Kubernetes is a lot easier.

Re:The Insanity of Being a Software Engineer by Ygg2 on Sunday April 06, 2025 @11:21AM (#43602086)
> I still write a lot of Python and shell. I still use Linux

All of those listed things have changed. Python went from 2 to 3, number of shells has multiplied like rabbits. Linux changed in leaps and bounds. It got async, BPF, different tech stacks, and window environments.

> Do you want the list of things that haven't changed since I started programming as a kid?

Sure basic principles have remained the same, but huge chunks of ecosystem have been transformed. Perhaps we are looking at it from different perspectives.

It's kinda like ecosystems. Amazon tropical rainforest looks the same now as it did 1000 years ago from birds eye view. But on the ground entire species came and went, and the species living there changed dramatically, in quality and quantity.

My issue is, employers don't want general knowledge, they want an easily slottable asset. You need to know their tech stack. Even if it changes. Hence why LLMs are so in demand.

Re:The Insanity of Being a Software Engineer by MrJohz on Sunday April 06, 2025 @04:36PM (#43604763)
Python 3 is not that different from Python 2. Yes, if you're a mindless interpreter designed to specifically parse and evaluate Python 2 code, you're going to have a hard time with Python 3. Thankfully, software developers are humans and should not have this issue.

The number of shells that are relevant to any workplace I have worked in have been two, possibly three if you're working somewhere heavily Apple-based. All three of these shells are POSIX-compatible. Other shells exist, but are entirely optional and rarely used (I say this as someone using one of those other shells).

Linux has changed more, and is probably the biggest source of change in the list that the previous poster described, but as they point out, most of these changes make managing Linux systems simpler, and shouldn't really cause significant problems.

I think you're strongly exaggerating the scale of changes here.

> My issue is, employers don't want general knowledge, they want an easily slottable asset. You need to know their tech stack. Even if it changes. Hence why LLMs are so in demand.

I'm a frontend developer. Every job I've had, I was not familiar with the specific framework they were using when I went in for that job. In every case, that's not been a problem at all, because I've been able to clearly demonstrate that I understand the foundation of frontend development, which is far more important than the precise technologies used in the company's framework of choice. My experiences in general are the complete opposite of what you describe here: every single employer that I've worked for has wanted primarily deeper general knowledge rather than specific knowledge of their specific stack.

Maybe this is a market thing — maybe things really are that different here in Europe — but your descriptions do not ring true at all for me.

Re:The Insanity of Being a Software Engineer by grandempire on Sunday April 06, 2025 @08:29AM (#43600972)
The comment we are responding to said it takes 3 months for tech skills to go out of date.
Re:The Insanity of Being a Software Engineer by hardwaresofton on Monday April 07, 2025 @10:43AM (#43612100)
> Kafka is out. It's all about Iggy! What do you mean it's different language? Learn it!

Are people really using Iggy/hyping it already? TIL it's now an Apache project[0], that's awesome, it looks impressive!

Sure, most reasonable people are definitely not ripping out Kafka for Iggy yet, but I'm certainly happy to hear it getting more usage/at least being considered.

[0]: https://blog.iggy.rs/posts/apache-incubator/

Re:The Insanity of Being a Software Engineer by ltdanimal on Sunday April 06, 2025 @05:41PM (#43605191)
Maybe we should agree that all jobs can't be compared apples to apples. I have 3 good friends that fly for major airlines. I'm pretty familiar with the jobs.

-Those tests are no joke, but saying they are more intense than a 4 year CS degree is ridiculous. Also the major airlines you can compare to FAANG, and many people study for 6+ months to pass those interviews - Airlines are union jobs. If you get them you aren't getting fired unless you try to do something really stupid. - There isn't any wondering if you are doing a good job or not , and you don't take any work home. - Regulations change or you can switch planes, but the career is leaps and bounds more static then SWE.

Net net is that they are very different jobs. SWE is a great gig overall but I take issues with people saying how much harder or easier it is than other jobs. "It depends" is the answer.

Re:The Insanity of Being a Software Engineer by vunderba on Sunday April 06, 2025 @10:28PM (#43606998)
Yep. OP fell into the classic trap of making generalizations across two COMPLETELY different fields despite only having knowledge in one of them. I got my PPL nearly a decade ago (obv a far cry from ATP but still) and it's ludicrous to try to compare the skill sets of computer science to piloting.
Re:The Insanity of Being a Software Engineer by dghlsakjg on Monday April 07, 2025 @11:58AM (#43612906)
That's it. Piloting isn't easy, and you do have to study a lot, but it is rote memorization for the most part.

That is a completely different kind of thing than the kind of thinking that we do in programming. One isn't better or easier than the other, just different.

Re:The Insanity of Being a Software Engineer by deeelle on Sunday April 06, 2025 @06:06PM (#43605356)
I feel like I've experienced the opposite honestly. I'm a mechanical engineer, and my wife's old college friends consist of a bunch of silicon valley techies.

Out of 10 people off the top of my head, most of them have been laid off in the past 5 years. For the ones that found new jobs (that I know) they are not satisfied with their pay.

I've talked my pay vs theirs and am shocked. Almost a decade worth of experience, making what I was making 4 years into engineering, in non management positions, and worse job security.

I could be mixing up programmer vs SWE. I just call them techies.

Re:The Insanity of Being a Software Engineer by fvrghl on Monday April 07, 2025 @10:34AM (#43612000)
Can you give your salary (or a range)?

Seems shocking that a SV swe would make what a mech eng makes after 4 years.