What are your programming hot takes?257m@lemmy.ml to Programming@programming.dev – 332 points – 11 months ago872Post a CommentPreviewYou are viewing a single commentView all commentsDoing this is a hot take, but "clean architecture" is a joke. My company is obsessed with it.I remember having a lot of doubts/criticisms of the book when I read it, but that was a long-ass time ago and I've forgotten it - what do you dislike?Off the top of my head... Too many layers of abstraction Multiple copies of the same model (entities, domain objects, models, DTOs, etc) Ours is a .NET6 solution, for what it's worth. The solution itself has a few flaws, so that might be tainting my opinion a bit.
Doing this is a hot take, but "clean architecture" is a joke. My company is obsessed with it.I remember having a lot of doubts/criticisms of the book when I read it, but that was a long-ass time ago and I've forgotten it - what do you dislike?Off the top of my head... Too many layers of abstraction Multiple copies of the same model (entities, domain objects, models, DTOs, etc) Ours is a .NET6 solution, for what it's worth. The solution itself has a few flaws, so that might be tainting my opinion a bit.
I remember having a lot of doubts/criticisms of the book when I read it, but that was a long-ass time ago and I've forgotten it - what do you dislike?Off the top of my head... Too many layers of abstraction Multiple copies of the same model (entities, domain objects, models, DTOs, etc) Ours is a .NET6 solution, for what it's worth. The solution itself has a few flaws, so that might be tainting my opinion a bit.
Off the top of my head... Too many layers of abstraction Multiple copies of the same model (entities, domain objects, models, DTOs, etc) Ours is a .NET6 solution, for what it's worth. The solution itself has a few flaws, so that might be tainting my opinion a bit.
Doing this is a hot take, but "clean architecture" is a joke.
My company is obsessed with it.
I remember having a lot of doubts/criticisms of the book when I read it, but that was a long-ass time ago and I've forgotten it - what do you dislike?
Off the top of my head...
Ours is a .NET6 solution, for what it's worth. The solution itself has a few flaws, so that might be tainting my opinion a bit.