#clean-code — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #clean-code, aggregated by home.social.
-
Depois de muito tempo, comecei a escrever sobre o tão falado e, aparentemente, pouco lido Clean Code.
https://dev.to/pbalduino/pt-br-clean-code-passado-a-limpo-2n4hE sim, continuo achando todas aquelas coisas sobre o autor e sobre quem bate palmas para ele.
-
💠 Weniger Code, mehr Substanz
Der beste Code ist der, den du nie geschrieben hast. Das ist das Motto von #Ponytail.
-
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 #MaintainabilityPhoto by Florian Olivo on Unsplash
-
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: https://javapro.io/2026/04/28/pattern-matching-in-java-25-writing-cleaner-safer-faster-code/ -
“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?
-
good read about "#Software #Craftsmanship in the AI Era"
by Sandro Mancuso#tdd #testdrivendevelopment #cleancode
https://www.codurance.com/publications/software-craftsmanship-in-the-ai-era -
On my tech reading stack 📚
-> more #security + #rust + #cleancode• Building Secure and Reliable Systems
• Design Patterns and Best Practices in Rust
• Clean CodeWhat are you reading this weekend?
-
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: https://javapro.io/2026/07/23/are-classic-design-patterns-still-valid-with-modern-java/
-
Learn everything you need to know about Clean Code via these 309 free HackerNoon blog posts. https://hackernoon.com/309-blog-posts-to-learn-about-clean-code #cleancode
-
Always define a clear role at the top of every skill file so you know whose perspective drives the execution. https://hackernoon.com/ai-coding-tip-026-assign-a-persona-to-every-skill-definition #cleancode
-
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: https://javapro.io/2026/06/10/beyond-uml-clean-software-architecture-in-the-age-of-ai%e2%80%91generated-code/
#CleanCode #Java @FLUXparticleCOM
-
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: https://www.gitclear.com/the_ai_code_quality_maintainability_gap
-
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
-
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
-
🚨 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! 😂
https://devz.cl/posts/solid-never-felt-solid/ #BreakingNews #CoderConfession #CleanCode #SoftwareDevelopment #TechHumor #SeniorEngineers #HackerNews #ngated -
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: https://javapro.io/2026/03/24/effective-pattern-matching-2026-edition/
-
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: https://javapro.io/de/datenorientierte-programmierung-mit-java/
#Java #CleanCode #DevOps -
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. 🍪
-
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.
-
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: https://dev.to/code-board/ai-writes-41-of-code-now-but-code-churn-is-doubling-in-2026-372f
-
„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.
-
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: https://javapro.io/2026/06/10/beyond-uml-clean-software-architecture-in-the-age-of-ai%e2%80%91generated-code/
-
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: https://javapro.io/2026/04/28/pattern-matching-in-java-25-writing-cleaner-safer-faster-code/ -
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. https://hackernoon.com/ai-coding-tip-020-create-a-second-brain #cleancode
