home.social

#cleanarchitecture — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cleanarchitecture, aggregated by home.social.

fetched live
  1. 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: javapro.io/2026/03/17/ai-witho
    #LangChain4j #Quarkus QuarkusIO #LLM

  2. 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: javapro.io/2026/03/17/ai-witho
    #LangChain4j #Quarkus QuarkusIO #LLM

  3. 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: javapro.io/2026/03/17/ai-witho

  4. 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: javapro.io/2026/03/17/ai-witho

  5. 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: javapro.io/de/von-spaghetti-zu

    #CleanArchitecture #DDD @ArchUnit

  6. 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: javapro.io/de/von-spaghetti-zu

    #CleanArchitecture #DDD @ArchUnit

  7. 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: javapro.io/2026/03/17/ai-witho

  8. 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: javapro.io/2026/03/17/ai-witho

  9. 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: meetup.com/barner-js-talks/eve

    #typescript #nitro #cleanarchitecture #bern #meetup

  10. 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: javapro.io/de/von-spaghetti-zu

    #CleanArchitecture #DDD @ArchUnit

  11. 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: javapro.io/de/von-spaghetti-zu

    #CleanArchitecture #DDD @ArchUnit

  12. 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.

    ripenapps.com/blog/how-to-use-

    #Flutter #FlutterBLoC #CleanArchitecture #FlutterBLoCArchitecture #FlutterAppDevelopment

  13. 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

  14. 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.

    Leia em:
    bolha.blog/riverfount/nomear-p

    Compartilhe boas práticas e vamos conversar sobre código que se explica sozinho. #Python #CleanArchitecture #PEP8 #BoasPráticas #EngenhariaDeSoftware

  15. 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.

    Leia em:
    bolha.blog/riverfount/nomear-p

    Compartilhe boas práticas e vamos conversar sobre código que se explica sozinho. #Python #CleanArchitecture #PEP8 #BoasPráticas #EngenhariaDeSoftware

  16. 🏗️ Clean Architecture organiza tu código en capas independientes para crear software escalable y fácil de mantener. Aprende sus principios y transforma tus proyectos 💻✨

    Lee más 👉 soloingenieria.org/ingenieria-

    #CleanArchitecture #DesarrolloDeSoftware #IngenieríaDeSistemas #Programación

  17. 🔥 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: live.symfony.com/2026-online-j

    #SymfonyOnline #Symfony #PHP #Workshop #CleanArchitecture #WebDev

  18. 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::

    bolha.blog/riverfount/arquitet

    #Python #ArquiteturaHexagonal #CleanArchitecture #DevLife #TDD #Microservices #FastAPI #SoftwareEngineering

  19. 🚀 New chapter added to the Guile Hacker Handbook 🚀

    This is a book to learn #Guile in a #TestDrivenLearning style 👽

    ⬇️ Check it out ⬇️
    🇫🇷 🇬🇧 🇮🇹 jeko.frama.io

    Contrary to what I have said previously, this new chapter is about having some fun using the use-cases in the REPL.

    #gnu #scheme #tdd #cleanCode #cleanArchitecture

  20. 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:

    pybit.es/articles/typing-proto

  21. 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. hackernoon.com/clean-architect #cleanarchitecture

  22. 🚀 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 👉 aleahim.com/ExtremePackaging

    #Swift #iOSDev #macOS #SwiftPM #CleanArchitecture #OpenSource #SwiftLang

  23. 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.

    jdriven.com/blog/2025/10/Vibe-

    New blog by @erikj

    #jdriven #java #ai #cleanarchitecture

  24. 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