|
|
|
|
|
|
by Fredej
1786 days ago
|
|
|
In many, many ways. Relationships to your fellow engineers help when you're banging out code and need a review or just a rubber duck session. Relationships to the Product Management team means you have a finger on the pulse in terms of where the product you're building is moving. That means you can push back on stupid things, and suggest brilliant things that were only possible because you had the technical insight. Relationships to upper management helps if you have some technical idea that you want to pursue which requires a significant investment. Basically, relationships help a ton if you want to have any influence on the work you're doing. If you're fine just taking whichever ticket pops up and implementing it then sure, you don't need relationships. I think this however also heavily depends on the company and culture you're in. |
|
|
I do command quite some deciding power. But I can’t figure out if it’s my technical skills, or the fact that I’m the only person carrying this project. Pretty sure no one else around me knows what a ticket is.
But what irks me is that my entire position feels incredibly ill-conceived. Like I’m not solving any actual problems. And I can’t “do” anything about it, because that would take years of company-wide restructuring. And I’m just not a long-term visionary, like my peers (who all happen to be, let’s say, at a much later physical and mental state in life).
That’s why I don’t see how in-company relationships benefit me. I wouldn’t dismiss them in general though, which I strongly came off as doing.
But it’s either that, or quitting. The latter will probably happen in the foreseeable future, once it doesn’t look too transient on my resume.