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”
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.
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.
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.
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.
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"
"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.
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.
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.
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.
Actually, no. It is a HR concern. HR need to put people into boxes. Most people dont actually fit but whatever.
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.