SlashSlime
Category
- Alex
Text
보이는 텍스트
Status
Empty
Assignee
Empty
Ip
Empty
Device
Empty
Started at
Submitted at
Completion time
Empty
Text
Empty
Rating
Empty
Checkbox
Checkbox
Select
Empty
Text
Empty
File
Empty
Date
Empty
I remember the times when I was completely sold on the idea of the Repository pattern. I wrote about it, talked about it in meetups, and used it extensively in projects, especially when I was diving deep into Domain-Driven Design (DDD) and layered architectures. The core principle was always the same: keep the domain layer free of data concerns and push data interactions out to dedicated repositories. It sounded great in theory and worked well for a while in practice.
But along the way, I found myself spending more and more time mapping data between different layers — database entities to domain objects, domain objects to DTOs, and so on — without seeing much real value, especially for typical line-of-business applications. My “Aha!” moment came when I realized how much simpler things could be if I just cut out the middleman, so to speak.
1
Shrooman
I’m a social psychologist, so I’m interested primarily in the situational and contextual factors that drive human behavior. When you’re seeking to
See latest comments
