Most companies want innovation and many of these same companies utilise an incremental software delivery model to achieve it. These models can be big on short-term delivery but weak on long-term vision. Delivering features to production weekly, yet failing to realise the product vision. These models ensure we build things right, but they can deter us from building the right thing.
When it comes to unit testing most people fall into one of two categories. Unit testing advocates and unit testing sceptics. The reasons there are unit testing sceptics can often be from bad test implementations. Created by unit testing pitfalls.
We are often an apprentice. Whether that’s joining a new team with a new business domain. Or joining a new job that requires new skills. This means that we’re at the mercy of needing someone else to guide us. Leaving us in the dark, trying to make sense of everything.
As I move between clients often I find myself in the apprentice space a lot. And then wondering what approach is best. Ask lots of questions or hardly any? What amount of interaction makes sense?