#cleanarchitecture — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cleanarchitecture, aggregated by home.social.
-
Solid and Clean Code never felt solid or clean to me
https://devz.cl/posts/solid-never-felt-solid/
#HackerNews #solidcode #cleanarchitecture #programming #bestpractices #developerinsight
-
Solid and Clean Code never felt solid or clean to me
https://devz.cl/posts/solid-never-felt-solid/
#HackerNews #solidcode #cleanarchitecture #programming #bestpractices #developerinsight
-
Most #AI prototypes work. Until the next model update breaks half the system. Lutske de Leeuw & Maarten Vandeperre show how #CleanArchitecture, ports & adapters keep AI integrations from becoming spaghetti code.
Read: https://javapro.io/2026/03/17/ai-without-spaghetti-clean-architecture-in-the-age-of-ai/
#LangChain4j #Quarkus QuarkusIO #LLM -
Most #AI prototypes work. Until the next model update breaks half the system. Lutske de Leeuw & Maarten Vandeperre show how #CleanArchitecture, ports & adapters keep AI integrations from becoming spaghetti code.
Read: https://javapro.io/2026/03/17/ai-without-spaghetti-clean-architecture-in-the-age-of-ai/
#LangChain4j #Quarkus QuarkusIO #LLM -
AI projects often start clean… then become architectural spaghetti. Prompts everywhere. Model calls hidden in services. Refactoring becomes painful.
Lutske de Leeuw & Maarten Vandeperre show how #CleanArchitecture keeps #AI systems maintainable.Read: https://javapro.io/2026/03/17/ai-without-spaghetti-clean-architecture-in-the-age-of-ai/
-
What is CQRS and how might it fit into Clean Architecture?
Read more here:
https://bgh.st/odnuuk -
How does MediatR fit into Clean Architecture?
Read more here:
https://bgh.st/rim1vi -
What's the Unit of Work pattern?
Read more here:
https://bgh.st/shxuqd -
【図解】2層構造→MVC→レイヤード→ヘキサゴナル→クリーンアーキテクチャ：設計思想の進化を一気に理解する
https://qiita.com/yut-nagase/items/21703af242e7ebfc37a9?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【図解】2層構造→MVC→レイヤード→ヘキサゴナル→クリーンアーキテクチャ：設計思想の進化を一気に理解する
https://qiita.com/yut-nagase/items/21703af242e7ebfc37a9?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Spaghetti-Code, Lasagne-Architektur, anämische Domänenmodelle: @quiquemmonte sammelt die zentralen Anti-Patterns & zeigt, wie hexagonale Architektur daraus einen testbaren #Java-Kern macht.
Baue Systeme, die überleben: https://javapro.io/de/von-spaghetti-zu-hexagonen-ein-praktischer-leitfaden-zur-sauberen-java-architektur/
#CleanArchitecture #DDD @ArchUnit
-
AI projects often start clean… then become architectural spaghetti. Prompts everywhere. Model calls hidden in services. Refactoring becomes painful.
Lutske de Leeuw & Maarten Vandeperre show how #CleanArchitecture keeps #AI systems maintainable.Read: https://javapro.io/2026/03/17/ai-without-spaghetti-clean-architecture-in-the-age-of-ai/
-
「テストコードは仕様書になる」クリーンアーキテクチャの各層で「振る舞い」をテストするべき理由
https://qiita.com/takishun_schoo/items/5b5fd06d488119daa899?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Am kommenden Dienstag, 3 März, werde ich an den BärnerJS Talks #26-1 einen Vortrag zum Thema «Moderne TypeScript-Backends mit Nitro & Clean Architecture» halten. Komm vorbei, wenn du Lust hast. Es würde mich freuen bei Pizza & Bier zu plaudern.
Details und Anmeldung hier: https://www.meetup.com/barner-js-talks/events/312500742/
-
Spaghetti-Code, Lasagne-Architektur, anämische Domänenmodelle: @quiquemmonte sammelt die zentralen Anti-Patterns & zeigt, wie hexagonale Architektur daraus einen testbaren #Java-Kern macht.
Baue Systeme, die überleben: https://javapro.io/de/von-spaghetti-zu-hexagonen-ein-praktischer-leitfaden-zur-sauberen-java-architektur/
#CleanArchitecture #DDD @ArchUnit
-
Building a Flutter app that feels fast, stable, and scalable starts with the right architecture.
Flutter BLoC Architecture brings structure to state management and clarity to complex app logic. See how high-performance Flutter apps handle data, UI, and business logic without friction.
A must-read guide for teams aiming for speed, control, and long-term app growth.https://ripenapps.com/blog/how-to-use-flutter-bloc-architecture-to-build-high-performance-apps/
#Flutter #FlutterBLoC #CleanArchitecture #FlutterBLoCArchitecture #FlutterAppDevelopment
-
En VS Code 1.109, esto escala de locos usando Agent Sessions y sub-agentes en paralelo para cada capa (Domain, Adapters, UI). Ahorras dinero, reduces iteraciones fallidas y mantienes el control técnico. Primero se piensa, luego se paga. 💻 #CleanArchitecture #Claude #VSCode #Programming
-
【初心者向け】フォルダ構成で迷わないための設計入門 〜「業務」と「役割」で分けるだけ〜
https://qiita.com/hoshi-gmoconnect/items/018889761cf6e201cb9f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【初心者向け】フォルダ構成で迷わないための設計入門 〜「業務」と「役割」で分けるだけ〜
https://qiita.com/hoshi-gmoconnect/items/018889761cf6e201cb9f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Nomear variáveis é um ato de design, não de estética.
No meu novo artigo, mostro como combinar Clean Architecture e PEP 8 para escrever nomes claros, concisos e inteligentes em Python — com exemplos reais e um mini refactor no final.
Compartilhe boas práticas e vamos conversar sobre código que se explica sozinho. #Python #CleanArchitecture #PEP8 #BoasPráticas #EngenhariaDeSoftware
-
Nomear variáveis é um ato de design, não de estética.
No meu novo artigo, mostro como combinar Clean Architecture e PEP 8 para escrever nomes claros, concisos e inteligentes em Python — com exemplos reais e um mini refactor no final.
Compartilhe boas práticas e vamos conversar sobre código que se explica sozinho. #Python #CleanArchitecture #PEP8 #BoasPráticas #EngenhariaDeSoftware
-
Nouveau sur le blog WanadevDigital 📖
Mohamed Senoussi, développeur Full Stack, partage son retour sur le pattern #CQRS avec #SymfonyMessenger pour mieux structurer des applications #Symfony complexes, à travers un exemple concret.
👉 https://www.wanadevdigital.fr/356-cqrs-avec-symfony-messenger-domptez-la-complexite-de-vos-applications/?mtm_campaign=Article%20Mohamed%20CQRS&mtm_kwd=Piaille -
Nouveau sur le blog WanadevDigital 📖
Mohamed Senoussi, développeur Full Stack, partage son retour sur le pattern #CQRS avec #SymfonyMessenger pour mieux structurer des applications #Symfony complexes, à travers un exemple concret.
👉 https://www.wanadevdigital.fr/356-cqrs-avec-symfony-messenger-domptez-la-complexite-de-vos-applications/?mtm_campaign=Article%20Mohamed%20CQRS&mtm_kwd=Piaille -
🔥 New SymfonyOnline Jan 2026 workshop!
Damian Dziaduch leads “Refactoring Towards Clean Architecture” 🏗️
A hands-on session to transform your Symfony projects — cleaner, scalable, and resilient code 💻✨📅 Jan 20, 2026 — 9:00 AM CET
🌐 Fully online👉 Join the workshop: https://live.symfony.com/2026-online-january/workshop
#SymfonyOnline #Symfony #PHP #Workshop #CleanArchitecture #WebDev
-
A nice history about how and why #cleanarchitecture came about at the start of this talk
-
What is CQRS and how might it fit into Clean Architecture?
Read more here:
https://www.devleader.ca/2024/02/07/cqrs-pattern-in-c-and-clean-architecture-a-simplified-beginners-guide/ -
How does MediatR fit into Clean Architecture?
Read more here:
https://www.devleader.ca/2024/02/06/c-clean-architecture-with-mediatr-how-to-build-for-flexibility/ -
What's the Unit of Work pattern?
Read more here:
https://www.devleader.ca/2024/02/05/unit-of-work-pattern-in-c-for-clean-architecture-what-you-need-to-know/ -
Quer transformar seu projeto Python em uma aplicação robusta, testável e facilmente escalável?
🚀 Conheça a arquitetura hexagonal, que isola sua lógica de negócio e permite mudar bancos, APIs e frameworks sem stress!
🧩 Quer saber como começar e refatorar seu código passo a passo?
Leia meu novo artigo sobre Arquitetura Hexagonal em Python — dicas práticas, vantagens e desvantagens::
#Python #ArquiteturaHexagonal #CleanArchitecture #DevLife #TDD #Microservices #FastAPI #SoftwareEngineering
-
Quer transformar seu projeto Python em uma aplicação robusta, testável e facilmente escalável?
🚀 Conheça a arquitetura hexagonal, que isola sua lógica de negócio e permite mudar bancos, APIs e frameworks sem stress!
🧩 Quer saber como começar e refatorar seu código passo a passo?
Leia meu novo artigo sobre Arquitetura Hexagonal em Python — dicas práticas, vantagens e desvantagens::
#Python #ArquiteturaHexagonal #CleanArchitecture #DevLife #TDD #Microservices #FastAPI #SoftwareEngineering
-
🚀 New chapter added to the Guile Hacker Handbook 🚀
This is a book to learn #Guile in a #TestDrivenLearning style 👽
⬇️ Check it out ⬇️
🇫🇷 🇬🇧 🇮🇹 https://jeko.frama.ioContrary to what I have said previously, this new chapter is about having some fun using the use-cases in the REPL.
-
The #CleanArchitecture I Wish Someone Had Explained to Me
https://medium.com/@rafael-22/the-clean-architecture-i-wish-someone-had-explained-to-me-dcc1572dbeac
-
You can also model the repository interface with `typing.Protocol`, so any implementation (SQL, CSV, API, in-memory) just has to “duck type” to that contract:
-
Clean Architecture made practical. Stop drawing circles and see how to apply the layers in a real mobile projects, explained by a dev for devs. https://hackernoon.com/clean-architecture-how-to-keep-your-codebase-scalable-without-overengineering #cleanarchitecture
-
🚀 New write-up: Extreme Packaging — my approach to modular Swift architecture
I’ve been experimenting with project structures where *every responsibility is its own Swift Package*.
The result: cleaner boundaries, faster builds, and reusable code between iOS & macOS apps.Full article 👉 https://aleahim.com/ExtremePackaging
#Swift #iOSDev #macOS #SwiftPM #CleanArchitecture #OpenSource #SwiftLang
-
You’re coding late at night. The lights are low. Your favorite playlist is playing, maybe something only you would call “focus music.” Your IDE is set to a theme that feels just right. You’re not rushing. You’re not distracted. You’re in the zone.
This is vibe coding.
https://jdriven.com/blog/2025/10/Vibe-Coding-A-Hype-or-a-Vibe
New blog by @erikj
-
JUnit 6 broke 50 repos. I’m delighted.
If a dependency bump can shatter your stack, you don't need fewer updates. You need better tests.
I maintain 50+ OSS repos as one human. I don't babysit them. I automated everything, including updates and minor releases. Many repos haven't been touched in 6 years. AS now JUnit 6 rolled in, a chunk failed. Perfect.
Why perfect? Because failure is a signal, not a disaster. Good tests mean breakage never escapes. I've had repos fail on a Java date parser change. Beautiful. I saw it before release, fixed it, moved on. During Log4Shell and Spring4Shell I didn't panic. I just waited for the next update. That's what behaviour tests are for. And no, they are not slow. If your tests crawl, your design does too.
I trust code I write. I do not trust magic. I remove convenience glue that silently rots:
I don't need MultiValueMap when Map<List> is clearer.
I don't need StringUtils.isEmpty when a simple null or empty check is obvious.
I don't need annotations that smuggle in half a framework.Every extra library is a future liability: CVEs, Licences, Security, Data Privacy, Performance, breaking changes, mental overhead. Use them to start, then delete them to last. Fewer moving parts mean fewer ways to die.
After 6 years my micro systems still boot in micro seconds, still read clean, still behave. CI pipelines aged, sure, but the code stayed boring. Boring is freedom. Quiet, peaceful, done.
If your stack cannot auto-update without heart palpitations, the problem isn't updates. It's architecture.
Principles I ship by
Automate updates and everything else I can. Let tests be the gate, not fear.
Push behaviour tests to the edges. If it's slow, refactor until it isn't.
Prefer primitives and standard libs. Delete decorative wrappers.
Design for micro systems, not micro monoliths. Start fast, stay fast.
Fewer tools, fewer surprises, fewer nights on fire.Congratulations. The system failed safely. After fix, you may proceed to do literally anything else with your life.
#java #junit #testing #oss #automation #developerexperience #simplicity #minimalism #microservices #security #log4shell #spring4shell #cleanarchitecture
-
JUnit 6 broke 50 repos. I’m delighted.
If a dependency bump can shatter your stack, you don't need fewer updates. You need better tests.
I maintain 50+ OSS repos as one human. I don't babysit them. I automated everything, including updates and minor releases. Many repos haven't been touched in 6 years. AS now JUnit 6 rolled in, a chunk failed. Perfect.
Why perfect? Because failure is a signal, not a disaster. Good tests mean breakage never escapes. I've had repos fail on a Java date parser change. Beautiful. I saw it before release, fixed it, moved on. During Log4Shell and Spring4Shell I didn't panic. I just waited for the next update. That's what behaviour tests are for. And no, they are not slow. If your tests crawl, your design does too.
I trust code I write. I do not trust magic. I remove convenience glue that silently rots:
I don't need MultiValueMap when Map<List> is clearer.
I don't need StringUtils.isEmpty when a simple null or empty check is obvious.
I don't need annotations that smuggle in half a framework.Every extra library is a future liability: CVEs, Licences, Security, Data Privacy, Performance, breaking changes, mental overhead. Use them to start, then delete them to last. Fewer moving parts mean fewer ways to die.
After 6 years my micro systems still boot in micro seconds, still read clean, still behave. CI pipelines aged, sure, but the code stayed boring. Boring is freedom. Quiet, peaceful, done.
If your stack cannot auto-update without heart palpitations, the problem isn't updates. It's architecture.
Principles I ship by
Automate updates and everything else I can. Let tests be the gate, not fear.
Push behaviour tests to the edges. If it's slow, refactor until it isn't.
Prefer primitives and standard libs. Delete decorative wrappers.
Design for micro systems, not micro monoliths. Start fast, stay fast.
Fewer tools, fewer surprises, fewer nights on fire.Congratulations. The system failed safely. After fix, you may proceed to do literally anything else with your life.
#java #junit #testing #oss #automation #developerexperience #simplicity #minimalism #microservices #security #log4shell #spring4shell #cleanarchitecture
-
Ungetrennte REST-Calls zerstören jede saubere Architektur – blockierende Aufrufe, Timeouts, unkontrollierte Fehler. @svenruppert setzt in #Java auf klare Adapter, Typsicherheit & Resilienz.
Jetzt direkt nachlesen: https://javapro.io/de/mit-vaadin-flow-rest-endpoints-in-core-java-konsumieren/
#CleanArchitecture #CoreJava @Vaadin
-
Ungetrennte REST-Calls zerstören jede saubere Architektur – blockierende Aufrufe, Timeouts, unkontrollierte Fehler. @svenruppert setzt in #Java auf klare Adapter, Typsicherheit & Resilienz.
Jetzt direkt nachlesen: https://javapro.io/de/mit-vaadin-flow-rest-endpoints-in-core-java-konsumieren/
#CleanArchitecture #CoreJava @Vaadin
-
Robert C. Martin - Clean Architecture
Po “Clean Architecture” Roberta C. Martina sięgnąłem z powodów zawodowych - pracuję obecnie przy przepisywaniu aplikacji w Pythonie zgodnie z założeniami tej architektury i uznałem, że warto lepiej zrozumieć, na czym ona właściwie polega.
Link do wpisu 🔗
https://xiegozbior.pl/zajawki/2025/07/22/zajawka-clean-architecture.html#CleanArchitecture #RobertCMartin #UncleBob #bookstodon #bookstagram #fediksiazki
@[email protected] @[email protected]Pełny wpis w wątku poniżej! ⬇️
-
When Product Met Tech
A Love Story Written in Stack TracesOnce upon a sprint, Product declared:
“This feature is simple. Just a button. Users will love it.”Tech stared into the void, which suspiciously resembled the legacy auth module, the monolithic database, and a CI pipeline held together by dreams and duct tape.
What Product saw:
* A done state.
* An Epic.
* An OKR.
* A trophy for “delivering customer value”.
* Ready to post on LinkedIn to shineWhat Tech saw:
* 12 layers of hidden complexity.
* No time to refactor.
* That code lines from 20 years ago, that nobody dares to touch.
* Development slows down
* One feature created, other feature breaks
* Existential dread.The tragic part?
We're both building the same ship.
One thinks it's a cruise liner. The other knows it's a submarine with duct-taped bulkheads.Product focuses on "what".
Tech is bound by "how", and worse, by what came before.
Good architecture isn't visible until it's absent. Then everything burns. Slowly. While everyone smiles in retros.Want to ship faster?
Make space for architecture.
Treat your tech leads like product owners of logic.
The best technologies and tools doesn't help when bad architecture slows and pulls your product down into the quicksand. Every step you take gets harder.#CleanArchitecture #ProductDelivery #productdevelopment #Productivity #programming #coding #projectmanagement
-
When Product Met Tech
A Love Story Written in Stack TracesOnce upon a sprint, Product declared:
“This feature is simple. Just a button. Users will love it.”Tech stared into the void, which suspiciously resembled the legacy auth module, the monolithic database, and a CI pipeline held together by dreams and duct tape.
What Product saw:
* A done state.
* An Epic.
* An OKR.
* A trophy for “delivering customer value”.
* Ready to post on LinkedIn to shineWhat Tech saw:
* 12 layers of hidden complexity.
* No time to refactor.
* That code lines from 20 years ago, that nobody dares to touch.
* Development slows down
* One feature created, other feature breaks
* Existential dread.The tragic part?
We're both building the same ship.
One thinks it's a cruise liner. The other knows it's a submarine with duct-taped bulkheads.Product focuses on "what".
Tech is bound by "how", and worse, by what came before.
Good architecture isn't visible until it's absent. Then everything burns. Slowly. While everyone smiles in retros.Want to ship faster?
Make space for architecture.
Treat your tech leads like product owners of logic.
The best technologies and tools doesn't help when bad architecture slows and pulls your product down into the quicksand. Every step you take gets harder.#CleanArchitecture #ProductDelivery #productdevelopment #Productivity #programming #coding #projectmanagement
-
Nobody want to be a shitty programmer. The question is: Do you do anything not to not be one?
Reading blogs or social media and watching YouTube videos is fun. After them, your code may be a little better, of course. But you need a lot. You need to study! Read good books and study the code of other programmers, for example. Maybe work with a new language, architectures and paradigms. You need break the routine.
If you know Object-oriented programming, you learn functional programming.
If you know Model-View-Controller, you learn Model-View-ViewModel.
If you don't know anything about architectures, you learn Clean Architecture, Hexagonal Architecture, etc.
If you know Python, you learn Ruby or Go.
If you know Clojure or Lisp... you don't need to learn anything else. You are already a good programmer. Just kidding. You can learn Elixir or Scala.
Be a good programmer my friend.
#Programmin #OOP #FunctionalProgramming #MVC #MVVM #CleanArchitecture #HexagonalArchitecture #Python #RubyLang #Golang #Clojure #Lisp #ElixirLang #Scala -
Nobody want to be a shitty programmer. The question is: Do you do anything not to not be one?
Reading blogs or social media and watching YouTube videos is fun. After them, your code may be a little better, of course. But you need a lot. You need to study! Read good books and study the code of other programmers, for example. Maybe work with a new language, architectures and paradigms. You need break the routine.
If you know Object-oriented programming, you learn functional programming.
If you know Model-View-Controller, you learn Model-View-ViewModel.
If you don't know anything about architectures, you learn Clean Architecture, Hexagonal Architecture, etc.
If you know Python, you learn Ruby or Go.
If you know Clojure or Lisp... you don't need to learn anything else. You are already a good programmer. Just kidding. You can learn Elixir or Scala.
Be a good programmer my friend.
#Programmin #OOP #FunctionalProgramming #MVC #MVVM #CleanArchitecture #HexagonalArchitecture #Python #RubyLang #Golang #Clojure #Lisp #ElixirLang #Scala -
True Engineering Isn't about using tools.
It's in the questions.
Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.
Do you know what that smart-syntax language is doing under the hood?
Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
Do you know what your "schema-less" database sacrifices when concurrency climbs?
Do you know how many runtime hacks exist to make your "native" build work seamlessly?
Do you know how your framework manages threads… or fails to?Many don't. And that's the problem.
We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.
If you're not asking, "What isn’t being said?"
You're not engineering. You're just believing and praying.
AI is a perfect example of many people which hype it but don't understand it.
You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.#TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech