Here’s a brief post. I’m not sure how to start it. It’s one of those “why didn’t I think of that” moments while reviewing some existing code. Due to NDAs, I cannot share the actual code. It has something to do with handling revisions. The closest thing I can relate to is how WordPress (WP) handles blog posts and revisions.
In this post, I’d like to share a lesson learned by one of the teams at O&B. They were using Spring Boot with Spring Security.By default, anything that is protected by Spring Security is sent to the browser with the following HTTP header:Cache-Control: no-cache, no-store, max-age=0, must-revalidateEssentially, the response will never be cached by the browser. While this may seem inefficient, there is actually
I was recently surprised by how one code base had public default constructors (i.e. zero-arguments constructors) in all their domain entities, and had getters and setters for all the fields. As I dug deeper, I found out that the reason why the domain entities are the way they are is largely because the team thinks it was required by the web/MVC framework. And I thought it would be