Evolution
Test Driven Development (TDD) since its rediscovery by Kent Beck in the early noughties has led to an evolution in the information technology developers of our species. So where on the test driven developer evolutionary tree do you or your developer kind sit?
This is a light hearted look, with some serious undertones, at the evolutionary state of Test Driven Developers. I hope you enjoy your journey of discovery…
Continue reading “The Evolution of Test Driven Developers” »
This developer quality tip is about keeping abreast with leading thinkers/players in your field. For me one of the leading thinkers in the software development field is Neal Ford from Thoughtworks. This tip relates to a topic Neal has been advocating since early 2009 – ‘Evolutionary Architecture & Emergent Design’.
Neal didn’t invent either concept, but is responsible for bringing them to my attention.
Doing it wrong!!
I have an almost unhealthy infatuation with productivity and ways to improve it!
It begun many moons ago with a to-do list written on a scrap of paper. I started writing to-do lists for all kinds of things. What I planned to do at work each day became a to-do list. Things I planned to do around the house became a to-do list. As many others before me, I learned that having a to-do list itself doesn’t result in improved productivity.
Sure, I got things done and felt a sense of achievement, but I constantly felt frustrated by the number of incomplete lists. My infatuation with improving my personal productivity had begun.
Continue reading “A Constant Strive To Improve Productivity” »
It's not 'ALWAYS' the testers fault...
…that your software doesn’t work!
I’m not saying it’s never the testers fault. What I am saying is this. It is not just the testers who contribute to the success or failure of your software.
Product/Business owners….Lets discuss it!
This is the 2nd of 3 discussions around the roles and responsibilities of the Product/Business owner in the agile software development life-cycle. In this 2nd discussion I will look at the roles and responsibilities of the team members at the iteration level. In a previous discussions I looked at their roles and responsibilities at the project level (It’s not ALWAYS the developers fault…). In the final discussion I will look at their roles and responsibilities in the story delivery life-cycle.
Writing Computer Code
This is the first in an ongoing series of tips for improving developer quality. Each tip will highlight development skills that I believe help improve code quality. Skills developers can learn via the resources linked to in the tip. Skills that once mastered will lead to better quality solutions.
This first tip looks at transactions. Good developers can tell you that transactions need to have ACID (atomic, consistent, isolated and durable) properties. They will also be able to tell you that transactions help recover from failures and help to keep the data in a consistent state.
It is not 'ALWAYS' the developers fault.....
…that your software doesn’t work!
I’m not saying it’s never the developers fault. What I am saying is this. It is not just the developers who contribute to the success or failure of your software.
Product/Business owners….Lets discuss it!
This is the 1st of 3 discussions around the roles and responsibilities of the Product/Business owner in the agile software development life-cycle. In this 1st discussion I will look at the roles and responsibilities of the team members at the project level. In subsequent discussions I will look at their roles and responsibilities in the iteration and the story delivery life-cycle.