Thanks to John for his comment that asks a couple of questions I should have addressed in my Methodology and Madness – Introducing Process to a Development Group article. John’s questions are: How do you decide which to solve first? How long do you leave between introducing each solution? How Do You Decide Which to Read more…
Going back a couple of years, the development group I was contracting in at the time had decided to move out of its present chaotic state and start using a development process. I wonder how well that sentence conveys what they were planning to do? Just to clarify, the plan was this: all permanent development Read more…
Many thanks to John for commenting on my Performance Tuning article. I’d just like to quote a snippet of what John has to say: “After all there’s no point optimising code that doesn’t actually work correctly” It reminded me of something obvious I forgot to mention in my previous articles: another of the “sins” I Read more…
In my previous article on Performance Requirements I argued that performance issues are requirements, and that this is not well understood in the software development community in general. In this article I’m going look at the performance tuning of existing code, argue that this is also poorly understood, and discuss the right way to go Read more…
Performance – in this case meaning a piece of software’s run time speed – is one of those things that always seems to cause problems whenever and wherever it comes up. Unfortunately, I think this is because it is very poorly understood across the software development community in general. Harking back to a contract I Read more…