As usual, i’ll do a quick description of my past activities :
- 2006-2008 : Time to grow again, and move to the Yahoo world. Becoming a pelegrin of Continuous integration, and all the related topics.
- 2003-2005 : Time to move to good programming practices, to follow growth of Kelkoo I’ve help to setup a development process to ensure work consistency accross all the team. I encourage also an effort to standardize tools used to build application.
- 2002 -2003 : I work for Kelkoo, a great developer experience. I develop a high performance service framework, which host for example the Kelkoo search service.
- 2000-2001 : Post doc in Australia, at Monash university. I work mainly on how constraint solver can help user to write flexible documents.
- 2000 : a Job for fluxmedia. I develop a little tool to ease XSLT processing over XML file, allowing to ‘pipe’, ’split’, ‘merge’ transformation.
- 1997-2000 : I did a PhD at INRIA, on the funny topic of :’Kaomi, a framework for authoring multimedia documents’, i work also on some aspect of SMIL.
- you can find a list of my past publications (here)
March 24, 2009 at 2:43 pm |
Hello Laurent,
I was browsing the web looking for some data on software quality and I found your posts very interesting.
I am from Bolivia, South America, my brother and I run a small software factory, we develop in PHP for clients in France, Spain and USA.
One of our important clients is asking us to put formal software quality metrics on our contracts, something like “… X errors allowed on production per every Y hrs. of development…etc.” with a penalty if we exceed the limit.
I was looking for statistic data of errors per hour of development or errors per line of code and general advice to better explain to our client the industry status on software quality and also negotiate something fair for both parties.
I excuse for this long post but I couldn’t find significant info on my first searches, I’ll appreciate any comments.
I also speak french just in case.
Thank you.
Best regards,
Camilo.
March 24, 2009 at 3:04 pm |
Hello Camilo,
The key approach when you speak of software quality, is to define, what’s quality for you …
it can be code quality : but application not working
it can be application quality : but code is crap
it can be both …. it’s mainly depend if you do a one shot application, or website … that will never change (micro site…) and in this case your prefer application quality.
Elsewhere code quality is a key success factor.
For PHP : php_codesniffer, and of course unit test and test coverage … will give a good idea of code quality.
Don’t forget to test nicely the DB connection, and to mock DB during test
You can also use specific tools to check security, code injection ….
Using more robust langages for WS (C / JAva) will allow to provide/secure more the code and the application.
March 24, 2009 at 4:42 pm |
Thank you very much for your comments and information, we are indeed facing quality challenges at this time, lot of work to do.
Best regards,
Camilo.