tips for transition from lead developer to architech/tech lead

Question

I got out of college in 06 with Bachelors in CS and since then have been working as a Java Analyst. Last year I got into a project where I am the lead java developer. But somehow I do not feel confident about being a 'lead'. I believe I am just the lead because I maybe know a wee bit more than other 2 developers. I am trying to make the transition from lead/analyst to java architect. I felt completely lost when I searched for Java Architect interview questions. I know very vague answers to them as last time I really read about encapsulation was back in college.

What tips/career advice would you give someone like me? I am willing to spend same amount of time needed for a Masters into the journey to being an architect. What books/readings would you recommend? Will certifications make a difference? What type of effort is required?

Answer 1

You can train to be an architect or a lead developer and it is definitely going to help but it doesn't mean that it will make you an architect. You need to have a personality that helps you to lead a project / team. Having knowledge is very important. In our field you always have to learn and if you are leader you need to teach others.

1. You need to has a vision. Without a vision there's no direction you can lead your team.
2. You must be able to share your vision. Communication is the key. You should be able to convince the management and developers you lead in your vision.
3. You should be able to take charge.
4. You should be able to inspire through example.

I'm trying to make a point here that you can have all the knowledge and all the training in the world but if you don't have a personality of a leader it's going to be tough to lead a team.

Answer 2

The biggest gap I see between where you are and where you need to be is in experience, that is, time. (IMHO) you simply haven't been out of school practicing your craft for long enough to give you the experience and long-term vision needed to be an architect.

However, you can't simply wait for this time to pass. You must broaden your experience and repertoire with a number of different projects, [Ack, I'm starting to experience buzzword overload now..] and...

• you can read more books
• broaden your experience
• broaden your perspective
• become a better teacher

And, you may need to leave your company for another job. It can be hard gaining a good breadth of experience at just one job/company (instead of gaining 5 years of experience, you end up gaining 1 year of experience 5 times over).

Good luck!

Answer 3

Before you can really be a good architect, you should understand the various frameworks that are commonly used, such as Spring and Hibernate, and know what the limits are of Java and know when they should and should not be used.

The best way to do that is to get used to writing similar applications with various approaches, then critique them.

Or, try to just start designing a distributed system for yourself, such as a game that can be played on the desktop or a cellphone, to see what different platforms are like.

I think trying to become an architect is that you start to think like an architect, and in your mind become one, then, you will get the title, at some point.

Not everyone is cut out to be an architect. What Vadim said is very true, though you seemed to put it down. An architect must be able to not only see the application in his head, and understand how it works, but then to communicate that to others, and then to be able to jump in and help out when a developer gets stuck, so the work can continue, and no one is spinning his wheels long.

You should also learn to listen to what people are saying, rather than just putting them down, as, when you talk to stake holders, or to the business side, you will interact with people that are not technical, but will have advice or suggestions that should be evaluated, and if you get a reputation as not being a good listener, then they will stop talking with you and your effectiveness goes downhill.