“Refactoring is the process of taking a running program and adding to its value, not by changing its behavior but by giving it more of these qualities that enable us to continue developing at speed.” – Kent Beck
A new developer gets his hands on an existing source code, and soon your hear this complaint : “Code is a mess, it must be refactored !” Sometimes, that’s true, and some other times, that’s a great recipe to end up with a code as bad as – or even worse than – the initial code. To decide if a refactoring is required, here are ten questions you should ask yourself (or the developer asking for the refactoring): Continue reading
Project postmortems help improving a development process. But before planning one, ask yourself why you need it, and what will be the consequences of doing it or not. There’s nothing worse than collecting people’s feedback, and then ignoring it. If you are not ready to take actions to improve things, just don’t do a postmortem. Else, the following tips may help you get the most from your project postmortem : Continue reading
One of your customers reported some very slow Microsoft SQL Server database access times. You restored his database at home, and were able reproduce the performance issue. But after the first execution, your super-slow query is now blazing-fast. Still you didn’t make a change… This is a courtesy from the SQL Server performance engine which cached a lot of things related to your previous query execution. How can you clear/flush this SQL Server cache before executing your performance tests ?