Solutions Architect | Developer | Blogger
Solutions Architect | Developer | Blogger
When I first encountered Entity Framework Core interceptors, I honestly did not pay much attention to them. At that time, I was busy solving more visible problems like wrong data, slow queries, or strange bugs in production. Interceptors sounded like…
When I first encountered shadow properties in Entity Framework Core, I honestly did not understand why I would ever need them. I was already comfortable adding fields directly into my entities. If I needed CreatedAt or UpdatedBy, I just added…
When I first started working seriously with Entity Framework Core, I treated it very simply. A string is a string, an int is an int, a DateTime is a DateTime. Life was easy. Then real business requirements arrived. Not tutorial…
When I first started using EF Core in real projects, performance was not something I worried about too much. Most examples online worked fine, the database was small, and the business requirements were still simple. I honestly thought performance tuning…
When I first started using Entity Framework Core, I had this feeling that everything was almost magical. I write some LINQ, hit Run, and boom, data comes back. At the beginning, that felt amazing. But later, when projects became bigger…
When I first started using Entity Framework Core seriously, I thought transactions were something “already handled by the database”. I remember thinking, why should I worry about transactions when SQL Server already knows how to keep data safe? That mindset…
I always tell people that EF Core is one of those tools that looks very simple in the beginning. You do a few queries, call ToList, and everything feels fine. Then the business side comes in and suddenly you are…
If you have been working with EF Core for a while, you probably stumbled on something called tracking and no tracking queries. When I first encountered these, I honestly did not pay much attention. I thought EF Core was smart…
When I first learned about Clean Architecture, it looked like the perfect way to build software. Layers are separated, dependencies are inverted, and everything seems to make sense logically. But after looking around different projects, talking to other developers, and…
When I started writing software, people always tell me about patterns, architectures, clean code, solid, layered design, all those big words. They are all helpful, of course. But after many years of building systems in real companies, fixing production issues…
