How to lead projects as a software engineer
read.highgrowthengineer.com
read.highgrowthengineer.com
> They know how to bring people together and deliver value.
I agree it's not JUST coding, but the rest of the article illustrates why people debate the title of "engineer" in software engineering.
Scheduling meetings, creating communication channels, doing the planning, meeting with people... this is NOT engineering! None of this is taught in Comp Sci degrees! The insistence on calling this engineering is a big factor why so much software is garbage, breaks easily, and takes a long time to make.
This is also a sign that the org 1) does not actually need engineers, and/or 2) does not appreciate engineering. If coding is so easy that you can do all of that other stuff, then presumably you are just implementing 3rd party solutions and glueing things together, instead of actually building a software engine.
I think we need to just call this type of role Technical Product Owner.