Hey everyone,
I just wanted to write up a post for those of you who haven’t worked in a team before, specifically in the software development field.
I was a freelancer and a lone-wolf who used to work remotely once before, and I totally understand how it is like. I remembered when I tried taking a software job and worked with others for the first time, I was afraid of criticism. Because of this, I was doing things wrong at the time.
I rethought to myself that there is no need to be afraid of criticism. It’s actually good since it’ll enable yourself to be open to learning new things. To keep learning is a key to becoming successful. This is what all teams do. Here are a couple of scenarios:
1. There is a requirement to be made on a specific functionality. Somebody had already done it on iOS, and the same will have to be done on Android. Because it was already done on iOS, it just means that Android will need to be implemented. Therefore, the Android developer will code the solution in order to make it work. Once it works, he’ll push it to production.
2. There is a requirement to be made on a specific functionality. Somebody had already done it on iOS, and the same will have to be done on Android. Because it was already done on iOS, the Android developer looks at the existing code and will try to find a better way to resolve this issue, so that it works flawlessly on both the platforms since they use the same backend. Once said developer architects the new solution out, the developer will communicate with his team in order to implement the needs of the functionality. Doing this, the code will be clearer and more concise, meaning the iOS code will then have to be refactored towards how it should be done.
Clearly, if we are talking just about team effort, then scenario 2 will be better. Spring cleaning is involved, which also means that the bugs will be less as well.
Even if the developer will not understand something, then said developer will ask another developer how something works or should work. If it’s a new implementation, then usually everything starts with a skeleton and a little piece of meat to make something functional. In here, there might be crashes along the way, so developers collaborate in making the functionality flawless.
Oh, and if you still feel like the lone wolf, just start off by being friendly. Eventually, you’ll get used to the environment and mesh along. Then that next job will become a lot easier as well (if it needs to go to that point)!
Until next time!
Brian.