Products · Pattern or everyday thing
Dependency injection
Raised as a usability problem by 10 people on Hacker News over 12 years (2014–2025), in 10 threads.
People raised many different problems with Dependency injection, but no single problem has yet been raised by 3 people in 3 different months and threads.
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 10 complaints
- Ctrl+click doesn't jump straight to the actual implementation2025-05-25
- Hard to tell when objects are constructed and what calls what2024-06-28
- When injection fails, it's hard to diagnose what went wrong and why2023-02-19
- Tracing which implementation runs requires digging through layers of configuration and implicit magic2022-12-16
- Exceptions give no graph info, so cycles are hard to diagnose and fix2022-02-27
- Can't jump to the actual injected dependency, only to its interface, making code hard to understand2021-10-19
- Tracing where injected or annotated code is defined becomes a lengthy research project2020-09-22
- Code using passed-around config objects and dependency inversion is nearly impossible to follow2018-07-26
- Must register and declare dependencies in separate places, hard to trace and check2016-07-26
- Simple connection requires building many factories and providers before doing anything2014-04-29