11 May 2013

being successful developer at new job

What combo makes a successful developer

In IT or Information Technology industry people will be changing their jobs. This could be an internal job in the same company or when you join another company as a lateral hire. Myself being a developer, let’s talk on how to become successful at a new job when you joined as developer role.

Priority items to pursue by any professional at new job to become successful :

  • Right skill for the new job.
  • Understand the project in depth at the new job.
  • Attitude matters at a new job most. Maintain good professional relationship with juniors, peers and managers alike.

Let's see in detail what it meant for developer to succeed at new job.

Filling the skill set gap for the new job:

when joined a new job or role and started working on the new project, it's always important to acquire the skill set what you’re new job requires. For example, you would have worked on .NET framework version 2.0, but the new project is being on the latest .NET framework.

another example could be when you don't have any experience in the database tier. You need to quickly learn the bare minimum database skills required for the new project you work on working on the new project.

without the right skills for the new job, it will be very difficult for effective participation in design discussion and to contribute significantly to the implementation.

So quickly fill the gap in your skill set and start contributing to come become successful developer at the new job.

Understanding the project in depth at the new job:

However technically good we are, what also equally a matter is, how much knowledge we got on the project itself. Developer at the new job should understand quickly the overall architecture and structure of the project at least in high level. Try to understand below on the new project:

  1. The structure of the .NET projects and solutions involved in the systems and the dependency involved between them.
  2. What are the different systems involved in the system? How does the data flow happen between the systems involved?
  3. What is the deployment architecture and how does each component in the system get deployed?
  4. Understand the relationship between the data involved in the system. Try looking at your database schema diagrams.

Attitude matters a lot:

We should behave professionally at the working place. Below points helps:

  1. Don't let your emotions flow freely when you are at a new job. At a new job, you have not yet understood people around. So they might misunderstand your emotions.
  2. Don't try to take control of the things in a hurry. Have patience. Respect your juniors.
  3. First impression is best impression. If you get a chance to speak in front of people in the whole project, don't miss the chance. Share your opinion and thank the people who are helping you to understand the project better.

No comments:

Post a Comment