Data wrangler, software engineer, systems programmer, cyclist. Unix (mostly Solaris) for aeons. I talk C, Python, SQL, Performance, Java, Kafka and Makefiles.
Location
Brisbane, Australia
Education
BA (Mathematics, Modern History), University of Queensland
My experience is that when you've got fewer than 10 people in the team, many of those roles can be combined - or even just shared around. Though I'd make sure that there's just one architect. If you've got a small team you have to work with and around each other, and I suggest that in that sort of environment everybody should be tasked with process as well as code.
That could get a little interesting if you have people of wildly differing skill levels, but the more senior members should be taking the lead on pulling the juniors up to their level. If you're in a team that small and the seniors aren't doing that, then they're not pulling their weight and you need to find a way to get them to do so.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My experience is that when you've got fewer than 10 people in the team, many of those roles can be combined - or even just shared around. Though I'd make sure that there's just one architect. If you've got a small team you have to work with and around each other, and I suggest that in that sort of environment everybody should be tasked with process as well as code.
That could get a little interesting if you have people of wildly differing skill levels, but the more senior members should be taking the lead on pulling the juniors up to their level. If you're in a team that small and the seniors aren't doing that, then they're not pulling their weight and you need to find a way to get them to do so.