Dealing with Technical Stories

Practical Software - Dealing with Technical Stories

One of the first thing they tell us about stories, is that they should be valuable.  That’s what  the ‘V’ in INVEST stands for: Taken from: http://en.wikipedia.org/wiki/INVEST_(mnemonic): V – Valuable – A user story must deliver value to the end user. That suggestion usually sits quite well with business side people, which nods in agreement when they […]

Technical Debt – Will hit you 3 times

“Look, it’s critical that we meet our deadline, and I know that we are already running behind. So please, we need you to push faster no matter the costs. And I don’t care if you need to cut some corners on the way. I’m totally aware of the costs, we just need to meet the […]

Testing Legacy Code – Initializer blocks

dominos blocks falling

Writing tests for legacy code may seem risky, even daunting: will we break our code? Will we need to rewrite extensive parts of our code in order to test it? Not many know that by following fairly simple practices we can start unit-testing our codebase with minimal risks. Here are two examples of how to […]