I don't think so.
You ask the contractor for what you want, iterate a little, and take what they give you. Sometimes you may read the results.
Yours sincerely, Software Developer with 6 years of experience. Last week for the first time in my career I've actually merged application code. It was AI generated.
I'm confused about the point he's making here with the 6 years thing.
It's a weird one, because recently I've been working on a JS based system when I don't know JS and it's definitely very very different from when it's a language you're familiar with.
Software "engineers" in North America don't have any actual professional board that licenses or oversees their work. Until governments actually regulate the profession through these bodies, no one can gatekeep software development job titles.
A bunch of blog posts talking about "industry standards" is not a reference point for this.
So I wonder if users of "heavy AI" should also need to have a license.
Will your model and harness be the same in enough time to develop a curriculum for it and disseminate that to enough people to give it enough of a reputation to be worth doing for students, before it's obsolete?
I'd argue no on both counts.
This work has key differences vs operating heavy machinery.
Using an LLM doesn't carry any inherent risk. It's the people working on software for safety critical systems that require relevant oversight. Irresponsibly turning an LLM loose on a safety critical codebase would be nothing short of professional negligence (at absolute minimum).
Well depends what your runaway AI goes hacking… people might indeed die.
It depends on the way they use it. If you design an architecture and use an LLM to fill it in, I'd consider a more technical label. If you're just using what Claude made, and providing feedback, that's just how software was done 10 years ago except then they'd be talking to a guy instead. And it would be orders of magnitude more expensive.
From my perspective, Claude feels like 5 engineers in a box. you can make things that required small organizations to make.
If you’re building and producing valuable software, you are still a creator or software engineer full stop. We can argue over titles, but don’t demote your own creative process to passive consumption.
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.
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.
Actual engineers, doctors and lawyers are given that title not through education but through actual legally-recognized standards bodies. These are standards bodies that certify them, review their work, can investigate deviations from standards and even delicense people if needed.
In North America, there aren't any such bodies for software development. So trying to gatekeep this term because of a university degree is absolutely not the same thing as lawyers, doctors or mechanical engineers.
I would be fully supportive of gatekeeping this btw but pretending that its the same as doctors and lawyers is ridiculous.
Until there are actual standards bodies overseeing this, sorry, your university degree equally means the same as anyone self-taught so long as no one actually oversees the work and certifies people.
As an example, I moved from Software Engineering to IT Controls Analyst. The pay brackets are lower and there are way fewer job postings. Even this chart of software related job completely leaves out any compliance or audit function, illustrating just how little my own profession thinks of us.
The point being: I'm always amazed at the cross-purpose impulse of arguing "the title is not important" while, simultaneously, really wanting to use the title.