80% of development time is spent in bugfixing and yet 80% of software defects that impact performance or scalability are only caused by a handful of architectural problem patterns.
So, why not understand what these problem patterns are by learning from others and make sure to avoid them right from the start?
After a quick intro to the problem of bad quality code itself, we walk through 6 specific examples of applications I've analyzed from a performance, scalability and architectural perspective. Each example highlights the impact of quality, the root cause and the technical metric to look at before checking in code to avoid these problems:
The final piece of advice is to verify some sanity checks before checking-in code but more so automating these checks when executing your automated unit-, integration- or functional tests. Most of these problems can be identified with single user tests.
More examples on metrics can be read on our blog – http://blog.dynatrace.com – by following me on @grabnerandi – and by using the Dynatrace Free Trial which stays free after 30 days when analyzing apps running on your local machine.
Andreas Grabner is a Technology Strategist at Dynatrace. This talk was recorded at the San Francisco Java User Group, May 26th 2015, in downtown San Francisco.