Skip to content

πŸ“š /blog

Here you’ll find a collection of posts covering different topics, updates, and notes worth sharing. It’s the main place to explore what’s new, catch up on recent entries, or dive back into older posts whenever you like


Finding The Best Design Pattern for Interfaces

Design pattern is a super useful concept in programming. They keep your code consistent and structured, which makes your life way easier. Personally, I'm a huge fan and think they should be a must for every project. It's not that I'm a pattern guru; it's just about having a consistent way of doing things.

After all, everyone implements these patterns differently. Whether you're an expert in ISP (Interface Segregation Principle), CQRS (Command Query Responsibility Segregation), or something else, each person will have their own implementation style. Some stick strictly to one pattern, some mix a few, and some just wing it. It's all good, as long as you create a standard to follow, and just document how your pattern works later.

Warning

Don't start coding until you know what pattern you're going to use!

Building a Second Brain

I recently came across this super cool concept called a Second Brain, thanks to Hilman's Twitter thread and the book Building a Second Brain. Basically, it’s a personal system to store and organize all your information so it's actually useful later on.

Why do we need one? Our brains are amazing for thinking, but not so great at remembering every single detail. Without a system, all our ideas and notes can feel scattered and hard to act on. A Second Brain helps you capture, organize, and retrieve information so it's useful for work, personal projects, or just daily life.