257m to [email protected] • 10 months agoWhat are your programming hot takes?message-square804fedilinkarrow-up1340
arrow-up1326message-squareWhat are your programming hot takes?257m to [email protected] • 10 months agomessage-square804fedilink
minus-squarePatchworkHorselinkfedilink10•10 months agoDoing this is a hot take, but “clean architecture” is a joke. My company is obsessed with it.
minus-square@[email protected]linkfedilink2•10 months agoI 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?
minus-square@NoXzemalinkEnglish1•10 months agoI’ve seen it get a lot of hate revently. In my experience, it’s mostly been from people upset they had to refactor their 400 line function or write unit tests.
minus-squarePatchworkHorselinkfedilink1•10 months agoOff 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?
I’ve seen it get a lot of hate revently. In my experience, it’s mostly been from people upset they had to refactor their 400 line function or write unit tests.
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.