home.social

#cleancode — Public Fediverse posts

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

fetched live
  1. A language feature is only useful if it makes the code easier to maintain. Clever code may impress today’s reviewer. Simple code helps next year’s team.

    Read in “Effective Rust” by David Drysdale.
    #RustLang #CleanCode #Maintainability

    Photo by Florian Olivo on Unsplash

  2. Long if/else chains, repeated checks, unnecessary casts—classic #Java overhead. #Java25 adds #PatternMatching in switch, #RecordPatterns & guards, reducing boilerplate & improving type safety.
    Mihaela Gheorghe-Roman explains: javapro.io/2026/04/28/pattern-

    #CleanCode #JDK25 @openjdk

  3. Long if/else chains, repeated checks, unnecessary casts—classic #Java overhead. #Java25 adds #PatternMatching in switch, #RecordPatterns & guards, reducing boilerplate & improving type safety.
    Mihaela Gheorghe-Roman explains: javapro.io/2026/04/28/pattern-

    #CleanCode #JDK25 @openjdk

  4. “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” – Antoine de Saint-Exupéry

    Good architecture often emerges through simplification rather than expansion. Every service, dependency, and abstraction introduces maintenance costs. Removing complexity can create more value than adding another feature.

    💬 What was the most valuable thing you removed from a system?

    #SoftwareArchitecture #CleanCode #CodeQuality #DevThinking

  5. Durch Dinge wie CleanCode oder dem KISS-Prinzip versuchen wir unseren Code möglichst verständlich zu halten. Wir benennen Methoden nachdem was sie tun, wissen, dass eine Methode auch nur eine Sache machen soll und auch die Benamung unserer Variablen sind sprechend. Wer das alles konsequent berück

    magicmarcy.de/java-doc-–-es-is

    #JavaDoc #Dokumentation #Kommunikation #CleanCode #KISS #author #Git #Git_Blame

  6. On my tech reading stack 📚
    -> more + +

    • Building Secure and Reliable Systems
    • Design Patterns and Best Practices in Rust
    • Clean Code

    What are you reading this weekend?

  7. On my tech reading stack 📚
    -> more #security + #rust + #cleancode

    • Building Secure and Reliable Systems
    • Design Patterns and Best Practices in Rust
    • Clean Code

    What are you reading this weekend?

  8. Are GoF design patterns becoming obsolete? Modern Java has replaced parts of Factory, Strategy, Visitor & more with features like lambdas, records, sealed interfaces and pattern matching. Learn with Andreas Jürgensen when classic design patterns still add value—and when modern Java already provides the better solution. Read now: javapro.io/2026/07/23/are-clas

    #Java #DesignPatterns #SoftwareArchitecture #CleanCode

  9. Are GoF design patterns becoming obsolete? Modern Java has replaced parts of Factory, Strategy, Visitor & more with features like lambdas, records, sealed interfaces and pattern matching. Learn with Andreas Jürgensen when classic design patterns still add value—and when modern Java already provides the better solution. Read now: javapro.io/2026/07/23/are-clas

    #Java #DesignPatterns #SoftwareArchitecture #CleanCode

  10. Durch Dinge wie CleanCode oder dem KISS-Prinzip versuchen wir unseren Code möglichst verständlich zu halten. Wir benennen Methoden nachdem was sie tun, wissen, dass eine Methode auch nur eine Sache machen soll und auch die Benamung unserer Variablen sind sprechend. Wer das alles konsequent berück

    magicmarcy.de/java-doc-–-es-is

    #JavaDoc #Dokumentation #Kommunikation #CleanCode #KISS #author #Git #Git_Blame

  11. Learn everything you need to know about Clean Code via these 309 free HackerNoon blog posts. hackernoon.com/309-blog-posts- #cleancode

  12. Learn everything you need to know about Clean Code via these 309 free HackerNoon blog posts. hackernoon.com/309-blog-posts- #cleancode

  13. Always define a clear role at the top of every skill file so you know whose perspective drives the execution. hackernoon.com/ai-coding-tip-0 #cleancode

  14. Always define a clear role at the top of every skill file so you know whose perspective drives the execution. hackernoon.com/ai-coding-tip-0 #cleancode

  15. Writing code gets cheaper with #AI. Understanding architecture does not. That’s why teams drown in systems nobody fully understands. Sven Reinck shows how dependency visualization can make large codebases navigable again: javapro.io/2026/06/10/beyond-u

    #CleanCode #Java @FLUXparticleCOM

  16. Writing code gets cheaper with #AI. Understanding architecture does not. That’s why teams drown in systems nobody fully understands. Sven Reinck shows how dependency visualization can make large codebases navigable again: javapro.io/2026/06/10/beyond-u

    #CleanCode #Java @FLUXparticleCOM

  17. Vor LLMs refactorten Entwickler doppelt so oft, wie sie Code kopierten. Heute kopieren sie 5x öfter, als sie refactoren.

    LLM liefert den Happy Path und schließt das Ticket. Aufräumen, Konsolidieren, Altlasten pflegen bleibt liegen. Langzeit-Wartung: −74 % seit 2023. Das Tempo ist echt. Die Rechnung kommt in Jahr 3.

    Source: gitclear.com/the_ai_code_quali

    #KI #AI #LLM #cleancode

  18. Vor LLMs refactorten Entwickler doppelt so oft, wie sie Code kopierten. Heute kopieren sie 5x öfter, als sie refactoren.

    LLM liefert den Happy Path und schließt das Ticket. Aufräumen, Konsolidieren, Altlasten pflegen bleibt liegen. Langzeit-Wartung: −74 % seit 2023. Das Tempo ist echt. Die Rechnung kommt in Jahr 3.

    Source: gitclear.com/the_ai_code_quali

    #KI #AI #LLM #cleancode

  19. Favour composition over inheritance. Instead of deep class hierarchies, build objects by combining smaller, focused components. Easier to test, modify, and reason about. #DesignPatterns #CleanCode

  20. Favour composition over inheritance. Instead of deep class hierarchies, build objects by combining smaller, focused components. Easier to test, modify, and reason about. #DesignPatterns #CleanCode

  21. The Single Responsibility Principle isn't just about classes - apply it to functions, modules, and even variables. Each should have one clear reason to change. Makes debugging and testing much easier. #CleanCode

  22. The Single Responsibility Principle isn't just about classes - apply it to functions, modules, and even variables. Each should have one clear reason to change. Makes debugging and testing much easier. #CleanCode

  23. 🚨 Breaking news: "Coder admits popular coding principles are not magical!" 🪄 Daniel, the self-taught programming oracle, discovers Clean Code is just "advice" from those pesky senior engineers. 📚 Oh, the audacity! 😂
    devz.cl/posts/solid-never-felt #BreakingNews #CoderConfession #CleanCode #SoftwareDevelopment #TechHumor #SeniorEngineers #HackerNews #ngated

  24. 🚨 Breaking news: "Coder admits popular coding principles are not magical!" 🪄 Daniel, the self-taught programming oracle, discovers Clean Code is just "advice" from those pesky senior engineers. 📚 Oh, the audacity! 😂
    devz.cl/posts/solid-never-felt #BreakingNews #CoderConfession #CleanCode #SoftwareDevelopment #TechHumor #SeniorEngineers #HackerNews #ngated

  25. Less boilerplate sounds great. But are you trading it for hidden complexity? #PatternMatching adds power—and surprising pitfalls. @cayhorstmann dives into where it actually pays off.

    Sharpen your mental model before production: javapro.io/2026/03/24/effectiv

    #Java #JVM #CleanCode

  26. Less boilerplate sounds great. But are you trading it for hidden complexity? #PatternMatching adds power—and surprising pitfalls. @cayhorstmann dives into where it actually pays off.

    Sharpen your mental model before production: javapro.io/2026/03/24/effectiv

    #Java #JVM #CleanCode

  27. Viele Teams verlieren Zeit, weil Daten überall validiert werden. Birgit Kratz analysiert, wie du Validierung an die Grenzen legst & illegale Zustände verhinderst. Ergebnis: weniger Runtime-Fehler. Sieh dir die Umsetzung im Code an: javapro.io/de/datenorientierte
    #Java #CleanCode #DevOps

  28. Viele Teams verlieren Zeit, weil Daten überall validiert werden. Birgit Kratz analysiert, wie du Validierung an die Grenzen legst & illegale Zustände verhinderst. Ergebnis: weniger Runtime-Fehler. Sieh dir die Umsetzung im Code an: javapro.io/de/datenorientierte
    #Java #CleanCode #DevOps

  29. Guten Morgen! ☕

    Kleine Erinnerung an alle, die heute „mal eben schnell“ ein Script schreiben wollen: Dein zukünftiges Ich liest diesen Code in 6 Monaten und wird dich verfluchen.

    Schreib einen Kommentar. Nur einen. Dein Ich von morgen schickt dir dann Kekse statt Hassmails. 🍪

    #OpenSource #Programmierung #CleanCode #DevLife

  30. Guten Morgen! ☕

    Kleine Erinnerung an alle, die heute „mal eben schnell“ ein Script schreiben wollen: Dein zukünftiges Ich liest diesen Code in 6 Monaten und wird dich verfluchen.

    Schreib einen Kommentar. Nur einen. Dein Ich von morgen schickt dir dann Kekse statt Hassmails. 🍪

    #OpenSource #Programmierung #CleanCode #DevLife

  31. Micromanagte Teams hören nicht auf zu arbeiten. Sie arbeiten nur heimlich.

    Bugs werden unter dem Radar gefixt, Refactorings versteckt, Probleme nicht mehr angesprochen. Wer kontrolliert statt vertraut, killt den Flow und merkt es nicht mal.

    #cleancode #Führung #development #dev

  32. Micromanagte Teams hören nicht auf zu arbeiten. Sie arbeiten nur heimlich.

    Bugs werden unter dem Radar gefixt, Refactorings versteckt, Probleme nicht mehr angesprochen. Wer kontrolliert statt vertraut, killt den Flow und merkt es nicht mal.

    #cleancode #Führung #development #dev

  33. LLMs now writes 41% of all code and code churn is set to double in 2026.

    66% of developers say LLMs output is "almost right."

    Translation: good enough to merge, broken enough to need rework. LLM doesn't produce less work, it just shifts it downstream, into review and maintenance.

    Source: dev.to/code-board/ai-writes-41

    #AI #cleancode

  34. LLMs now writes 41% of all code and code churn is set to double in 2026.

    66% of developers say LLMs output is "almost right."

    Translation: good enough to merge, broken enough to need rework. LLM doesn't produce less work, it just shifts it downstream, into review and maintenance.

    Source: dev.to/code-board/ai-writes-41

    #AI #cleancode

  35. „Refactoring-Sprint nach dem Release" ist die größte Lüge der Softwareentwicklung. Der kommt nie. Sobald er ansteht, killt ihn der nächste Prio-1-Task.

    Tech Debt baust du im Ticket ab, nicht im Event. Boy Scout Rule statt technischer Insolvenz.

    #cleancode #Softwareentwicklung

  36. „Refactoring-Sprint nach dem Release" ist die größte Lüge der Softwareentwicklung. Der kommt nie. Sobald er ansteht, killt ihn der nächste Prio-1-Task.

    Tech Debt baust du im Ticket ab, nicht im Event. Boy Scout Rule statt technischer Insolvenz.

    #cleancode #Softwareentwicklung

  37. Writing code gets cheaper with #AI. Understanding architecture does not. That’s why teams drown in systems nobody fully understands. Sven Reinck shows how dependency visualization can make large codebases navigable again: javapro.io/2026/06/10/beyond-u

    #CleanCode

  38. Writing code gets cheaper with #AI. Understanding architecture does not. That’s why teams drown in systems nobody fully understands. Sven Reinck shows how dependency visualization can make large codebases navigable again: javapro.io/2026/06/10/beyond-u

    #CleanCode

  39. Quick C# Tip: Stop using as followed by a null check. Modern C# pattern matching is your best friend! Use if (obj is MyType myVar) instead. It safely casts and assigns in one single, readable line. Less boilerplate, more elegance. 🧼✨ #dotnet #csharp #cleancode

  40. Still writing instanceof + casts + nested conditionals? That’s legacy #Java. With #Java25, pattern matching simplifies type checks, switch logic, and data extraction.
    Learn how with Mihaela Gheorghe-Roman: javapro.io/2026/04/28/pattern-

    #CleanCode #PatternMatching #JDK25 #JAVAPRO

  41. Still writing instanceof + casts + nested conditionals? That’s legacy #Java. With #Java25, pattern matching simplifies type checks, switch logic, and data extraction.
    Learn how with Mihaela Gheorghe-Roman: javapro.io/2026/04/28/pattern-

    #CleanCode #PatternMatching #JDK25 #JAVAPRO

  42. Use Obsidian with Markdown notes, YAML metadata, and direct AI file access to build a Second Brain with LLMs that gives your tools persistent project context. hackernoon.com/ai-coding-tip-0 #cleancode

  43. Use Obsidian with Markdown notes, YAML metadata, and direct AI file access to build a Second Brain with LLMs that gives your tools persistent project context. hackernoon.com/ai-coding-tip-0 #cleancode

  44. Microsoft is gaslighting your workflow. Forced AI in VS Code is creating massive technical debt and breaking your flow across every machine you own. It’s time to reclaim the kernel of your craft. 🛠️💻

    #VSCode #SoftwareEngineering #CleanCode

    bdking71.wordpress.com/2026/05

  45. Файл вырос до 800 строк и это была моя вина…

    На каждом ревью найдётся кто‑то, кто спросит: «Зачем четыре файла, если это один пайплайн?» А затем, давайте объясню!

    habr.com/ru/articles/1033218/

    #python #file_size #aiogram #LOC #architectureascode #refactor #cleancode #code_quality

  46. Long if/else chains, repeated checks, unnecessary casts—classic #Java overhead. #Java25 adds #PatternMatching in switch, #RecordPatterns & guards, reducing boilerplate & improving type safety.
    Mihaela Gheorghe-Roman explains: javapro.io/2026/04/28/pattern-

    #CleanCode #JDK25 @openjdk