| Well fair enough. I don't consider myself better then my team when taken as a whole, however I am the lead for a reason and I'm much closer aligned on how to maximise what we're delivering to the client as I have to actually deal with them. The reasons why I sometimes have to pick a worse solution to a problem are obvious to me but not always to my team, but that's the way it goes and I'm the boss. An example? Once we had a requirement to have a user store for some group of apps and we came up with a really nice ldap solution, and two members of the team were really invested in the solution and the debates were endless on some technical details of the implementation. It was beautiful, as these things go. Then I find out that there's an existing AD environment we can just hook up to instead of reimplementing functionality that already exists so I shitcan the project. Does that make me arrogant or good at my job? My job is to help my clients, spending a few months implementing something that already exists just because some of my tech staff prefer our solution is not helping my client, yet these two members refused to implement the Code to interface the existing environment. Disagreements happen, but refusing to do work you disagree with when you're a contracted professional is unacceptable. As for my tech credentials, yeah I did a bit of ia32 back in the days where one might want to use 16 bit registers to avoid nulls if you get what I mean, wink wink, but never for profit. C? Yes, I was a c developer and I maintained boost on Solaris for a few years while maintaining as much ingnorance of c++ as possible and not really understanding any of it (mostly a packaging gig). Today, we are further up the stack but I don't think it has much relevance. I don't make unpopular decisions because I don't understand what the consequences are which seems to be your take; I just pick the battles we should be fighting for our clients and my comment was that I have little time for people who can't put the client ahead of what they want to work on. You are hired for your technical ability but that's to further the goals of your client. You aren't working on your side project and refusing to work on things, even those we all don't want to be doing but which further our clients goals is unprofessional and I have no problem saying goodbye to those who do. Its good to be strongly opinionated. Discussion is great. Multiple solutions and experimenting are good. Your design doesn't happen for some reason (and like above, it might not be because it's not the best solution) that doesn't mean you don't look like a spoiled child refusing to do what you're getting £1000/day to do, and unfortunately this attitude is more prevalent than you'd think. |