top of page
Search


Code Rule #04: Prefer String Formatting over Concatenation
Discover why string concatenation with + or . creates messy, error-prone code — and how sprintf-style formatting leads to cleaner, safer, and more maintainable software. From readability to AI assistance, here's why you should prefer string formatting over concatenation.

Mateusz Roguski
Apr 248 min read


Code Rule #03: Be either declared final or abstract
In modern OOP, every class is a decision. Should it be reused? Extended? Or locked down? This article introduces a simple but powerful rule: every class should be either final or abstract — never left open by accident. You'll learn why this matters for architectural clarity, how different languages support it, what design patterns and principles it promotes, and how it even improves AI-assisted development. A must-read for developers who value clean boundaries, safe code, and

Mateusz Roguski
Apr 197 min read


Code Rule #02: Annotations Are Not Architecture
Annotations are convenient — but convenience is not architecture. In this article, we explore 10 hidden drawbacks of overusing annotations and attributes, how they break core design principles, and what to do instead to build systems that are clear, testable, and AI-friendly.

Mateusz Roguski
Apr 188 min read
bottom of page
