Shifting left? Learn more about what this means and how to start in the #continuousdelivery podcast! Featuring Zarar Siddiqi, Csaba Bereczki and Gino Marckx
Watch video at https://t.co/oVwxoxB4OR
Or find the audio only version at https://t.co/Oo45SNAQwE
WTF! Why Transformations Fail, liquid death and more. Check out the next episode of the continuous delivery podcast on YouTube (https://t.co/kCznpJYIbF) or elsewhere (https://t.co/B5tYiKenXj)
#podcast#continuousdelivery#agile#transformations#wtf
Starting off the New Year with a discussion on microservices versus modules, moving on to some other topics including the necessary architectures required for continuous delivery.
https://t.co/GNbRWew1Kt
#continuousdelivery#microservices#softwarearchitecture#agile#podcast
How do you hire talent for Continuous Delivery? We talk tactics and principles at play when building your team, including interview techniques.
https://t.co/l7yQxDsCuD
Apple: https://t.co/fVdoxW0pSW
Spotify: https://t.co/nfqaynWIfL
#continuousdelivery#agile#hiring
Regression testing sounds like a good idea, when in reality it is a speed-killing anti-pattern. We discuss alternatives.
https://t.co/17QXFBDDQF
https://t.co/5oXyu7wGMg
#agile#continuousdelivery#regressiontesting#testing
Backlog refinement is an activity used by teams to look ahead to future work. This is a noble idea but can lead to significant amounts of waste if a team isn't careful.
Ep 74. Perils of backlog refinement
https://t.co/7vLLeE0Llr
#agile#continuousdelivery#refinement#podcast
Making a simple/obvious plan is 10x harder than the complex, convoluted, full of caveats one that hedges bets & shies away from making hard choices on priority & trade offs. Annoying side effect is that it also looks like it didn’t take as much work as the complicated one
Insights are only meaningful when they are based on accurate data. How can we help the team measure what they care to improve?
Ep 73. Metrics the team cares about
https://t.co/zMj57ohHpT
#agile#continuousdelivery#podcast#metrics
Bureaucracy doesn't appear overnight, it creeps in. What can we do prevent bureaucratic waste?
Ep. 72: Minimum Viable Bureaucracy
https://t.co/nRaicddQg4
#agile#podcast#continuousdelivery
@davefarley77 The main argument for PRs that I've heard is that people learn in different ways and methods, and assuming that pair programming is the best one isn't always accurate. There's something to be said about asynchronous learning. I agree, though, the WIP and delays PRs introduce = 👎
@toshieuya@davefarley77 I agree that it can add complexity, but I also find if I’m adding complexity by adding a feature flag, then that is feedback on my (poor) design.
In my experience, the complexity comes from leaving the flags in there when you don’t need them anymore. Got to take them out.
@davefarley77@GnafGnaf Yes, I find this to be true. For people with auto updates turned off it gets annoying.
I’ve also put a lot of the UI in WebView in a separate repo than the app, so you can always push to that without bothering the AppStore Gods.
@HernanWilkinson@davefarley77 Introducing more complexity into the merging process seems like a step backwards. The first thing to do when implementing a new feature is to create a feature toggle which turns the feature off and then commit your feature code behind it.
@allenholub You can layer in security step by step and organize those steps into small little tasks. I don’t know if I’d call it a “story” but breaking it up seems like a good idea.