3 ms·
I've long since moved on from that position, and that company, so no worries there. I'd be worried about this however: >> I am head of development in my compa
by YeGoblynQueenne 10y ago
I've long since moved on from that position, and that company, so no worries there.
I'd be worried about this however:
>> I am head of development in my company. I make standards and learn others WHY. They soon all become groopies
It's easy to get people to agree to everything you say if you're their boss. It's good to keep that in mind, always. For myself, I've had the best experiences and learned the most when I had senior devs who listened and were willing to mentor, rather than impose their will.
Of course, up to a certain extent, if you set up processes in a certain way and then hire people to execute them, and they agree to come onboard, there's no issue of forcing them to do as you say. If they don't like it, they can go somewhere else.
Still, I think the best lesson I got from that job where people didn't want to listen to the junior dev (me) is that you should always be open to advice from all levels in the company hierarchy.
- majkinetor 10y agoI work for government. You can't really impose anything on people in gov, three are no reprecussions for not listening to the boss. > You should always be open to advice from all levels in the company hierarchy. I agree 120%. I don't really care what's your position in the company. I am practical person - if you can prove me that I suck I will be happy to change. But I do need proof that new concept works in real world - so many things look good on the paper and you need to digest stuff fully. Currently, my best brainstorm partner can't be lower in the company, but he is driven by pure passion.