What is hardcoded stateless properties code smell?

It's instantiating stateless utility classes (like formatters) directly in constructors as private instance vars—creates tight coupling, test woes, rigid designs.

How to fix hardcoded dependencies in constructors?

Use dependency injection via constructor params, pass as method args, static methods, or inline creation/logic. Linters help spot 'em.

Why do AI code generators create hardcoded stateless properties?

Training on quick scripts favors 'new' in constructors for speed; lacks nuanced DI unless prompted. Humans must review.

🧠 Engineering Culture

Ditch Hardcoded Dependencies in Constructors Now

Your constructors are hoarding useless roommates. Time to evict them with proper dependency injection.

theAIcatchup Apr 10, 2026 3 min read

Constructor code with hardcoded new keyword turning into rigid coupling chains

⚡ Key Takeaways

Evict hardcoded stateless utils from constructors — use DI or inline. 𝕏
This smell tanks testability and hides coupling; linters catch it easy. 𝕏
AI spits it out often, but detects it flawlessly when shown. 𝕏

Published by

theAIcatchup

Ship faster. Build smarter.

#AI code generation #Clean Code #TypeScript refactoring #code smells #dependency injection #software testing #typescript

Worth sharing?

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

AI Spits Out Code in Hours, Crashes in Minutes: Who's Minding the Bugs?

40,000 Users Vanished: The QA Blind Spot Behind Production Disasters

Bug Reports That Force Developers to Act

Clean Code: The 70% Rule That's Still Haunting Every Dev Team

Stay in the loop