The bug we presented in our previous post got a lot of very interesting comments. So, big thanks to all of you who did share your point of view about it
I am not a QA expert; my experience as a consultant is more oriented towards code quality and development lifecycle’s best practices.
So I was curious about more authorized opinions before to start formulating some hypothesis in this second post.
As a Quality consultant, I love nothing more than finding bugs.
Nothing more fun than analyzing the code of an application and find one or more big good unforgivable bugs, as an ABAP ‘Break’ (instruction used in debug mode that will instantly stop the program), an OPEN / CLOSE file in a loop (time consuming instruction that should be placed out of the loop, obviously) or direct access to the database from a JSP page. No need of a specialist to know that these are serious defects.
Yet there is a situation when I hate finding bugs: as a user of an application.
It’s been a while since we talked about Sonar. I was a bit busy recently to discover new territories (see previous posts Elastic Software, Quality in the Cloud) so I am late in the update of my Sonar environment. Furthermore, there is a new release 3.0 with a bunch of new features.
So without further ado, the time has come for a Sonar upgrade. Continue reading
In our last post, we explained the concept of elasticity as the ability to move resources within a virtual infrastructure to answer business demands and (not always predictable) peaks with the best possible responsiveness.
Now, it’s not only about the ability to ‘inflate’ infrastructure by adding necessary resources, but also to ‘deflate’ it by reallocating these resources elsewhere. Like a balloon, the more elastic the infrastructure, the more it is easy to inflate and deflate.
What does that mean for your applications? Are they ready to go into the Cloud?
As we have seen in a previous post – Quality in the cloud – cost reduction remains the main motivation when it comes to go into the cloud and virtualized infrastructures. Then the second main reason is Capacity management.
When you have to size a physical infrastructure and a operating budget to manage it, the model is this one:
Well. I decided not to do a post each time the blog goes up a new level, but that’s too funny. Continue reading
I am still playing with the City Model plugin for Sonar made by eXcentia.
For those who missed the previous episodes, you can find them here: City Model, City Model – New release, The ABC metric.
This plugin is really fun. And everyone finds fantastic a visual representation of the code in the form of a city. Going to the essential is important when you regularly assess the quality of applications.
I have been involved recently in some discussions about the usefulness of the LOC (Lines Of Code) metric. As I explained in some previous posts, this is the first one I look at when doing an assessment of and application and its code quality. And I do it only to get an idea of the size of the application. Continue reading
Do you remember that I got a nice Christmas gift?
It was the Sonar plugin City Model made by eXcentia and they have released a new version. This will let us the opportunity to show how to customize your own dashboard with Sonar.
Methodologies. Agile. Scrum. Extreme programming. Lot of methodologies. « User stories » is currently very fashionnable. That’s Ok.
When I was a developer, I did not think about methodologies. You are a good developer or you are not. And if you are not, there is no methodology that would change that. Continue reading
