Whether or not you agree with the basic premise of this article, I’m sure you’ll be able to agree that any software project of a reasonable size will have bugs. The way these bugs are dealt with can often become an obstacle to forming a healthy relationship with the customer, and can even impede the software development process itself. There’s many ways to approach this issue, and I’m going to start with a common one.
Digital service delivery
7 Reasons to Adopt #NoEstimates in Software Delivery
In this first of a pair of articles about software project estimations, I’ll be arguing in favour of foregoing estimations.
9 Benefits of Test Driven Development
Test Driven Development is the practice of writing a test for a piece of required functionality, before writing any implementation code. This test should fail when first run, and then, you write the code to get it to pass. It doesn’t have to be the most perfect code, just so long as the test passes. Once it does, you can then safely refactor your code.
Continuous Delivery: Organisational Challenges
Adopting continuous delivery for a single team is tough, adopting it across a whole organisation exponentially more so. It’s hard to catalogue all the issues a business may face during a transition, but in this post I’ll discuss the common pitfalls.
Continuous Delivery: Keeping Quality High
Practicing Continuous Delivery is worthless if it’s not to facilitate the delivery of high-quality code. In this article I am going to cover some techniques, tools and best practices we employ at Made Tech to keep our pipelines moving, and how you can compel developers to push quality code often by rewarding them for attention to detail, rather than punishing them for making mistakes.
4 Reasons Not To Adopt #NoEstimates In Software Delivery
The #noestimates movement is a subject that has generated a fair amount of controversy in the software development community since its inception, including within the team here at Made.
The Building Blocks of Reliable Software
When solving requirements for a system, you should extract specific roles out into service objects. The lazy path is to solve problems directly where you encounter them such as in the controller, model or view (given you are using MVC of course).
Continuous Delivery: Continuous Improvement
We’ve discussed what Continuous Delivery is, the benefits, how to prepare your team for it, the challenges you may face adopting it, the tools you can use, how to build your pipeline and what you can do to make sure quality remains high, but how do you stay on top of the advances in Continuous Delivery?
Continuous Delivery: Keeping A Clear Path To Production
Note: Article edited on the 4/12/2018
Continuous Delivery: Tools
Finding the right platform to form the basis of your Continuous Delivery is key, and you really need a solution that is going to fit into your existing way of working with minimal effort.