Skip to main content

Some small observations about working in a team

As we approach the first official delivery of the automated laboratory system on which I have been working on for the past couple of years with my colleagues I realized some important conclusions about working in a team.

I realized now that all of us from my team have kind of grown together over the past couple of years. All those challenging situations, funny moments and hard work have brought us together without us even knowing. When I first started in this team, we were all quite different and initially kind of cold to each other. Especially my boss but I think that is expected since he is in a delicate position and so I understand him.

But as we worked more and more together, we kind of slowly started opening up. I realized then that it's not enough just to be colleagues in order for a team to work. You actually need to see everyone as a bit of a friend. Why you ask me? Because only then you will feel free to collaborate with other people to work together on something. I noticed that when there were 2 codependent tasks and you gave them to people that weren't that close, a lot of miscommunication happened which caused those 2 tasks not to meet the requirements. And it's pretty simple, those 2 persons didn't see themselves as friends and were reluctant to communicate to each other the issues that arouse. In the end, each person fixed the issues that arouse in their own way and imagined that the other person came up with the same idea. So the feature which they worked on, didn't work at all as expected and another task had to be made to resolve the conflicting solutions to issues between the previous 2 tasks.

And I noticed that there is a lot more to a team than meets the eye. You might think that if all the team members are on the same page and come up with the same ideas then that's a good thing. Well, it's kind of wrong. If everyone on a team has the same ideas then there are fewer overall ideas in the team. In the complex world of software development you need as many ideas as possible because of the wide range of problems that we have to solve. So in a team you should have as many people with different ideas as you can. But the problem is that 2 people with very different ideas will find it harder to communicate to one another because they aren't exactly on the same page. If their ideas are so different they will spend more time explaining their ideas to each other. Ideally there should always be some sort of friction in a team in order to produce good ideas. You should have enough diversity in a team while retaining good communication between members.

In time a team tends to become more homogenous. This means that communication between members improves but the number of ideas dwindle. I think this is why in big companies with many teams it is actually encouraged to swap members between teams.

Comments

Popular posts from this blog

Some software development common sense ideas

 I haven't really written here in a long time so it's time to write some new things. These are just some random common sense things that seemed to short to write about individually but seem really interesting and useful to me or other people 1. There is nothing fixed in software development, all things vary by circumstances and time Remember the documentation that didn't seem that important when you started the project, well after a couple of years one the application has grown and become really complicated, no one actually knows everything about the application anymore. So now you really need that documentation. What happens if you suddenly need much more people to develop the application because of some explosive growth? Without documentation, new developers will just look at the application like they look at a painting. This actually happened to me. Maybe in the beginning of a project, a technology really helped you a lot but as the project grew, it started making things...

Some real soft skills which are useful as a developer

I keep hearing more and more that as a software developer you still need soft skills, that soft skills are more important than technical skills and so on. But no one really has any concrete ideas about what these soft skills actually mean as a developer. Everyone just keeps talking about them but I don't see anyone actually going into details about them with concrete examples. Not to mention that a lot of people are just trying to make money out of these things and when they say that soft skills are important it is usually followed by some self advertising about their soft skills trainings. And to make matters worse, some of these preachers, pardon people, don't have a lot of experience in the development field. Some of them are not that good developers and then they say, that not only technical skills matter but also soft skills. Maybe they are not so great developers because they also don't have good enough soft skills also. Now on to the concrete part of soft skills....

My thoughts as an experienced developer in this field.

To be honest, I would have never guessed that      I would end up saying these these things, especially jn the beginning of my career. As you become more experienced, you kind of get to see everything and you become less impressed by new things. Honestly there is some sort of repetitiveness in this field and we kind of like to reinvent the wheel quite often, because well, we become a bit too easily bored. Take for example how the web looks now, a lot of it has been borrowed from other places, mostly desktop development, especially the parts about making custom reusable components.  Or from older frameworks, like state management in the UI which actually was first properly implemented in Asp .Net Webforms, as far as I know, something like 20 years ago, where you used to have the dreaded view state.  But most likely something similar existed before that too. I was not that surprised when React adopted initially this idea. Or even less surprised when hooks where in...