I am a firm believer that anyone should have a side-project. It does not matter if it is for pure learning purposes, fun or with the goal of making money.
Sometimes, we have to measure the execution time of certain code blocks. The traditional way would be to capture start and stop time with System.nanoTime() and print out the difference.
Works, but gets messy when you try to capture more than one time.
I bet your answer will be something like “yes, definitely, or are you crazy?”.
I’ve started helping out on a pretty old legacy system. It’s in its second decade and probably not far away from 20 years of existence. It went through many developer hands, everybody leaving its mark on it, myself included. There have been several attempts to reinvent it or at least parts of it, but none has been really successful so far. It is a mess, but it still works.
I covered properties handling in Spring Boot a while ago in my Learnletter. This page summarize all emails to make it easier for you to dive into the topic.
That’s the most common error when starting with Spring. Most of the time, it is an error made by us and Spring complains rightly. Sometimes, however, it is not one simple, stupid error caused by us. Reader Mark did have one of those rare exceptions last week.
Did you ever come across a piece of code and you though “wtf??? which idiot did write that junk?”.
In this short tutorial, we’ll cover how to receive a webhook from Paddle in Spring Boot properly.
In the last recap session, we take a look at doing validations.
One way of handling errors in Spring MVC is by declaring a responsible class using the @ControllerAdvice annotation.