Apparently there are no good #gcc tools to find unnecessary header includes in #CPP while using ninja/cmake (and NOTE not being the author of the build system)

...

A lot of you guys are #programmers what's the right tool here?

I don't need something that complains about every external include not found, just local symbols without having to recompile everything.

EDIT: Good Answers everyone!

#code #codeQuality

Sometimes, shipping means stepping back and cleaning house. Refactoring and optimizing today to pave the way for smarter calculators tomorrow.
#CodeQuality #DevDiaries #CSharpDev #LegalInnovation
Sometimes, shipping means stepping back and cleaning house. Refactoring and optimizing today to pave the way for smarter calculators tomorrow.
#CodeQuality #DevDiaries #CSharpDev #LegalInnovation

Every time I get into doing some code, I get sucked into refactoring another part of Inkscape's ancient past.

The problem is; I have an artists eye for code design and ugly, overly complex, under-tested and worse than all of those asymmetric code makes me all itchy.

Tonight's refactoring: No, version strings should not be parsed and saved by some weird third party function.

#inkscape #programming #codeQuality

The Case for Software Craftsmanship in the Era of Vibes - Zed Blog

From the Zed Blog: Working toward genuine, quality software in an era where code production is not the constraint anymore.

State
of AI code quality

Learn more about the insights we've gathered from 600+ developers on how generative AI is shaping developer experience, trust, productivity and code quality across the SDLC.

Qodo

🤖💭 need to think/write: "Should open source exclude AI-generated code?" Not outright bans, but better quality standards!

Research shows AI code has real security issues, but the solution isn't rejection—it's applying the same critical thinking we've always used.

Let's be AI realists: embrace the potential while maintaining the collaborative excellence that makes open source special! 🚀✨

#OpenSource #AI #CodeQuality #TechPolicy

Know What You’re Testing: Mastering Code Coverage in Quarkus with JaCoCo
A hands-on guide for Java developers to generate, visualize, and improve test coverage in Quarkus applications
https://myfear.substack.com/p/quarkus-jacoco-test-coverage
#Java #Jacoco #Testing #Junit #CodeQuality

Why @Annotations Will Eventually Burn You.

Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.

Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.

Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.

Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.

#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming