this post was submitted on 24 Jul 2026
35 points (100.0% liked)

Programming

27863 readers
557 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 3 years ago
MODERATORS
 

cross-posted from: https://programming.dev/post/54023908

Hi!

I've never read any of Uncle Bob's books. But I have taken interest in "Clean Architecture" as it seems like a good solution to make mid to large sized projects simple to understand and maintain.

I think MVC gets too much coupling and fails at larger projects, same with n-tier. But I'm not sure about anything right now (software design is a very complicated problem after all).

So I was wondering if you friends who have used Clean Architecture in production can share your knowledge and experience with me about this design?

Is it actually good and worth investing in?

Footnote:

I'm especially weighing this architecture because Uncle Bob's writings are really hit and miss. I don't see him as a master or guru so I take everything he says with a grain of salt.

you are viewing a single comment's thread
view the rest of the comments
[–] AlteredEgo@lemmy.ml 0 points 3 days ago* (last edited 3 days ago)

I've become disillusioned with such approaches because coders tend to loose themselves in the aesthetics of ideas and architectures. And that can lead to high verbosity for something that could be much simpler, which then makes code harder to read and browse. Basically I doubt that complex software problem can actually be planned and designed without programming them first. That could well be just my own limits.

So today I prefer a bit of a "return to monke" C-style procedural approach and don't even like OOP anymore.

I do wonder if there is a more formal framework for natural language (AI prompt) programming. Maybe LLMs could be used as an actual research tool to explore a high number of different architectures of well defined programs, and then compare them. Like have the same app programmed in hundreds of different languages, designs and idioms, and then compare them to get the answer to your question.