home.social

#clean-code — Public Fediverse posts

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

fetched live
  1. 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

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

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

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

  5. 🚨 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

  6. 🚨 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

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

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

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

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

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

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

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

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

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

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

  17. „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

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

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

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

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

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

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

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

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

  26. Core features only. No bloated code.

    [✓] Samsung Smart Switch support
    [✓] Xiaomi backup extraction
    [✓] iOS Manifest parsing
    [✓] Direct local data control
    [✓] Fast indexing & search

    Just the tools you need to access your own history. 📱⚙️
    Explore the build: keepita.com/

    #Keepita #FeatureList #ProductivityTools #Android #iOS #DataManagement #IndieDev #BuildInPublic #CleanCode

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

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

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

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

    habr.com/ru/articles/1033218/

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

  30. 𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐓𝐫𝐮𝐬𝐭

    At 𝐖𝐞𝐛𝐁𝐨𝐨𝐬𝐭𝐏𝐫𝐨𝐬, we believe the web should be fast, accessible, and beautiful for everyone. 🌐

    We don't just build websites; we build digital experiences that help small businesses compete with the giants. From clean code to responsive design, we’re here to help you grow your digital footprint the right way.

    𝐏𝐫𝐨𝐮𝐝 𝐭𝐨 𝐛𝐞 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐭𝐡𝐞 #𝐅𝐞𝐝𝐢𝐯𝐞𝐫𝐬𝐞!

    webboostpros.com/

    #SmallBiz #WebDevelopment #WebBoostPros #DigitalGrowth #CleanCode

  31. Magic Numbers reduce code readability by hiding business rules in literal values. Replace Magic Number with Named Constant systematically improves code quality through self-documenting constants.

    This technique connects directly to clean code principles and software maintainability.

    newsletter.shiftelevate.dev/p/

    #CleanCode #Refactoring #Java #MagicNumbers #SoftwareEngineering

  32. Magic Numbers reduce code readability by hiding business rules in literal values. Replace Magic Number with Named Constant systematically improves code quality through self-documenting constants.

    This technique connects directly to clean code principles and software maintainability.

    newsletter.shiftelevate.dev/p/

    #CleanCode #Refactoring #Java #MagicNumbers #SoftwareEngineering

  33. There is ASCII Art and there is a View-Finder showing the document space in miniature. How very German of me... #deutschland

    FOSS, single-file, vanilla, save with CTRL + S. This is designed to make single file webpages/programs in absolute position or VW. The keyboard is like Vi. 20 levels per project. #VanillaJS #Minimalism #WebPerformance #Lightweight #SingleFile #NoBloat #FastWeb #ZeroDependencies #CleanCode #OfflineFirst #Efficiency #100DaysOfCode #GreenComputing #LowTech #WebStandards

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

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

  36. Tiefe Vererbung, Seiteneffekte, schwer testbarer Code = klassische OOP-Schmerzen. Birgit Kratz zeigt, wie Records + Pattern Matching Fehlerklassen eliminieren. Weniger Bugs, weniger Debugging.

    Hol dir exakte Beispiele für stabileren Code: javapro.io/de/datenorientierte
    #Java #CleanCode

  37. Tiefe Vererbung, Seiteneffekte, schwer testbarer Code = klassische OOP-Schmerzen. Birgit Kratz zeigt, wie Records + Pattern Matching Fehlerklassen eliminieren. Weniger Bugs, weniger Debugging.

    Hol dir exakte Beispiele für stabileren Code: javapro.io/de/datenorientierte
    #Java #CleanCode

  38. 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 OpenJDK

  39. 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 OpenJDK

  40. Most developers write code. The best ones write code that nobody has to fix at 2am.
    What's the worst "2am call" moment you've had as a developer?
    Drop it in the comments — let's collect the horror stories. 👇
    Comment "CLEAN" below and I'll DM you Utilizor's internal Code Quality Checklist — the exact one we use before every client delivery.
    #SoftwareDevelopment #CleanCode #WebDevelopment #Utilizor #DeveloperLife #CodeQuality #TechFounders #Programming

  41. 🚪 Where privacy meets poetry in pure HTML.
    I crafted a tracker-free corner of the web: no ads, no bloat, no surveillance. Just 5 trusted European sources for knowledge & privacy, with built-in listen/copy/save tools.
    You’re a guest here. Never a product.
    🔗 doors.mom/doors-eu.html
    #DigitalPrivacy #CleanCode #OpenWeb #PrivacyByDesign #Eu #security
    🤍🧊🪷🦋🌊🐟🌳🌸🍷🌷🍃

  42. 🚪 Where privacy meets poetry in pure HTML.
    I crafted a tracker-free corner of the web: no ads, no bloat, no surveillance. Just 5 trusted European sources for knowledge & privacy, with built-in listen/copy/save tools.
    You’re a guest here. Never a product.
    🔗 doors.mom/doors-eu.html
    #DigitalPrivacy #CleanCode #OpenWeb #PrivacyByDesign #Eu #security
    🤍🧊🪷🦋🌊🐟🌳🌸🍷🌷🍃

  43. Behold, the Nanopass Framework: the IKEA toolkit for compiler construction. 🛠️ Just add a pinch of domain-specific seasoning and voilà, a compiler with enough "intermediate representations" to make your head spin! 🎡 Who knew compiler creation needed to be this... "clean"? 😏
    nanopass.org/ #NanopassFramework #CompilerConstruction #IntermediateRepresentations #CleanCode #DomainSpecific #HackerNews #ngated

  44. #JPA is not a silver bullet — but it doesn’t have to be a bottleneck either. Julius Mischok shows when to tune JPA, when to use projections, and when plain SQL is the better choice.

    Read the full piece: javapro.io/2025/12/31/high-spe

    #ORM #Java #Persistence #Hibernate #CleanCode

  45. Optimizing Git for AI Workflows

    The introduction of AI in coding has disrupted traditional Git workflows, leading to issues like lost uncommitted work, cluttered branches, and anxiety over stashing. To address this, the concept of a "Mirror Branch" is proposed—a personal workspace for developers to freely commit messy outputs, logs, and drafts without the pressure of maintaining a clean history. This method allows for exploration and experimentation while keeping the feature branch uncluttered. By separating the messy process from clean code promotion, developers can maintain context and memory of their problem-solving journey, thus enhancing productivity and reducing mental overhead without losing valuable insights along the way.

    roofman.me/2026/04/09/optimizi

  46. A new Blog section is now live on:

    🔹 stackcompassguide.dev/blog.html

    It contains articles about keeping architecture simple, avoiding overengineering, and recognizing common software anti patterns, based on real world decisions and tradeoffs. I will keep adding more over time.

    If you are figuring out what to use and why, this might help or maybe even inspire you. 😉
    I would really appreciate any feedback.

    #programming #softwaredevelopment #cleancode #softwarearchitecture #devops #refactoring

  47. The fourth article in the Architectural Decisions series is out now ✅

    This time, it’s about why simplicity often wins over unnecessarily complex architecture in practice. Why it’s better to start simple, avoid premature optimization, and when it actually makes sense to introduce complexity.

    If you’re dealing with system architecture or thinking about better technical decisions, it might give you a new perspective, maybe help, maybe inspire. 😉

    🔹 mortylen.hashnode.dev/why-simp

    #programming #cleancode #softwarearchitecture #softwaredevelopment #decision #refactoring #devops

  48. ApproveJ 1.6.0 is here 🚀

    ✨ Inline Value Updates update approved value in your test source
    📸 Enhanced Visual Feedback with diff
    🤖 AI Assisted Reviews

    👉 approvej.org
    🔗 Full Changelog: lnkd.in/eyTtdR_3

    #ApproveJ #Java #SoftwareTesting #OpenSource #VisualTesting #IntelliJ #DX #CleanCode

  49. Have you ever found yourself in a situation where you wanted to do things “the right way”… only to end up complicating your life? 🤔

    In a new article from the Architectural Decisions series, I explore how good intentions lead to overengineering.

    If you’re building things “just in case,” you might be creating problems that don’t even exist yet.

    I hope this article helps and inspires you.

    🔹 mortylen.hashnode.dev/when-goo

    #programming #cleancode #softwarearchitecture #softwaredevelopment #decision #overengineering