Hi,
Do you know the feeling? You turn on a device that you use over and over again. For years. You recognize the sound it makes.
The rhythmic “whoosh whoosh whoosh”, when you start the dishwasher.
Or the familiar “click” when the oven turns on.
Your signal: everything’s working. Carry on!
It no longer meets your expectations?
That’s exactly what happened to me with my microwave.
Are your controllers constantly filled with primitives? In ArticleController, the first line of every method is: articleRepository.findById(articleId). We keep making the same conversions. I hardly observe as many primitives in any other layer as in the API layer. This leads to much boilerplate. The code becomes harder to test. And it’s harder to read. Yet we know how much easier it is when we work with type safety. In this article, I will show you how to use the Converter Interface to automatically convert your primitives into the correct type.
Hi,
“The VPN should not be operated by you [Sysadmins].”
After this sentence, I saw startled faces.
It slipped out of me. During the weekly Jour Fixe between the developers and admins.
It came to the question of what our priorities are.
It hit a nerve.
Probably not because the participants are emotionally attached to the VPN.
Probably not because the statement is wrong.
No - it’s more likely because it’s so unconventional for the team.
In almost every web application, logic related to the user must be executed. To access this, his data is assigned based on his authentication. With Spring Security, the authentication framework in the Spring stack, we have various ways to accomplish this essential task.
In many applications and examples, it is common to statically retrieve the SecurityContext in Spring to access the current UserDetails. However, this has some disadvantages:
Hi,
Last week, emotions were running high.
One of my clients achieved something extraordinary. They have successfully operated a product for 10 years. Highly profitable.
But the project was not started by trained developers. It began as a side product. The initial developers were career changers. Highly interested, motivated, engaged, and experts in their domain.
And they accomplished something that fails in 9 out of 10 cases. Their product is actively used. Customers happily pay for it. It solves a real problem. In a niche that hardly any other company can occupy.
Marcus Held