"where (s)he will face his(her) greatest challenge yet...confronting the darkness within and uniting the forces of good in the final confrontation of the galactic (tech) civil war..." - Return of the Jedi (C) 25-May-1983
There is a civil war raging in the tech galaxy—a war of definitions. What exactly is a software engineer versus a software developer?
Since the dot-com boom, the global demand for software creators has skyrocketed, often outpacing supply. This has posed unique challenges for industries like automotive and manufacturing, where disciplined software development is essential, but compensation is often lower than in trendy West Coast "tech" firms. These sectors are frequently mocked as outdated or less innovative—unfairly so.
Enter generative AI—and more recently, Agentic AI—which has introduced new ways to accelerate code creation. Since 2020, job postings in software have steadily declined, signaling a shift. This transformation doesn’t mean the end of software engineering; rather, it marks a renaissance.
Important distinction: I say Software Engineering, not merely coding. AI-assisted code generation is shining a light on the difference between writing code and engineering software based or enhanced products.
This shift has caused fear and confusion, particularly among those who’ve long blurred the line between developer and engineer. Some tech leaders lament the “death” of software engineering (often misusing the term), but others recognize that AI is a tool—not a replacement—for real engineers. As Mary Shaw and Eunsuk Kang note:
"The discipline of software engineering encompasses the full scope of software systems from concept to retirement...from understanding the problem to evolving the system over time."
Your grandfather assembling a Heathkit didn’t make him an electrical engineer. Likewise, building a hobby project with Arduino doesn’t make you a software engineer. Even if your job title says so.
To be a software engineer, you must practice software engineering—consistently and rigorously.
In my 30 years as a degreed and practicing software engineer (and 35+ in product development & consulting), I’ve witnessed a steady decline in genuine SE behaviors. But the tide is turning.
AI isn’t replacing engineers—it’s amplifying the value of those who understand the problem, not just the code. Engineers who can articulate the problem space and map it to structured, evolving solutions will be in demand. This clarity helps businesses define what truly differentiates them in the market.
With well-structured problem definitions and solution strategies, Agentic AI becomes exponentially more useful—able to generate better code and adapt as business needs evolve. This is where working with Envorso can make the difference. We help teams learn how to communicate better and develop their internal vocabulary for their unique product requirements and designs. Enabling them to reduce redundant product development and costly product rework through better product definition and failure prevention techniques.
This paradigm shift will favor smaller, focused engineering teams—less burdened by scattered global coordination, yet more productive and cost-effective. The demand for real SE education will rise—both to produce new engineers and to upskill today’s developer workforce.
Far from a threat, this is an opportunity—a massive one.
The return of the software engineer isn’t fiction. It’s happening. AI will filter the galaxy of code writers, not by speed, but by understanding. Those who can define problems and engineer solutions—those who embrace the full discipline of SE—will lead the next age of innovation.
The Force is strong with those who engineer.
If you need to awaken the force in your Software Engineering community, or transform young padawans into Engineers, reach out to me at Envorso to begin the journey.
Written by P.S. Abowd.