Developers should be allowed to deploy at any time. Many find this a scary prospect since it makes traditional release management and QA very hard. We have found that empowering developers to own the responsibility of deployment allows you to ship software much faster whilst maintaining or even improving the safety of releasing changes when compared to more traditional processes.
Made Tech Blog
Giving teams freedom to structure their own time
It can be scary to devolve a lot of managerial and planning responsibility to teams but we’ve found lots of positives in changing the way we approach time management. Allowing teams the ability to plan their workloads, holidays, working location and client engagement has resulted in a greater sense of ownership on projects.
Effective Client Showcases
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.
Semantically Stable Test Suites
When we run a test suite in most languages, we can also generate reports with percentage of code coverage. These reports aren’t all they are cracked up to be.
Planning is hard, can we do Kanban instead?
Planning is an activity that usually results in some emotional response, however it can generally be said that teams avoiding planning will also be avoiding thinking about the future in general. A lack of robust planning the detail in your organisation can bubble up to impact plans at the high level portfolio, causing serious consequences on Lead Time and Delivery Rate.
Finery awarded Website of the Year at Retail Systems 2016
We’re incredibly proud to announce that the website we built with the team at Finery has been named Website of the Year at the Retail Systems 2016 award show.
Cohesion, coupling and viscosity
One of the most important goals of a software engineer is to craft highly cohesive code. Cohesion refers to the grouping of code in a software system.
Code reviews using the pull request workflow
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.
Pair Programming
We’ve helped a number of organisations successfully adopt pair programming, giving their teams the ability to increase productivity, improve knowledge sharing and enhance the quality of their software.
How to survive your first tech talk
I hate public speaking. It’s one of those things that I avoid at all costs. Though when my Brother made me his best man, there was no getting out of delivering a speech. And when my colleague signed me up to a do a talk without my consent (thanks Chris!), there was no getting out of delivering a tech talk.
Get our latest blogs with our monthly newsletter. Subscribe now
