Working smart, not working hardA common problem for servers in coffee shops is remembering who's drinking regular coffee and who's drinking the decaffeinated stuff. A coffee shop manager with unlimited time and resources might send all the servers to Kevin Trudeau's Mega Memory seminar, where they ' d learn to vividly imagine a calf with a hide that matches, say, the customer's paisley tie, so that seeing the tie at refill time would trigger the thought of the paisley calf-and decaf coffee. Most coffee shop managers
take a much simpler approach to the problem, though: they just tell the servers to give you a different kind of cup if you order decaf The server need only look at your cup to know what type of coffee you're drinking..
Very adex, when we encounter problems, maybe just use a slight way to solve it, this work can be more than half-effort, no longer selling up late, but also completed the project as scheduled. Small changes may produce amazing results, so do you easily observe the existing job method, will it be easy to happen? Is it a lot of time? If so, find out a simple and effective way to improve these situations.
When seeking solutions for problems, I will correct the questions once again, and cultivate themselves to make accurate problems and come up with better answers. But light is not enough, accurate issues may also be wrong, will get no help. It must be noted that if the problem is cut, whether it is the purpose of truly want to achieve, whether it is an ideal situation.
Don't fix bus latter; fix it. * The constant message to programs is this bugs are serious and must not be ignored. This point is emphasized Right from
The Start of The Project And Receives Perpetual Reinforcement.
* Programmers Become Solely Responsible for fixing their owing bugs. No longer do the careful program bend to Help FIX
The Bugs of The Sloppy Programmers. Instead, The Careful Program Get To Implement The Features The Sloppy Program
can not get to because they're stuck fixing bugs in their earlier features. The effect is that programmers are rewarded for being careful. Justice! * If programmers are fixing bugs as they're found, the project can not possibly have a Runaway bug-list. in Fact, the bug-list
Can Never Sneak Up and Threaten Your Project's Timely Delivery. How Could It? You're Always Fighting The Monster While
It's little.
* Finally, And Perhaps Most Important, Requiring Programmers To FIX THEIR BUGS As The Find The Makes It Quite Apparent IF
A Particular Programmer Needs More Training-His Or Her Schedule Starts Slipping, Alerting You To a Problem That Mightotherwise Go Unnoticed.
Although this view is also very correct, it seems that there is not much relationship with this chapter. Is the author want to explain this is also a strategy?
Timely discovering and modifying BUG is important, but I think it is more important to prevent BUG from appearing. TDD (Test-Driven Development) is a quite a good method. If there is a perfect test case, whether it is developed or reducing the chance of BUG appearing during the modification.
