I must confess it: I have always been wary of the concept of technical debt. It has always seemed a marketing concept to me.
It’s like if you decided to buy a car, and the salesman will be giving you the keys and proudly adds with a smile: “you owe already $ 10 000”. And he does not speak about the car credit, no, he simply means that the car you have just bought contains certain flaws that will become increasingly apparent over time, and weary the engine, the body, even probably the driver.
How would you react if a salesman told you that? Would you buy this car?
One number for the post today: 1001.
This is the number of unique visitors on my blog Qualilogy in 3 months.
Maybe you remember that, at December 31, or 40 days after it has been launched, 300 visitors had made 456 visits and saw 1,160 pages.
I was invited last week to attend a marketing event where different customers did talk about their experience in the world of Cloud and virtualization.
It was really interesting: I learned a lot, but especially, I discovered the vision of the production teams about… application quality.
A message to the project teams: good times are running out. Continue reading
We saw in the previous post ‘Use cases – Working seamlessly together‘ what use cases are most often applied with a code analysis tool, and provide the greatest benefits:
- Quality Gate to validate the delivery of a new application version.
- Management of SLAs and benchmarking of providers.
- Continuous Integration / Improvement.
We have seen in the previous two posts that some quite common use cases require just a limited number – 10 to 20 – of metrics. These use cases are:
- Validate the delivery of a new version of the application (Quality Gate).
- Get objective data for SLAs.
- Manage the Continuous Integration / Improvement processes.
A comment in the first post asked: “What are these 10 or 20 most important metrics?”