Showing posts with label problem solving. Show all posts
Showing posts with label problem solving. Show all posts

Thursday, January 28, 2010

Systems performance: an optimizing benchmarking and profiling process

I've been doing lots of performance work recently (hence the lack of posts), and I've found a nice article on mid-life crisis for .net developers. This msdn entry "10 Tips for Writing High-Performance Web Applications" is good as well.

 
Perhaps the most important aspect of performance work is to adopt a consistant approach - I found that PDCA works very well.


 
  • Check - benchmark and profile your code
  • Act - Analyze the results to understand the bottlenecks
  • Plan - Create a theory for how you can improve performance
  • Do - Implement the theory, and go back to the first stage
Repeat this a few times and you can get some major learning about how a system works, and ultimately improvements.

  

Friday, October 24, 2008

Pentasolve: a problem solving approach.

I'm adopting a new technique today, Pentasolve: a problem solving approach.

Principally this means when faced with a [technical] questions I will attempt to generate five candidate answers.

I will then select the best answer. I'm doing this for a number of reasons:
  • Creativity: It will force me to consider more left-field solutions.
  • Peer pressure: It will allow any "obvious" solutions to have peers that it can be evaluated against.
  • Maturation: This process will give ideas more time to evolve before I fix on one.

Why five? no scientific answer to this - three seems too small (I can always think of three, five forces me to think). More than five seems to be overkill.

I'm about to attempt a relatively complex product development, so I will see if this technique helps or not.

PentasolveTM - solving your problems 5 steps at a time ;-)