One of the essential parts of SCRUM is cost estimation. Some authors even recommend estimating in 2 iterations.
In my case, I don’t do the second estimation with real time. I think it is an extra effort that doesn’t pay the bill. In the other hand, I think that the fuzzy-and-intuitive cost estimation with Story Points is great :).
I like to think about…
I like how Martin Fowler writes, but beyond that, I liked a lot the content and philosophy behind this book.
The books explains design patterns very frequent in enterprise applications with examples. It also includes diagrams and implementations in Java that explain the scenarios.
The book is intended to be for any software developer but if you are a Ruby on Rails developer, I’m sure you’ll enjoy reading the theory and the discussion behind some patterns you use every day. Ruby on Rails is clearly inspired by this book and it is a phenomenal reference for some concepts.
I have to confess that until last year I was not paying attention
to keep gems updated. My top 3 excuses:
“I had to find time” because “It was going to pay the bill”.
After the experience I became fan of having dependencies updated as much as possible. I learnt some lessons.
Senior Software Engineer @ Jobandtalent. Previously CTO @ Playfulbet.