@alexbunardzic I watch somewhere (youtube maybe) a TV series works this way too. One team works on one story line and another team on another story line. At the end the viewer will get one season.
Not sure if this analogy corrects or better.
@GergelyOrosz Been there, done that. The only lesson I can share is: never eat the cake from the middle, cut from side by side; probably like eating an apple.
Di masa-masa winter ini, sayang-sayangilah tim infra/devops/apalahnamanya kalian.
Mereka ini yg langsung berhadapan dengan billing dan cost software yang kalian deploy.
Kapan terakhir kali kalian ajak mereka standup atau minimal meeting buat nentuin tech stack kalian?
Irjen Teddy Minahasa Putra memerintahkan Kapolres Bukit Tinggi Dody Prawiranegara untuk menyisihkan 5 kilo sabu-sabu total 41 kilo hasil tangkapan. Teddy beralasan 5 kilo sabu-sabu itu untuk bonus para anggota polisi di bawah kepemimpinan Teddy. https://t.co/c6VcNSMb8t
That's a good point and the reason I included "Make an effort to understand legacy code" in "3 underrated things great developers do" https://t.co/qfpFPyEMdN
In about 15 minutes we're going to talk about "standups," "daily scrums," ticket numbers, rule-following, vocabulary transformations, and teamwork.
Probably.
Likely.
Or something like that.
New year, same day, same time.
Our Twitter Space is back! This friday join in on our open discussion around an awesome blog from @tottinge; The Daily Meeting.
Set a reminder for 2pm CT this friday. ๐
https://t.co/pKoFTpX0sI
#meetings#twitterspace#colaboration
Seriously, you have no idea how must waste, blockage, delay, communication failure, risk, and interpersonal conflict is CAUSED by working solo on separate partial, dependent tasks.
If you start to see it, it will break your heart. It is so much unnecessary work and trouble.