this post was submitted on 01 Sep 2023
338 points (96.2% liked)

Programming

17553 readers
329 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Patchwork@lemmy.world 10 points 1 year ago (1 children)

Doing this is a hot take, but "clean architecture" is a joke.

My company is obsessed with it.

[–] scubbo@lemmy.ml 2 points 1 year ago (2 children)

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?

[–] NoXzema@lemmynsfw.com 1 points 1 year ago

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.

[–] Patchwork@lemmy.world 1 points 1 year ago

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.