Code coverage is the measure of the amount of code being executed by tests.
Are you leading teams and want to make sure they are productive?
Ah, holiday traditions. Christmas carols, Black Friday, Cyber Monday, fruit cake, egg nog, and change feeze.
I’ve been a software engineer for a while. When I had the opportunity several years ago to help uncover the core practices needed for continuous delivery, one of the things we needed to know was how to measure the outcomes.
Continuous delivery is a way of working to reduce cost and waste, not just build/deploy automation.
If you don’t follow Dave Farley, co-author of Continuous Delivery, you’re missing out.
I recently saw a documentary on the history of the Ford Edsel.
A frequent conversation I have is about branching patterns. Legacy development was all about long-lived branches to develop complete features followed by code freeze and merge hell.
In the lifecycle of most applications there comes a time when they will go into maintenance mode where changes become very infrequent.
“We want our teams to be more efficient and deliver higher quality!