Whoever plans and does not execute becomes a mule without a head. But those who execute without planning, will come to dust.
Everything that is complex can become more or less complex. If the development of a computer system is more complex than initially anticipated and, even after exhaustive testing, putting it into production seems to be asking for failure to come, it is time to improve the system planning rather than try to correct the flaws of what has already been developed.
That is, it specifies the system again and restarts development.
When the success of the computer system does not seem to be possible, do not insist on debugging. Without a crisis, restarts everything. Even if success takes longer, it will be much more intense and lasting.
Imagine a surfer entering the sea. As he goes entering the sea, the waves get bigger, less frequent and with the “fatter” ridges. Now imagine that the waves is computer systems. Trying to drop a wave is like debugging a system. Returning a wave corresponds to specifying the system again.
If a part of a computer system has already gone into production successfully during the development of another part that needs a restart, as I said before, you don’t have to restart everything from scratch. In other words, you don’t have to go back to the sand, just go back to the the wave gives you trouble.
Now imagine that the part of the computer system that has already gone into production successfully is the current wave and the problematic wave is the next. If the problematic wave does not seem to be possible to correct, returns to the problematic wave, not all the waves. If don’t come back, mad cow …
Returning a wave brings a good tranquility. But doesn’t relax, plan to pass the problematic wave. Spend your strength on this planning, not on dropping the current wave. Because, without planning, mad cow…
Paulo Ricardo Silveira Trainini
Lamentamos que este post não tenha sido útil para você!
Vamos melhorar este post!
Diga-nos, como podemos melhorar este post?