Exercise your unit test suite, frequently. It’s your first line of defense against regression, drift, and data decay. Treat it like an immune system — not an ornament.
Time is not absolute. Your code breaks when you treat it that way. https://hackernoon.com/code-smell-307-naive-time-assumptions-and-how-to-fix-it #cleancode
From UML to Inheritance!
At #PSConfEU 2025, @stephanevg.bsky.social took us on an OOP journey with #PowerShell classes:
Constructors & static members
Debugging tips
Method overloading made fun
PSConfEU 2026 tix live → psconf.eu
#CleanCode #PSConfEU2025
- YouTube
️ AI can shave off hours writing boilerplate, but is your delivery really faster? Low‑quality code takes 2.24× longer to maintain.
You ship quickly today but spend twice the time fixing and refactoring tomorrow. That backlog grows fast.
Balance speed with checks: integrate AI suggestions into your CI pipeline so you catch regressions early. Keep your velocity without sacrificing stability.
working on a new very short #presentation about #technicalDept, #cleanCode and #metrics.
whole thing is done in #inkscape, clones and the spray tool are very helpful to create visual slides
REST in #Vaadin? Viele packen es direkt ins UI und wundern sich später über Chaos. @svenruppert liefert einen Bauplan: HttpClient, Adapter, Records & klar getrennte Schichten. So bleibt dein Code testbar!
Lese: https://javapro.io/de/mit-vaadin-flow-rest-endpoints-in-core-java-konsumieren/
#CleanCode #CoreJava #DevSecOps @Vaadin
Just started using an AI coding assistant? Amazing! But beware: even AI-generated code can carry hidden “debt.”
Studies show low‑quality code has 15× more bugs. If you blindly accept AI suggestions, you could be building future headaches.
Action tip: Always run an automated quality scan (SonarQube, CodeScene) on AI‑authored code. Catch issues before they slow you down!
There's an art to writing code comments. Too many and nobody reads them. Too few and future developers curse your name. Find the sweet spot.
Most testing advice sounds great until you try it on a real project.
That’s why I use 4 axioms of testing that hold up in real-world codebases:
1. You can’t test everything
2. You can’t prove it’s bug-free
3. Start early
4. Bias is real
Ask this before writing a test:
**“What’s the purpose of this test in this context?”**
If it doesn’t verify, protect, or document behavior/specs why write it?
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
Ein URL-Shortener von Grund auf gebaut: Sequenzielle IDs, MappingStore, #Vaadin-Verwaltung, alles in purem #Java. Wer wissen will, wie Architektur zu funktionierendem Code wird, findet hier die Antwort von @svenruppert: https://javapro.io/de/teil-ii-url-shortener/
#CleanCode #DevSecOps @vaadin
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
A code review full of sarcasm and vague critiques is like giving someone a broken compass and saying “you’ll figure it out.”
Clarity > cleverness.
If you want better code, offer better feedback. Precision, kindness, and context go further than snark ever will.
New post:
Heuristics to determine unit boundaries: object peer stereotypes, detecting effects and FIRS-ness
https://codesai.com/posts/2025/07/heuristics-to-determine-unit-boundaries
Subscribe to our newsletter: https://codesai.com/newsletter/
#legacy_code #SoftwareEngineering #CodeQuality #Tech
#tdd #cleancode
Was fällt euch auf? Ist das wirklich sinnvoll so?
Diskutiert mal!
Bitte denkt selbst nach und fragt nicht einfach eine KI – eure eigenen Ideen interessieren mich viel mehr!