AG International Consulting

Career progress as a personal growth

In this article, you will learn about the programmer, Aaron Vegh's career experience, which has changed his life completely. He has received significant and interesting challenges on the way to success.

I’m a software developer and I want to tell you about my life experience. Three years ago I joined the team in big media company. My clients were mainly single person, so the communication with them, explaining the product and convincing was much simpler. My first greatest fear is connected the first year of working with the team. It's a feeling when you do not feel good enough. This feeling never leaves. Over the years that I have changed in my thinking is to understand that so many people think that, people do not feel sufficiently in the team and you will always feel that way. I got the important and interesting experience when I worked in the team, which I would like to share with you. First of all, we should note that the work that we do is difficult and requires great effort. Empathy is the best way to deal with chaos.  Everyone should realize that no one is perfect in team and the error may be made during the code creation. In a way, it means that we can use humor to transmute Imposter Syndrome into a healthy respect for the work that we do. I learned that I do not need to impress the team members. I do not work only for myself and my future self but for my future team and future  developers who have not been hired yet. I worked on code with headers containing the names of coders who’d left the company a year ago or longer. And now that I’ve been gone for over a year, it puts a smile on my face to think that a file like AssociatedValues.swift, with the header “Created by Aaron Vegh on 2016–02–19,” may still be used today. I want to write my code to be clean and simple so that others can keep it and work with it. I also learned that when company hiring a developer, technical skills and professional standards are very important. During the formation of the code, I concentrated on many details. On a team, with an app that will be used by millions of people, a feature has to be done right. The code has to be clean. A bug must be fixed conclusively. Hacks, kludges, and bad code smells are unacceptable.

Finally, I learned the importance of attitudes. I'm not Tony Stark, but I've realized the importance of trust. The most important thing is to get a job that other developers do not want. Over time, the process of respecting the work, writing clean code, insisting on professional standards, and having the right attitude helped me climb over that bulwark of Imposter Syndrome. It makes sense: the more success I have, the harder it is convince myself that I can’t do the job. That’s not to say the feeling is gone: there are still times where I vacillate between feeling utterly masterful and completely inadequate, even on the same day. The consistent demonstration of skills strengthens the team. The team-created application is much better than the app that I would do alone, but the Iron Man is wonderful for one man to cope. However, team work is very effective and productive to solve many problems.