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.
#1 Transaction Models & Strategies
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.
Continue reading “Improve Developer Quality Tip #1” »
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.
- How can this be the case?
- Who contributes to the success or failure of your software?
- What can be done to improve the chances that your software will be a success?
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.
Continue reading “It’s not ALWAYS the developers fault…” »