Software Design

Something that’s often overused, misunderstood, or just incorrectly applied in software development: Data Transfer Objects (DTOs). DTOs are a common pattern, but like many things in software, they tend to get used in places where they don’t actually solve the problem at hand. So, what are DTOs really for? When should you use them? And when are they just extra work with no real benefit? Let’s dig in. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. What Are Data Transfer Objects (DTOs)? First, let’s start with… Read More »DTOs & Mapping : The Good, The Bad, And The Excessive

You Aren’t Gonna Need It. The essence of YAGNI is simple: don’t build something today that you assume you’ll need in the future. However, there’s a nuance here because we also don’t want to handcuff ourselves. Let’s explore how this principle applies both to features and technical implementation. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. The Two Sides of YAGNI First, let’s break down how people often think about YAGNI. On one hand, there’s the feature side. When developing a product, you might think you’ll… Read More »Do you really need that abstraction or generic code? (YAGNI)

DRY Principle is seemingly advocated for or against. In reality, it’s not good or bad so as long as you understand why you’re applying it and for what purpose. Misunderstanding DRY is why your system can turn into a hard to change rats nest. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. Don’t Repeat Yourself (DRY) When it comes to DRY, opinions are all over the map. Some folks swear by it, while others argue it’s the worst idea ever. The truth? It’s not inherently good… Read More »DRY principle is why your codebase sucks?