Why Engineering Managers Still Want to Write Code
The article explores why engineering managers often feel compelled to keep coding, discussing the motivational pull of programming, the challenges of slower feedback loops in management, future career considerations, and how acknowledging these feelings can help balance technical passion with leadership responsibilities.
One of the biggest challenges for engineers transitioning to management is realizing that producing code is no longer their primary goal, yet the question of whether managers should continue coding remains a frequent topic of discussion.
Programming Can Keep You Motivated
Most engineering managers start as software engineers; after years of hands‑on development, they often retain a strong passion for coding. However, moving into leadership can diminish the direct satisfaction of building and seeing one’s own code in action, leading to a sense of loss when they no longer write code daily.
While a manager’s success is measured by delivering valuable features and helping engineers grow, the personal pride of saying “I built this” is hard to replace.
Additionally, managerial duties such as handling personnel issues can be draining for those who prefer technical work over people management.
Slower Feedback Loops
Software engineers typically enjoy short feedback cycles—writing a test, seeing it fail, fixing code, and watching the test pass—all within minutes.
With CI/CD pipelines, code can reach production in hours, providing rapid gratification.
In contrast, engineering managers experience much longer feedback loops: building a career‑development framework, seeing a team member get promoted, or implementing new engineering practices can take weeks, months, or even years.
Managers must continuously invest effort over long periods before tangible results become visible.
Future Career Prospects
New managers or those uncertain about long‑term direction may wonder whether to keep coding, as it can affect future career options.
Some managers return to individual contributor roles, a phenomenon described as “swinging between manager and engineer.”
Even after months without coding, engineers may fear they have lost technical proficiency, though in reality the knowledge remains, albeit a bit rusty.
Understanding and Accepting These Feelings
If you are hesitant about continuing to code, reflect on why you enjoy coding in the first place.
If your true passion lies in engineering rather than managing, consider how to stay engaged as an engineer.
As a manager, your primary responsibility is to support your team and help them reach their full potential; recognizing when you are not suited for this role is also important.
Many managers love their position and find joy in seeing their teams thrive; if you do not, that is acceptable, provided you acknowledge it and act responsibly.
Original source: Why Engineering Managers Still Want to Write Code
Laravel Tech Community
Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.