For a bit more than half a year ago I decided to leave the corporate world. I moved to Ocado Technology which was starting a new office in Wroclaw at that time. I guess I forgot to boast about it. This post won’t be about how great Ocado is or anything like that (however if you ask me, it is). I just wanted to share one thing that we did in Wroclaw, which
Estimates are all about time. During one of last retrospective I realized that for some people estimates, and their role, are not that well understood. If not perceived well they can create pressure. Because what happens when we estimated the amount of work needed wrong? What happens when what we declared is significantly different than what we actually needed to fulfill our task? Estimates are provided by developers and mean
One of my latest tasks was to review and refactor unit tests in our system, which I found especially suitable for me. After presenting my results to the team guys asked me to create a page on Confluence describing my remarks and proposed practices we should follow – what a great occasion for a blog post. So here I present some practices that in my opinion (and my team’s opinion too) can improve