When interviewing someone, whether it’s a small or big company, I always come back to one thought – “What will they be like tomorrow?” When we grow outside of this shoebox? When our product scales? When the team gets bigger? Will they be able to grow with us? Will they be able to lead with us? Will they be there with us tomorrow? This is the question that always nags at the back of my…
I’m not the greatest QA tester. I’m not even sure if you’d consider me mid-level. But I know the results of what happens when you don’t test properly when all you focus on is the happy path and never consider what might go wrong. Edge cases aren’t my master but they do sit at the back of my mind, driving the course of development so I can be sure they are accounted for in what…
Most likely it’s evolved. Beyond what you started doing, beyond what was in the paperwork. Perhaps what is leaps and bounds from where you started two years ago where everyone was elbows apart and now you are miles away from each other. Despite all that, do you know what your job description is? I’m not talking about the one that everyone can pull up from the company website and go “here, this is what I…
What is it that you deliver to your customers? Your team? Your CEO? Your clients? Writing code, building test cases, writing requirements – those aren’t what you deliver – they are the output of what you deliver. Here are some ideas of what you can deliver (written in the I format) I deliver scalable, performant solutions. I deliver software that takes a licking, keeps on ticking, and comes back to life when everything around it…
Let this picture sink in. I don’t know who made it but it’s perfect. If you want every possible test scenario run, then you should be prepared to pay for every random test scenario. The problem isn’t in the code we write (that needs to grow and iterate and develop) but what we are willing to pay for it. If you are using something beyond its means, beyond what it was originally intended to do…