4 ms·
I can resonate with the author, giving the context working on Scaleups and Big companies, where the coordination and communication plays a very heavy toil on th
by braza 3y ago
I can resonate with the author, giving the context working on Scaleups and Big companies, where the coordination and communication plays a very heavy toil on the actual work.
I do not believe in this model of “big collaboration” with folks swarming around a problem and each one with partial context trying to fix something that structurally has a huge communication, coordination and technical coupling.
The best work experiences that I had was in teams that we establish the APIs, S3 buckets where the processed batch files will stay an maybe a e-mail list where someone will reply if something change.
- blastro 3y agoFirst two sentences describe my current situation. How to improve it?
- braza 3y agoI do not have a straight answer, but one thing that I saw working is the concept of “Good fences” where folks still act as a team but has clear touch points related with problems and when things goes south everyone knows what to do.
- blastro 3y agoThanks for your input!
- platformeng 3y agoNot saying these will solve your problems, but it may help give it a little perspective at least: https://www.opslevel.com/resources/optimizing-engineering-communication-for-better-developer-experience https://www.opslevel.com/resources/optimizing-engineering-co... https://fernandovillalba.substack.com/p/improving-engineering-communication https://fernandovillalba.substack.com/p/improving-engineerin...
- blastro 3y agoThank you for this