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. After getting to the bottom of relationship mapping in the previous blog, I will go over some common JPA pitfalls in Eager/Lazy Fetching and show how to avoid them.
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.
JPA Pitfalls: Relationship Mapping
This article is part of the JPA Pitfalls series, and our first topic of discussion is some common JPA relationship mapping pitfalls. JPA makes it really easy to do things the wrong way, and makes it really unintuitive to do things right.
Mocks - Fake it ‘till you make it?
To mock or not to mock - why is this discussion even on the table? Somehow it’s a complete no-brainer that the answer is a straightforward ‘yes’ since developers need to remove all dependencies and use mocking frameworks to write reliable, repeatable tests yielding consistent outcomes.