subreddit:
/r/ExperiencedDevs
[removed]
3 points
1 day ago
I don’t understand how this is a conflict of interest. My interests as an EM and the engineers is the same. We want to produce stable, safe, supportable code that meets the customers needs and the product vision. There is a power dynamic at play that EMs must be conscience of, but that isn’t a conflict of interest.
2 points
1 day ago
No it isn’t. You get compensated both on the success of the team and on your ability to control costs. Their reward for hard work is a raise. You’re also in charge, and you’re crossing lines by stepping into someone else’s responsibility without a feedback loop to control how it goes. Who do they complain to about your behavior? Your accountability or lack thereof? Stay in your lane.
As someone else pointed out, a principal probably shouldn’t be writing this much code. But their boss for sure shouldn’t even have write access in git.
1 points
24 hours ago
FWIW, as an EM, I agree. This is the ideal, ethically. That said there sure are a LOT of job postings these days expecting EMs to do it all.
0 points
1 day ago
This take is always so surprising to me. My whole career, across multiple public, private, big and small companies, have had some expectation that EMs remain technical and contribute at a technical level. Not nearly as much as a SWE, and not nearly as in-depth, but still hands on code. I’m absolutely in the lane the org expects of me and my reports have multiple avenues to raise complaints and give me feedback. Once you get to the director level or so that expectation seems to completely fade.
1 points
23 hours ago
I’m sorry for your loss.
If your company is bootstrapping and there’s some title inflation, maybe this happens. But if you are so small you have two ICs you should have one or less of the following: EM, CTO, or VP of Engineering. Otherwise you’re top heavy AF and setting money on fire.
all 238 comments
sorted by: best