Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
onboarding. communications. work on the learn/productive curve.
also - listen to the new devs, and don't pull the "I know better, shutup" shit. -
Growing too quickly cann lead to collapse, thus it's essential to get processes and documentation ahead of growth.
-
asgs112863yAdd a few more senior Devs/Leads to spread the load. Otherwise,
You will be pestered with
1. more questions and issues
2. More meetings
3. More Jira tracking and maintenance
4. More planning, arguments, frustrations in general
Basically, it should be a controlled meaningful proportional growth -
JsonBoa29883yFor byte's sake, listen to @PonySlaystation . document and clarify your processes or soon enough the word "clusterfuck" will be an understatement.
-
@JsonBoa I'm no expert though...
I witnessed a partner company go bankrupt due to tripling their size within some 14 months. But COVID might have played a role in it as well. -
Reading books about scaling teams and business is a good strategy. Unfortunately I have no recommendations on this topic but someone else might?
-
Like others have said, documentation for process in place now, _and_ make sure all new devs have access to it day one.
Also, I would add to make sure the documentation includes all setup needed to get your solutions running locally on a bare bones dev machine. -
It is a good idea to ask everyone about their previous scaling experiences, good and bad, from previous jobs. If they come up with potential issues ask the team how they could be mitigated. People use to engage more in what they have contributed for.
What are some strategies to grow when your team size is increasing? My team will be doubling in 6 months. All devs.
rant