Recently I read this article for hte indispensable developer. If I have to sumarize the article in one sentence it is “Consider the context” ! Please read it there is “novinka” as chessmasters said!

Two or three weeks ago I read a post of Michael Nygard “Failover: Messy Realities”.
It’s very interesting to see that among normal operation state ,failure state , and normal state again there is a whole universe. By the way in my humble experience I had a case where I had to explain of my American colleagues similar problem where during surgical operation they had implemented restart of surgical operation hardware due to firmware failure! The result of this restart was memory leak and unloaded dynamic library. Hardware restart was necessary approximately on 10 to 15 minutes.  I can’t explain you how hard was for me to explain them that we have a memory leak and instantiation of dynamic libraries throwing data from the hardware to the software application. The application responsibility is to decide to signal to surgeon if the surgeon is close to a spinal cord nerve !!!!!!!!! As I know they had done an operation already in parallel with the old system. But I am not sure how safe was that combination between the old system and the new one.  Probably the advice is to know the dependency of the system and it’s behavior during failure.

Today I read the post Pair Management of Michael Feathers. There is something interesting that wasn’t mention in the post. This is hte  fact that pair management will reduce the risk in taking decision but this fact  probably must be proof from the researchers in the Management science.  Probably you know that every decision on management level costs 100 to 1000 times more time than a software mistake so you can imagine what influence could have pair management in software projects.

Today I read this post “Study shows brief meditation helps cognition” of Andy Hunt which is very important for every professional software developer. If you have some interests in this area please read  the post, you will like it!

Recently I read an interview with Donald Knuth. I liked the answer of the question
“Do you think deep analysis of a problem or a solution to a problem is something that can be taught?”.
Read it !

Today I read the Top Five Causes of Poor Software Quality. Don’t you think that in some way the root of the problem is clear strategy for technologies, platforms usage, and lack of serious self education?

Recently I read this article by Bill Curtis. I think that this one of the articles which should be read many times because it shows us one of the roots of our problems in software development.