257m@lemmy.ml to Programming@programming.dev · 1 year agoWhat are your programming hot takes?message-squaremessage-square1056fedilinkarrow-up1344arrow-down114
arrow-up1330arrow-down1message-squareWhat are your programming hot takes?257m@lemmy.ml to Programming@programming.dev · 1 year agomessage-square1056fedilink
minus-squarePatchworkHorse@lemmy.worldlinkfedilinkarrow-up10·1 year agoDoing this is a hot take, but “clean architecture” is a joke. My company is obsessed with it.
minus-squarescubbo@lemmy.mllinkfedilinkarrow-up2·1 year 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-squarePatchworkHorse@lemmy.worldlinkfedilinkarrow-up1·1 year 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.
minus-squareNoXzema@lemmynsfw.comlinkfedilinkEnglisharrow-up1·1 year 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.
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.
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.