At Made we host regular client showcases, this is an opportunity to sit down with the client to discuss how the iteration and the project as a whole are progressing.
As developers we always appreciate a second pair of eyes and an extra brain. The eyes are really helpful for catching that extra whitespace you might have missed. The additional brain power might help you solve a problem in your code with 5 fewer lines. All of this results in better code and more collaboration.
Note: Article edited on the 4/12/2018
As an industry of tinkerers, optimisers and perfectionists we occasionally miss the beauty of unorganisation and human instinct. Our obsession to be more efficient and productive can sometimes have some undesired consequences. At Made we often adapt our processes in the name of efficiency but lately we’ve started experimenting by taking away some of these processes with surprising results.
Over the past year I’ve worked on a number of projects that have involved some large organisations. By large organisations, I mean, big hefty things that have been around for a while, have lots of cogs and yet still achieve a lot.
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.
There are many challenges in building an agile team. We hear about self organising teams, but how can a CTO ensure a roadmap is kept? We hear about #noestimates, but how can we plan anything without estimates? Failure is an important part of agile, but how can we accept failure in production? Communication is key, how can we encourage it?
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.
Released in late 2013, Remote: Office Not Required by David Heinemeier Hansson and Jason Fried (of Basecamp, formerly 37signals) immediately struck a chord, particularly in our industry. Suddenly it had become acceptable to want to work in places other than the office!
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.