Which means that the people who speak louder online, with higher frequency and reach, are not necessarily the ones striving for Independence, Depth, Honesty, or Breadth through the content they create. They are not necessarily the ones equipped with the experience and knowledge required to share thoughts that will provoke change in our industry.

This is such a genuine opinion, beats the odds that, if you are an individual who is an industry trendsetter, then you do not have time to write about the content that you are working on. So anyone who has the power and time to write will have a perspective on how design should be.

Effective Java is always a good book to read and this latest edition is no different. Here is the Amazon link to get the book. Here are some code samples and presentation promoting the book. My quick code snippet from the book.

There are different ways to get a custom error message page in spring boot. The following solution worked for my web project. Here is the overview of the structure.

Pic

To start with, if there is 404 error, then we want a custom error page showing up instead of the spring boot’s default page.
The first thing we are going handle is to suppress the boot framework’s error page. For this, we will go to the application properties and add the following line

server.error.whitelabel.enabled=false

As we are done with that, now let us implement the ErrorController interface. The thing to keep in mind is, we have the LOG entry that says what happened to the code base as we reached here. Here is the sample code.

One other way that we can add the custom error message is using the Spring 2.x’s ConfigurableServletWebServerFactory implementation. We add this to the main method of the web module. Here is the sample code for this entry.

Let us try to put together some JUNITs with Spring 5 injection. One of the most challenging things of integrating JUnit and Spring was the role of the IDE. It is important to keep an eye on that.
So here is the code we are going to look.

Now when we are running the JUnit, we have to make sure the @Test annotation is from the JUnit jar file. If you accidentally have the TestNG’s @Test annotation, it will not be able to understand the configuration that we have in the JUnit header. Finally, remember to make sure the IDE is not making anything goofy where it pulled a wrong Annotation class. Here is a useful Stackoverflow discussion on this.

I really enjoyed this commencement speech from David foster. This was from Tim Ferris news letter. The narration where the speech is talking about compassion. In the middle of the speech, I was thinking this is another left wing constructed speech talking about first world problems. I was wrong, and am glad that I heard the entire thing.