Much like the well-known technical debt, I would argue that this kind of impact on the long-term delivery and DevOps capabilities is often underestimated if not totally ignored. It is, however, a debt: interests will be paid.
In @TeamTopologies, each team works on its domain and its code. This helps manage their cognitive load.
Unfortunately, business does not always need changes in all the domains with the same priority.
In addition to that, when a team owns a service but has to accept contributions from many other teams, they might not feel responsible for the resulting software. Especially when the "guest" code starts creating issues in production…
Wanna try code smell panini? Check it out in part 2 of the notes on the technical agile practices training we organized at Worldline.
https://t.co/ylUF4uCOpw
Here are some notes on a technical training experiment we did at my client Worldline.
It was inspired by techniques from @LlewellynFalco and @emilybache, so if you like it, check their stuff out. ;-)
https://t.co/La8iA1aLEr
Hi @mobtime_app ! (great app by the way ;-) ) Is there any way to save the participants and settings for next time or do I have to enter everything each time?
Can't wait for next week's @ddd_eu workshop on "TDD for real-world applications!"! It's going to be awesome! :-)
https://t.co/lL0nvKqw8M
Dry-run is already tomorrow!
Now I know how to refactor legacy code without tests! :) Thanks @LlewellynFalco and @jaybazuzi for this awesome "Refactoring to Cleaner Code" workshop! I learned new things there.