I think it is indeed a cultural change and you need all team members onboard. We've been fortunate to have started out as a relatively small team on the frontend and it's been working well having us all onboard.
I worked for a company a couple of years ago that tried to implement this and it didn't work because one guy set it up but didn't really get the rest of the team onboard with it so it ended up being quite messy and very quickly wasn't maintained.
I'd say the biggest downside is the architectural mindset that everyone needs to have to get the most out of it. A lot of people don't put effort into really digging into how it should work and then end up getting impatiently frustrated when they struggle to add the the existing architecture. At least that's what I experienced when first trying to embrace this. Once those hurdles are overcome then it becomes pretty smooth sailing!
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.
I think it is indeed a cultural change and you need all team members onboard. We've been fortunate to have started out as a relatively small team on the frontend and it's been working well having us all onboard.
I worked for a company a couple of years ago that tried to implement this and it didn't work because one guy set it up but didn't really get the rest of the team onboard with it so it ended up being quite messy and very quickly wasn't maintained.
I'd say the biggest downside is the architectural mindset that everyone needs to have to get the most out of it. A lot of people don't put effort into really digging into how it should work and then end up getting impatiently frustrated when they struggle to add the the existing architecture. At least that's what I experienced when first trying to embrace this. Once those hurdles are overcome then it becomes pretty smooth sailing!