|
|
|
|
|
by Karrot_Kream
1294 days ago
|
|
Yeah I've worked in infrastructure through most of my career wherever such a distinction is available (or when it opens up), and this is a common complaint. Product folks get the most visibility and get kudos and parties for product launches. Meanwhile, the deployment infrastructure staying up is just expected, even though the engineers responsible for it are working hard to keep it up. It affects team morale (infrastructure teams are unrecognized for their hard work) and also has material affects on promotions and compensation as it's harder to justify business impact on these teams. I know folks that left infrastructure teams because of this dynamic. |
|
told them flat out that they are most likely going out of business, but I’ll get it a try.
Couple of times owner tried to Ask me when feature X would be delivered. Just told them no. Managers were wise enough to understand they were one pissed tech guy from failure.
3 years of endless late nights to get company back to a good spot with a rebuilt time, new infrastructure. Proper documentation, the works.
Finally left after being passed over for promotion to a guy that did nothing, but promised the world. (He never delivered)
Took me a couple years to recover from that job.
I don’t work late nights anymore. If company doesn’t care to invest in infra, I look elsewhere.