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.
We don't need software that just works, but be able to build to adapt and most importantly build and adapt as quickly as possible. That's easier said than done. Numerous challenges slow us down in achieving the state of adaptability. "What slows us down?" Well, it's the crappy, unreadable, tightly coupled code that we have written or writing.
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.
So many books, so little time. In addition, every day we have tons of digital content made available in almost every area. Here are some of my picks in Domain Driven Design
So many books, so little time. In addition, every day we have tons of digital content made available in almost every area. Here are some of my picks in Design Thinking & UX
Innovation is a miracle when a special person raises their hands to God, the Red Sea is parted or the iPhone is born
A wireframe is a low-fidelity, simplified outline of your product. There is a verity of tools available in the market ranging from it's simplest form of pen & paper to all the way hi-fi drag & drop. Below is the list of some that I like