4 ms·

> Getting anything done in an organization means building the right relationships first. Building the right relationships is the difference between being able t

by hnick 7y ago

> Getting anything done in an organization means building the right relationships first. Building the right relationships is the difference between being able to ask the infrastructure guys to create some VMs for you in Slack, they do it immediately and then ask you to fill out a ticket and having to fill out the ticket and wait for two weeks. Funny, they keep rolling out more 'advanced' helpdesk software where I work to avoid building social connections. In the old days I got to know people, now there's no chance of that. There isn't even a name on the emails. I think in the long run this really hurts the company. It also makes it much easier to be upset at the 'stupid help desk people' rather than individuals you know might just be having a bad day.

scarface74 7y ago
I actually left my last company partially for that reason. I was the dev lead, responsible for getting a green field project out and the company I was working for merged with another company and they instituted so many processes around the IT processes I couldn’t get anything done. We also migrated to AWS and they treated AWS like an expensive colo. Every thing had to be approved, we could only get VMs and no access to any other functionality and I couldn’t even get a separate dev account, isolated from production so we could experiment and work. As soon as I got phase 1 completed of the project, I found another job as “just” a senior software engineer and the day I came in, immediately got full access to everything and admin credentials to our AWS accounts. Before the IT gatekeepers respond about how crazy it is to give software engineers unfettered access to the production infrastructure, I was brought in partially for my AWS architectural experience (adult supervision), I negotiated not to be a team lead and I switch back and forth between development and cloud infrastructure depending on the day of the week.

by hnick 7y ago

scarface74 7y ago

I actually left my last company partially for that reason. I was the dev lead, responsible for getting a green field project out and the company I was working for merged with another company and they instituted so many processes around the IT processes I couldn’t get anything done. We also migrated to AWS and they treated AWS like an expensive colo. Every thing had to be approved, we could only get VMs and no access to any other functionality and I couldn’t even get a separate dev account, isolated from production so we could experiment and work. As soon as I got phase 1 completed of the project, I found another job as “just” a senior software engineer and the day I came in, immediately got full access to everything and admin credentials to our AWS accounts. Before the IT gatekeepers respond about how crazy it is to give software engineers unfettered access to the production infrastructure, I was brought in partially for my AWS architectural experience (adult supervision), I negotiated not to be a team lead and I switch back and forth between development and cloud infrastructure depending on the day of the week.