The ultimate management sin
The ultimate management sin. It sounds like this should be an easy sin to avoid, but it isn’t. You have some needs of your own as a manager, and these needs may run squarely against your intention to preserve and use wisely the time of the people working under you.
JPA Pitfalls: Generating IDs
This article is part of the JPA Pitfalls series. JPA makes it really easy to do things the wrong way, and makes it really unintuitive to do things right. In this blog post series I will go over some common JPA pitfalls, and introduce generating IDs.
Solidity and Typescript Part 1
The first part of the short post series will go through project configuration and setup using the latest packages and compilers available (to date). Visit the GitHub repository to see a complete project for this part.
JPA Pitfalls: Eager/Lazy Fetching
In this article, we are going to discuss different JPA fetching types, their pros and cons, and see which one you should prefer. This article is part of the JPA Pitfalls series.
Eliciting, Estimating, and Prioritizing an Epic Backlog to Deliver Value - Part 2
Separating product features into "Must-haves", "Should-haves", "Could-haves" and "Would-haves" (commonly known as MoSCoW) can provide a great deal of information about how to prioritize work for a new product release.
Scrumfall: The Fall of Scrum
In his book Scrum: The Art of Doing Twice the Work in Half the Time, Jeff Sutherland introduces us to the idea and origins of Scrum. He brings us to a time when he was serving as a pilot in the air force during the Vietnam war. They had a clear directive - OODA: observe, orient, decide and act.