"Improving software quality, - by accounting for our slow brains"
Isn’t it amusing that the solution to complex problems you encounter in your work all of a sudden pop into your head? Maybe during dinner? In the shower? while watching a movie? How about that test you took at school, with that last tricky question, that you all of a sudden see the solution to, clear as day, three days after turning in the test?!
Have you noticed that the code you wrote a month ago now seems to suck? I’ve definitely had both the “Eureka”- and the “what the heck did I do here!?” syndrome lots of times over the years.
If you look up the scientific papers, I’m sure you’ll discover that the brain isn’t very fast. It can process massive amounts of data, but the throughput just isn’t all that great. So! How can we take this into account when trying to improve as software professionals?
The solution might be to constantly have a number (two to three) tasks going on at the same time. That way, thoughts and Ideas can mature over time, and smart solutions might appear almost by themselves.-) so… My theory is that we can improve quality and maintain productivity by working multitasked but at a slower pace…
What do you think?
