Design code Java!

Yeap, I have the pleasure of announcing that I’ve started my YouTube channel . It was a daunting task, but I've taken the first step to start talking about topics that I enjoy and how much I enjoy them!

I was looking for a good code design and good practices channel that was simple and objective. Therefore, instead of complaining about not finding one, I created mine.?

For me, it is also an opportunity to be closer and share experiences about Java code and my favorite programming paradigm: Object-Oriented Programming.

I got some issues from code reviews (from other people's code and mine) and explained the reason for going in a particular direction instead of another.

I plan to go beyond Java: Talk about Java, good code design practices, Cloud-Native, Software Architecture, NoSQL databases, and more!

If you have any topic or suggestion that you wish to be discussed, please, send them using this form .

Form link: https://forms.gle/m3GicSvg2trnUJMX9

Articles:

• Now It's Time to Uncomplicate With the Not-So-New API in Java: In this article, I explore the options around Java Date. It is not a new API. However, it is still a relatively unused API.

Videos:

• The Power of Enum : Enum is a feature that almost every language has. On Java, you can go beyond and combine it with design patterns such as strategy, singleton, and so on.
• Java's Encapsulation - When the getter and setter became your enemy: Encapsulation is key to a good code design. But what does that mean? Surely, it does not mean adding getter and setter methods to all private fields; those are POJO, or JavaBeans. This video explains why that's not a good approach.
• Builder Pattern and Fluent-API - how to create complex objects with Java : When an entity has several rules, we need to make sure it is created consistently. This video will explain two patterns to achieve this.
• Optional in Java - When better code is not an alternative: Learn how to combine the Optional API in your Entity Model to achieve a good design and avoid the million-dollar mistake: the Null.