zlacker

[parent] [thread] 0 comments
1. wallac+(OP)[view] [source] 2022-01-29 21:45:47
regarding the apparently competing values of reliability and velocity, try propagating these goals through different mediums. code quality can absolutely be ingrained into the culture. things like TDD, when/what to integration test, and encouraging PR reviewers to enforce these requirements. you can literally just run an in-house course/training for everyone and the aggressively follow through.

once you’ve got reliability deep-seated in the culture, then you can talk about velocity all you want without worrying that your teams will make confused tradeoffs. in effect, you’ve communicated the nuanced concept that “we move fast, but always within the constraints that provide for a reliable product”. most people aren’t consciously thinking about it that way (not a bad thing), but their behavior matches what you were originally wanting to convey with a nuanced message.

[go to top]