JPA Pitfalls Part 2: 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, we will go over some common JPA pitfalls in Eager/Lazy Fetching and show how to avoid them.
Adam Williams: The Future Outlook and How to Steer Long-term Value in Private Equity
Adam Williams, Vice President of Private Equity at Symphony, has been in business leadership roles for over 20 years. Adam started his professional story as a school teacher and coach, and his love for sharing knowledge is what ultimately drove all of his roles in the future.
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.
Eliciting, estimating, and prioritizing an epic backlog to deliver value
Working on projects in the “Complex-Chaotic” quadrant intersection of the Cynefin diagram, where today’s projects are mostly found, can be quite challenging. Trying to gather every valuable input, feedback, and requirement from a stakeholder group that is large and dispersed, lacking in communication and collaboration between its representatives, product or feature owners, and not having a single point of decision making, can easily discourage and demotivate.