A less generous take on this post is that an elite engineering team drove a perfectly competent developer out of the company by minimizing the perceived value of their contribution. I don't think that was good management, if so.

Fred Brooks, in the Mythical Man Month, identified the value of "toolmakers" to the "surgeons" many years ago. I think that model applies here too.

Seems to me that a better path would have been to ask the developer in question to lead the automation project, and generally push them over time to look for, and implement, improvements across the development chain that increase efficiency. The elite devs get to keep on doing what they do, but now the whole boat is lifted, and the dev gets to put some real wins on their resume.

I have a story about engineer vs technician. In my very first technology job (title was web assistant, so, very much technician) we updated our online education platform and suddenly all our course were breaking.

After some investigation we found that one line in an xml inside the course zip file needed changing. So, my manager planned how to do it. We'll divide the 40k courses into batches, different individuals would tackles certain batches and it all would be done in about 4-6 weeks...

Well, probably my ADHD brain or just being lazy but that sounded like an awful lot of repetitive work that I didn't want to do (change file extension to .zip, decompress, go to file X, find line with XYZ and replace for ABC, save, compress, change file extension back to proprietary format), so after talking with my boss and asking permission I got a week to try to automate that.

Back then I knew almost nothing about software development but I was aware of bash and python... so I cobbled together a janky script that would likely make me cry if I saw it now, tested it on 1 course, then on 10, then on 100... and then shared with my boss. It all worked perfectly! We still batches of about 1k courses at a time to confirm that everything was working ok, and in the end the job took about 2 days and 1 person (as opposed to 4-6 weeks and 5 people).

I was very proud of that accomplishment and very likely marked my perception of the value of software as a tool to decrease human effort (nobody got laid off or leaved, is not like we didn't have A TON of work apart from that migration).

Anyways, just wanted to share :-)

I’ve worked as a non software engineer with non software technicians, and I’ve spent a lot of time thinking about the differences. Most of the work done by engineers was also quite repetitive; in our case the big difference had more to do with whether you turned a wrench during the day, which mainly resulted from differences in your degree of formal education. I was quite junior at the time, however. Where experienced engineers made a difference was in their ability to change how we used the machines, where technicians generally did not. (Sometimes they did, and jumped onto the engineer or management track as a result.)

All of which is to say that I formulate a spectrum from technicians through engineers, to scientists. Technicians use technology, engineers devise new technologies using scientific facts about the world, and scientists discover new science. All three parties end up spending a lot of time on repetitive tasks, however.

Perhaps what makes computer science unique here is that it’s a science of automation, and as such it actually offers us the opportunity to reduce repetitive work.

I like the distinction between technician and engineering. So much of software development is just technician work and has nothing at all to do with engineering.

Unlike other countries in the US you can call yourself an engineer as a job description without any restrictions, so far too many people have taken on that job description, even if it does not make any sense.

The SREs have the word "toil" for work-that-has-the-technician-nature. Relevant page of the SRE book is https://sre.google/sre-book/eliminating-toil/ .

I like this distinction between engineer and technician

However, I think if the tech industry adopted this distinction formally, the outcome is that there would be far fewer software engineers and far more software technicians.

Which would probably actually be a good thing overall. Most solutions being built out in the world don't seem to need software engineers imo

In my country software engineer is a protected term. People get sued for calling themselves software engineers if they are not licensed. For me the difference between “software engineer” and “technician” is that the latter has a limited scope of work and is supervised by the former.

I think it’s a good idea to have a mix of both. There is a certain amount of toil involved in large systems and automating every single task is not always worth the effort. It’s nice to have technicians around to help with that toil.

Predictability is great for everyone, from managers to directors to even company investors. What everyone wants to see is consistent yoy/qoq growth. We should all strive for this kind of consistency.

However, balancing this consistency with new adventures is where things get a bit tricky. I kind of like Jeremy Howard's approach to learning here. I don't know if it can be applied to a company or a team scale.

Spend 50% of your time on predictable tasks, those that you have mastery over and can do comfortably. Spend 50% of your time on frontier stuff things that break your comfort zone.

Over time the some of the latter tasks will get into the former category, thereby leading to automation organically.

The ratio of comfort:frontier tasks is personal and let's engineers choose their ratio. Some may want the ratio tilted in the comfort zone (greater predictability ) while some may choose to adventure into the frontier zone (lesser predictability ). An organization should have space for both. Even the same individual can alter these ratios based on their life stages, external circumstances.

Put rather simply, a good software engineer can also choose to be a good technician and vice versa. Why should these roles be mutually exclusive ?

All too often the cost of automation is higher than the cost of just doing the work manually each time. While the example case that doesn't seem to be true, it isn't clear if they did the analsys. if the manual project took 5 minutes every week and the automation took 2 engineers 2 weeks, it will be 2000 weeks before the automation effort pays off - will you need it that long - don't forget that if the process changes you have even more effort in automation, now add in interest on the investment...

Of course as time goes on we get better automation tools. what used to not be worth automating often is today.

Don't forget that humans tend to be good at noticing "thats funny" situations while automation will pass many of those situations because you didn't think about them and thus didn't handle that error. This is why despite being a big deliver in automated tests I still demand a large amount of time spent in manual testing everything.

I have, at some point in my career, had the title of "Automation Engineer" in the past. I generally agree with the article except there is one huge oversight: Automation requires predictability as a prerequisite and complex systems are not naturally predictable. It takes effort from smart people to ensure the predictability of a system and repeat a task long enough that it can be automated.

> But it wasn’t great for the business!

That is a pure and virtuous stance.

I typically refrain from giving management ideas of this sort. It's not a given that the pros outweigh the cons - especially in large organisations.

In any case I'm currently in a project which was supposed to be for Technicians, but I need to do a lot of Engineering due to, well, bugs and tech debt.

My take is that any sufficiently long running project, even if originally simple, creeps beyond the skillset of Technicians.

The difference between technician and programmer isn't about predictability, it's about novelty.

The technician has to know the system well enough to respond correctly (or even proactively with preventive maintenance, etc.) to unpredictable problems that are "in the book".

The programmer by definition solves novel problems.

- - - -

edit to add: Beware folks who look down on technicians. It's a kind of "code smell" of the mind.

> We wrote some code to automatically generate an HTTP API from the corresponding gRPC API

It's possible to do this without writing code. https://github.com/grpc-ecosystem/grpc-gateway

You can even get it to generate Open AI style documentation.

The root of all evil is beliefs in some form of exceptionalism that exempts you from having good worksmanship.

Being so special you are exempt from having to write documentation, tests, give visibility, etc.

Automation is can be partial, like series of scripts that are ran manually.

This take makes sense in the context of the specific example, but falls apart for most other software engineering. You can't automate away defining business logic, but in many cases you can deliver it predictably.

I use the terms "bespoke work" and "commodifiable work" to differentiate the two kinds of work in the article.

I think the article misrepresents what actual technicians do and their value.

I wish we had a definition for machine learning engineer

This is like comparing DevOps engineers and Systems Administrators.

Both extremely important to the business but sysadmins are perceived at a lower level?

Thus we don't need that much software engineers. Things should start to get cheaper (considering everything else the same).

"I've learnt that Von Manstein (and others) paraphrased Prussian Field Marshal Helmuth Karl Bernhard Graf von Moltke (1800-1891) who categorised his officer corps into four types.

Intelligent & Lazy: I make them my Commanders because they make the right thing happen, and find the easiest way to accomplish the mission.

Intelligent & Energetic: I make them my General Staff Officers because they make intelligent plans that make the right things happen.

Stupid & Lazy: There are menial tasks that require an officer to perform.. and they follow orders without causing much harm

Stupid & Energetic: These are dangerous and must be eliminated. They cause things to happen, but the wrong things, and so cause trouble."

it is an extremely dangerous thing to think of being a "technician" as less important or lower status. until such work is automated (and I strongly believe it should be) then bad configurations will get pushed to production and bolts on doors will not be tight.

i find this article to be overly long

≥≥ Unlike other countries in the US you can call yourself an engineer as a job description without any restrictions, so far too many people have taken on that job description, even if it does not make any sense.

This is one of my pet peeves... in Engineering school it is beaten into you that what you build has to be correct. Correct as in, did you check the poles and zeros? Is this thing going to oscillate out of control and kill people in any breeze? Is this circuit ever going to go into a region where it will fail, probably killing people, and did you ensure you have circuitry that will prevent that? Is every floor of this building rated for the loads, winds, seismic activity, etc.

I feel like in software, there used to be a lot of focus on correctness of algorithms. In undergrad computer engineering we had to take algorithms and again in grad school. That class seemed like the one to teach you to be correct, but it was just in your algorithm design. So much of software today controls hardware that may end up controlling (insert your deadly item here: life support, airplanes, cars, trains, critical infrastructure, deadly infrastructure, etc) that it makes me wonder just how much holistic testing of the "in which ways can this software fail and kill people" has taken place.

According to the dictionary, engineer is defined as: A person who designs, builds, or maintains engines, machines, or public works.

You may have a point that the prevailing idea of what engineering is does not recognize software as an engineering discipline as it does not fit into any of engines, machines, or public works. But if we were to include software, surely all software practitioners are people who design, build, or maintain software? Even the web API guy from the story is an engineer on that end.

I think there is a distinction in general. On the other hand, as someone with degrees in other areas of engineering, I also think there can be too much emphasis placed on the degree to which those other areas of engineering apply formal process and rigorous practices to everything they do. Yes, there are established codes for structural analysis and the like but there's still also a lot of seat of the pants.

> Predictability is great for everyone, from managers to directors to even company investors.

I think it's terrible for the knowledge worker, causing both great emotional turmoil (at the dissonance of expectation versus how they actually perform) and reducing quality of output greatly (by forcing output when more dweel/pondering time is required).

Hammock Driven Development by Rich Hickey was such a an enormous relief of a talk to run into, back in the day, hit upon so many tensions & frustrations I had because business Taylorism expected consistent output, expected me to know the process from a->b and to be able to say at every point I am x% of the way through the journey. The businesses doesn't know what's happening but cares enormously about making sure it's extracting as much consistent "progress" as it can out of me/us.

HDD talked to how analysis & understanding, how development & problem solving iteration really work. And it works nothing like what a business wants. And what a business wants hurts the quality & doesn't permit ideal outcomes to emerge & surface. https://github.com/matthiasn/talk-transcripts/blob/master/Hi...

And the human factors are that dwell and pondering are essential for creative and knowledge work. Time in the hammock opens possibilities, fuels the muses.

> Spend 50% of your time on frontier stuff things that break your comfort zone.

That would be so excellent. I still get that mandate a lot, but so often I see peers whose whole life is cranking out pre-digestrd ready-to-go tickets. I want to see a world where we raise up engineers & engineering, not just ticket technicians.