@UxBjarne@SKrokfors Hyperspecialicering som leder till kunskapssilos, personberoenden och kasta över staketet beteende inte bra. Men specialisering som mentor och kunskapsbyggare bra.
@tottinge Our team/mob have 1-2 hours of "learning time" every day, inspired by @mob__mentality https://t.co/cUVYyZ9FKu. It is helpful to say the least and often feeds back into our work and process (the virtuous loop https://t.co/dBPAZDpE1f)
Ego Driven Development - I do whatever feels meaningful to me and give little thought to the impact on team throughout, team spirit or the cognitive load and stress level of my team mates
Recently performed a "hard team reset". Blank canvas, scrapped old habits, introduced #mobprogramming. Taking it from there. Feels good.
TBM 7/52: Making Room For New Things, by @johncutlefish https://t.co/zF3Y8wp4lJ
@SKrokfors@allenholub I think I lean towards some kind of week ownership model. E.g. If my team needs to make a change in some other teams domain we mob together. I like the idea of shared ownership but am concerned cognitive load would grow in order to make good decisions in many different domains.
@d_stepanovic I can see the point in their argument but believe that mobbing usually covers most perspectives and the benefits of mobbing far outweigh the benefits async and fresh perspective. In rare cases perhaps both async and sync should be combined to get the best of both worlds.
For each code change we should consider the cost of the change in comparison to the value of the change. The cost obviously includes the time it takes to produce the change but much more importantly it includes the cost of maintenance during the entire lifetime of the change. 1/6
Boring as it sounds, I think we need to be much more aware of the maintenance cost of code changes and avoid changes where the value vs cost comparison does not add up. 6/6
"they get together to divide the work up into individual pieces so they can avoid talking to each other while coding".
I'm more and more questioning why this is still the common way to do things in our profession.
@rmcomplexity When they get together to divide the work up into individual pieces so they can avoid talking to each other while coding, and then hope to integrate it some day in the future?
That's a kind of collaborating, but also just turn-taking with some overlap.