Uncle Bob's 3 TDD laws 1. Write no production code, except to pass a failing test 2. Write only enough of test to demonstrate a failure. 3. Write only enough production code to pass a test.
Ignoring a clearly broken situation reinforces the ideas that perhaps nothing can be fixed, that no one cares. And it quickly spreads among the team.
"If you can't run, how can you have fun? Well then let your butts burn" Kanchan told me jokingly. "WHY NOT?" was the thought and thus began my self-imposed small challenge of cycling for thirty days.
If you are working on asp.net mvc project and you publish using visual studio, sometimes you may face below error This program is blocked by group policy. For more information, contact your system administrator To fix this follow below two things 1. Add below lines in your web.config 2. Just remove all the contents inside... Continue Reading →
The fierce competition in the market place is driving many changes in the corporate world to cut costs, be more productive and be cost-effective. Many corporate are looking at ERP as a means to achieve these three objectives. However, the corporate history of ERP implementation is a mixed bag with many horror stories and some successful ones.