The key word here is Lead. As in: lead by example. Be able and willing to jump in at any place of the stack, even if it’s not Java. I hate to say it (to a tech lead) but JavaScript has gotten as advanced and as complicated as Java has in the past few years. Evolve or get eaten. Be able and willing to back up all the impromptu design and architecture questions with the demonstration of getting things done - or making progress learning the other parts of the stack that are not Java but are the bulk of the story workload right now. If you just aggressively ask the ‘front end’ devs on your team whats taking so long and why things are so complicate. Be prepared to either jump in and help when the ‘backend’ Java work runs out or to called out in public on your contributions to the team since you “don’t’ (or cant?) do php or JavaScript.” Ok, end of rant. But seriously, if you lead any team, not just a tech team and you sit on the wagon everyone is pulling asking why things take so long and how difficult can it be, expect some members of your team to lose all respect for you and question both your ability to lead and your relevance as a ‘Senior’ Dev who only does Java. If you lead my team and I see you doing anything and everything to make our project succeed I will gladly give 110% to the team. If you sit behind the wagon we are pulling, well, I will put that extra 10% into looking for other opportunities.
9/14/2013 ~ 2 min read
