❌ I removed AutoMapper…

by Jan 12, 2024

❌ I removed AutoMapper…

It was making my code more complex without reaping the benefits 🚫.

Why? 🤔

Low no. of entities to map in my codebase.

I was defining all field mappings anyhow because I like explicit mappings. 🧩

So, it didn’t solve a problem for me. But it made mappings more complex. 📚

What did I replace it with? 🔄

static Create methods on my DTO’s, like FromCustomer() and ToCustomer().🚀

Works perfect for me! ✔️👌

What do you think? 🧐


Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more