The agile manifesto says:
"We are uncovering better ways of developing software by doing it and helping others do it."
NOT
"We know the one true way to manage the software lifecycle. We don't actually write software, but we can certify you."
#agile
One of the hallmarks of good agile development, perhaps the thing that separates it from poor agile attempts, is the attention to design.
A good agile team will design continuously and refactor to the new designs. A poor team will just bolt on new stuff blindly.
Are you confusing 'refactoring' with 'rewriting'? Stop! Refactoring is about changing the structure without altering behavior. A simple name change can be a refactoring step; rewriting the whole module is not. #Refactoring#SoftwareEngineering#ContinuousImprovement
@HansDeLeenheer @tdpauw PRs, statistically, increase risk, assuming that they are less frequent than daily and according to the data from State of DevOps reports. So if the engineer deems the risk to be high, they should avoid them.
@jasongorman Oh yes. And IntelliJ IDEA doesn’t support it for Kotlin. I had to find a workaround which takes a couple of additional steps, one of which is manual.
"It's hard to predict what this dice will roll."
"Well, then, you need to get better at predicting."
Conventional wisdom about software development processes - that unpredictable work needs better estimates, not a more predictable way of working.
@IgorskiCo@davefarley77@KentBeck CD is literally principle 1. “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
I confess that I am not a big fan of "The Test Pyramid" so here's a #Thread on what I think is a better focus for your automated testing strategy...
1/14