What is Code Smell 319?

Hardcoded stateless properties: storing utility classes as instance vars via `new` in constructors, creating tight coupling.

How to avoid hardcoded dependencies in constructors?

Use dependency injection, inline creation, static methods, or pass as parameters — keeps code flexible and testable.

Why is dependency injection better for testing?

It lets you mock or swap providers easily, ditching rigid internals for injectable collaborators.

🛠️ Developer Tools

Hardcoded Stateless Properties: The Silent Code Killer

Hardcoding stateless utilities as instance vars? You're gluing tools to your objects forever. This code smell turns flexible workers into rigid robots.

theAIcatchup Apr 10, 2026 4 min read

Constructor code with red-highlighted hardcoded new keyword and coupling chains

⚡ Key Takeaways

Ditch `new` in constructors for stateless utils — inject instead. 𝕏
Hardcoding boosts coupling, kills testability, mimics real-world rigidity. 𝕏
AI generators spew this smell; linters and targeted prompts fix it fast. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#AI coding #TypeScript best practices #clean code #code smells #dependency injection #software design #software testing

Worth sharing?

Get the best Open Source 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

Clean Code's Enduring Fight Against Software Rot

Rust Panic Traces Slashed 80% — Finally Useful

Kotzilla Fixes Android's Mystery Crashes for Good

E2E Tests: Why Green Lights Don't Mean Your App Works

Stay in the loop