It's my first month at Netguru and this post is an outline of the first impression I had when I started working here. I'll try to focus on the most important aspect which is, I think, teamwork.
It's my first month at Netguru and this post is an outline of the first impression I had when I started working here. I imagine this is something that might concern a lot of newbies so that's why I decided to jot down a few thoughts about this time. I'll try to focus on the most important aspect which is, I think, teamwork.
For me, the first month was really challenging. That's mostly because of the fact that I had never worked in a software company before. I used to learn everything on my own - reading, coding and Googling. I have to admit that coming up with solutions and tackling problems by myself did give me a lot of satisfaction, but there are two sides to every coin, right? And then, when the team arrived... boom! There was a world of difference! I might compare it to being the last soldier on the battlefield who then sees the reinforcements riding in on the horizon. What a relief! You're not alone anymore and your problems and concerns are not just yours!
Teamwork. That's what makes this job really fun. Instead of spending days thinking up a solution for some kind of a problem, you can just ask your team - maybe they'll bring something fresh to the table. No need to explain why that's great, I suppose. There are obviously a hundred ways of doing something and sometimes it’s really hard to pin down the best solution. That’s why you shouldn’t be scared of feedback from your team. They are here to help, not to point the finger! Teamwork makes you much more efficient and, probably most importantly - you learn way faster than when solving problems on your own. That can translate, for example, into 10 minutes instead of two days!
Let's assume that you're working on something that you're completely unfamiliar with. You can never be 100% sure that you’re on the right track. Teammates can put you back on course during pairing sessions or with just a quick video call. Moreover, coding on your own doesn’t guarantee that you’ll end up with the ultimate solution. In a team, however, your mates can always review your work and, if need be, suggest what might be improved or tweaked.
You can’t really talk about teamwork without saying a bit more about code review. Before any commits go further, someone from your project team (or from another project) will review your code and check it for mistakes or suggest a better way. You don't have to be afraid of breaking anything. Every single line you write gets examined and, wherever there’s room for improvement, you'll get feedback as soon as possible. Isn't that great? There's one more thing that comes to mind when mentioning feedback - as we say, "you are not your code"! That’s one of our mottos.
So, all in all, teamwork is a fast-track towards improved performance and rapid personal development. Don’t underestimate it! You’ll make a quick transition from a newbie to a much more experienced coder. Finally, remember - sharing knowledge is the key to evolution!
If you want to know more about how we share our knowledge internally or if you are, perhaps, just looking at how to introduce it in your company - check this post written by Joanna.