Your coding agents already wrote a memory layer. It's just not indexed.A few weeks ago I spent most of an evening debugging a postgres connection leak that I was pretty sure I had already debugged. Not a similar one. The same one, in the same service, with the same pgxpoJul 16 · 7 min readvshulcz.hashnode.dev
How I made dependency injection in Python 130× faster: from reflection to compiling the graphThere's a stock argument against DI containers in Python: a container is just overhead, pass the dependency into the constructor yourself and stop overengineering. It sounds reasonable, and I believed1Jun 18 · 8 min readvshulcz.hashnode.dev
Where should dependency wiring live in a Python app?Python does not need a dependency injection container by default. For small applications, direct constructor calls are usually the best option: repo = UserRepository(settings.database_url) email = Ema1VJun 9 · 5 min readvshulcz.hashnode.dev
When Python manual wiring turns into copy-paste architectureI usually avoid dependency injection containers in Python. Not because dependency injection is bad. Most of us already do it when we pass objects into constructors. I avoid containers because small PyMay 26 · 6 min readvshulcz.hashnode.dev
