You're viewing a single thread.
Saw this when I was on reddit. People from all walks of life were commenting how this was relatable to their job/experiencs. Was pretty cool to see, you never think about some of their obscure jobs that are hella impactful
Actually, I sometimes wonder about it with my job.
I'm not doing the actual development. I get that's part of being a more senior engineer, but it makes me feel far less effective and skilled when all I do is communicate requirements, balance client needs vs business and infrastructure requirements, and review code and documents to ensure another team of engineers can support it.
But then, usually in some crisis scenario when shit is going down, the engineers responsible for the development become deer in the headlights. Instead of letting everyone panic, it's up to me to identify what broke (or what wasn't working to begin with) implement or communicate any workarounds, and get tickets/tests written up to be worked on/fixed and prioritized. It's those situations that remind me that a lot of our jobs aren't that flashy, but without them, nothing in the world would work.
I get that's part of being a more senior engineer, but it makes me feel far less effective and skilled when all I do is communicate requirements, balance client needs
Yeah. I'm 100% not a people person. I focus on one person - my client - and pretend they are a good friend with a great idea of a product regardless of how good it really is.
Everyone else I have to report to can just suck it. As long as the client is paying and happy and the devs are working and I understand the code & docs, then that's good enough for me.
If it prevents me from further promotions even better. If I get any further away from code I would cry.
Office Space was amazing watching once I'd been a developer for a while. I had so much sympathy for that dude, because it's definitely a real job and having someone bad at it definitely makes my job harder, but it definitely feels like a "do nothing" job.