News for hackers. Stuff that matters.
Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @03:07AM (#50505016)
I have a bachelor of Software Engineering that is fully accredited by the Australian institute of Engineers. It was two years longer than a C.S. Degree.

Software Engineering is about so many things other than code it was an ongoing debate if code and programming should even be taught at a university level course, and while contemplating my masters of S.E. I had many great conversations with faculty about the distinction. Writing code is much more akin to welding or wiring, therefore belongs at a trade school, not a university.

After all, the discussion goes, Aerospace and Electrical Engineers don’t learn the doing of welding or pulling wires through crawl spaces, why should Software Engineers concern themselves with the doing of code.

>a S.E. should be able to differentiate good code from bad

A software Engineer needs to have all phases of the SDLC in mind, and be thinking about and planning all of them. Code is a tiny piece of the puzzle.

I’m thinking about requirements gathering, designing, testing, deployment, maintenance, long term change strategy, hand off to a new owner, etc, etc.

I could always see the merits of both sides of the discussion. Then at my first few jobs it very quickly became clear that many CS grads were just there to write code and that’s it. They didn’t have the big picture ideas at all, and I immediately understood the difference of a Software Engineer.

Re:A Family Tree of Software Job Titles by f1shy on Sunday November 15, 2026 @03:21AM (#50505077)
Just let me give my 2ct: as somebody that did search for hiring EEs and mechanical engineers, I really searched hard for the ones that DID soldered, pulled wires and welded, even for management positions. They use to manage much better, had better communication with the team, had better feeling for quality, could look much further in the furure and had much more authority, begin way more respected by the team.

That being said,

> A software Engineer needs to have all phases of the SDLC in mind, and be thinking about and planning all of them. Code is a tiny piece of the puzzle.

I would not AT ALL call it tiny. Yes, is one part of MANY. But is your final delivery. Would be like a Toyota saying: “hey they don’t really have to understand what makes a good car, the cars we sell is a tiny portion in the whole development cycle”

Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @03:30AM (#50505120)
I remember a professor who used to say “If the requirements, design, test plan and acceptance criteria are done to a high enough standard, the code can be written by a monkey.”

Which is exactly what we’re seeing now with LLMs writing code.

Interestingly you’ll see the same building a mega bridge or skyscraper. As long as the plan has been done well, it can be assembled by relatively very unskilled labor.

Note the test plan and acceptance criteria could be one and the same, depending.

Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @07:19AM (#50506400)
> If [everything before coding] are done to a high enough standard

That "if" is doing an unrealistic amount of lifting, here, in practice, and that's probably why human coders have had a better run than monkeys.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @06:59PM (#50512260)
I'd disagree as we have counterexamples all over the place in the real world. For software there's LLMs - it is clearly possible to use them to implement large projects autonomously provided that your requirements are sufficiently well thought out. Zooming out to other disciplines any large construction project fits the bill. Clearly a "high enough" standard is achievable.
Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @07:15PM (#50512394)
Just talking about software engineering, I think that the places where requirements are strong enough to be implemented unambiguously, are few and far between. So, it's "clearly possible", but rare, in my universe, your mileage may vary.
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:22PM (#50512446)
And yet somehow people are successfully leaving some projects almost entirely up to agents. Does that not run directly counter to what you're saying?

Also I will observe that something being rare is not in and of itself an indicator of whether or not it is reasonable. Many things are done a certain way because that's the conventional approach or it's more cost effective or due to some logistical concern.

In the case of software development it was previously cheaper not to exhaustively specify everything up front but I'd argue LLMs have upended that longstanding status quo within only the past year.

Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @08:02PM (#50512763)
I don't think that runs counter...

We had humans that were smarter than monkeys, dealing with imperfect requirements. Now we have LLMs that are smarter than monkeys, dealing with imperfect requirements.

LLMs don't work because of good requirements input, they work despite the poor requirements they're given.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @08:56PM (#50513102)
Okay but all you're arguing at that point is that it will continue to be rare because LLMs that exceed the capabilities of monkeys are readily available and not that much more expensive than their less capable cousins. Not that there's any inherent reason it's unrealistic to do so. With skyscrapers it's cheaper to make sure the specification is bulletproof and with software it's cheaper to kick it out the door while it still has more than a few holes in it.
Re:A Family Tree of Software Job Titles by f1shy on Sunday November 15, 2026 @07:25AM (#50506423)
> If the requirements, design, test plan and acceptance criteria are done to a high enough standard, the code can be written by a monkey.

Nice sentence. But it has 2 problems:

1) Define "high enough" - There is where good requirements start, make it measurable!

2) Related to "you’ll see the same building a mega bridge or skyscraper". I've seen enough cases where "unskilled labor" messed up building something. You will reply "that is why I said 'Acceptance Criteria'!". My take is: you are making it far more complicated than it should, taking totally unnecessary risks, and it will be invariably more expensive in the long run.

I mean, I've seen enough examples of cases where the acceptance criteria was not properly checked, because also the ones doing the test were "unskilled" and had received a "perfect plan". (Just look at any infrastructure disaster we have every year)

And even in the best case: you discover the poured cement does not meet the specifications. What now? Blow the thing and start over? Better to have skilled labor.

Again, my 2ct. experience: hire experienced people, who actually have done the work all the way down to the lowest level.

"If you think knowledge is expensive, try with ignorance"

[dead]
Re:A Family Tree of Software Job Titles by julianlam on Sunday November 15, 2026 @02:43PM (#50509983)
It's a bunch of engineers (by title) doing what they can to gatekeep those who dare not pay the piper out of the jobs.

"Engineer" is a restricted title in Canada... and so it should be, but I don't think it should be used keep people away from software eng work.

Re:A Family Tree of Software Job Titles by randomaccountpe on Monday November 16, 2026 @01:08AM (#50514555)
This was my general thought too.

I do think there should be reasonable restraints before we start labeling people, but I often see this go too far both ways.

Restraining job titles too hard in circumstances where job X is obviously qualified to do job Y, it comes across as ignorance or an emotionally driven decision.

Or not restraining hard enough (I can't think of many examples, other than where someone just obviously hasn't put in enough work to be qualified for the job).

I don't want to say it's ego-driven, but it sometimes across like that.

Re:A Family Tree of Software Job Titles by mike50 on Sunday November 15, 2026 @06:48AM (#50506223)
Electrical Engineering programs have practical labs where you build electronic projects and run wires. Most electrical engineers don't work in power or building engineering. Senior design projects (for undergraduate) have to be mostly built by the students. Metallurgical Engineers and Welding Engineers take welding courses not Aerospace.
Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @07:10AM (#50506354)
Absolutely , you’re right.

Of course no Electrical Engineer would be able to tell you the building code requirements for how close an outlet can be to a sink, or the ground, or a window. Every electrician can.

No Aerospace Engineer will be able to weld strange metal combinations, or be great at aluminum and thick stainless and oil pipeline pipe. Every ticketed welder can.

When you want the doing done, it’s great the Engineer has a working knowledge, which no doubt makes the project better, but no way in hell you get them to do it on the real thing. You get the ticketed tradesperson.

Re:A Family Tree of Software Job Titles by squishington on Sunday November 15, 2026 @07:29AM (#50506448)
If writing code can be considered a trade, what about debugging? What about debugging a complex embedded system? I'm not sure what i should call myself. I usually just say programmer because it's easier to say that. I did an electronics and communications degree at an Aus uni, focusing on DSP and FPGA. I had 2 FPGA jobs, one in defence and one in medical devices. Now I've been working with embeddes software for 7 years for a chip company. I'm still not sure if I should call myself a Software Engineer, even though that's what it says on my contract. I occasionally find gaps in my software engineering knowledge, but i learn as i go.
Re:A Family Tree of Software Job Titles by AQuantized on Sunday November 15, 2026 @08:32AM (#50506809)
I don't understand the view that coding is like a trade; even with a good idea of the systems involved and an intended design, I often find out things while coding that change the perceived optimal design substantially. I don't think this is nearly as likely to be the case with wiring or welding, and may even be impractical to change regardless given the less mutable nature of the metal or electrical systems you're working with.
Re:A Family Tree of Software Job Titles by giantg2 on Sunday November 15, 2026 @08:45AM (#50506904)
I think you're vastly underestimating the complexity and possible technical variations involved in welding and wiring at an industrial level.
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:03PM (#50512300)
> I don't think this is nearly as likely to be the case with wiring or welding

The same thing can happen. The difference is that there's more work put into surveying ahead of time, more work put into planning in advance, and if changes do turn out to be necessary it requires a round trip with the relevant accredited architect, engineer, etc.

Re:A Family Tree of Software Job Titles by sdeframond on Sunday November 15, 2026 @12:28PM (#50508768)
I've come to think there is a good amount of BS, bikeshedding and misplaced ego in making these distinctions.

Actually, no. It is a HR concern. HR need to put people into boxes. Most people dont actually fit but whatever.

Re:A Family Tree of Software Job Titles by LtWorf on Sunday November 15, 2026 @05:32PM (#50511573)
I'm not sure how _not_ knowing how to do something very important and central to your objectives should be a quality.