Programmer Humor

Standard shitpost and then out of nowhere “Hello inject me with beans please”

WHY IS IT SO FUNNY

We're struggling to deal with climate change and these selfish developers can think of nothing except building more factories. This is a global issue, we need a global solution: eschew factories and services for defining everything globally.

I fucking hate Spring.

The quickest way to get a team of 10 contractors to turn 100 lines of basic code from a decent engineer into 2k, with 50 janky vulnerable dependencies, that needs to be babied with customized ide's and multi-minute+ build times and 60m long recorded meetings.

Fuck Spring.

Hello inject me with beans please

not again

XML is the second worst programming language ever created by humans

Why yes, I would like my stack traces to make no ffing sense! I'm so glad you asked.

My favourite take on DI is this set of articles from like 12 years ago, written by a guy who has written the first DI framework for Unity, on which are the currently popular ones, such as Zenject, based on.

The first two articles are pretty basic, explaining his reasoning and why it's such a cool concept and way forward.

Then, there's this update:

Followed by more articles about why he thinks it was a mistake, and he no longer recommends or uses DI in Unity in favor of manual dependency injection. And I kind of agree - his main reasoning is that it's really easy for unnecessary dependencies to sneak up into your code-base, since it's really easy to just write another [Inject] without a second thought and be done with it.

However, with manual dependency injection through constructor parameters, you will take a step back when you're adding 11th parameter to the constructor, and will take a moment to think whether there's really no other better way. Of course, this should not be an relevant issue with experienced programmers, but it's not as inherently obvious you're doing something potentially wrong, when you just add another [Inject], when compared to adding another constructor parameter.

Say what you want about DI frameworks, but if I have to remove another fucking global variable so I can write a test, I'm going to cut a bitch.

Is this even a joke? In Spring DI beans are nothing but glorified over complicated global variables.

Also this fits in here perfectly https://m.youtube.com/watch?v=k0qmkQGqpM8

I think this might be the first of these I've seen where pretty much all the comments are just agreement.

Can we talk about annotations which are broken when you upgrade spring boot ? You are asked to upgrade some old application to the newest version of spring boot, application that you discover on the spot, the application does not work anymore after the upgrade, and you have to go through 10 intermediate upgrade guides to discover what could possibly be wrong ?

Tell me more about these beans

I'll never plaster the back of my car with stickers that all proclaim the same things in ALL CAPS.

But if I was going to...

It would pretty much match this meme.

I love dependency injection personally.

I managed to completely change how YARP routed requests by registering a single interface.

The flexibility it provides is awesome. And it makes testing so much easier.

DI: ☺️

DI frameworks: 😒

At work we have a lot of old monolithic OOP PHP code. Dependency injection has been the new way to do things since before I started and it's basically never used anywhere.

I assume most people just find it easier to create a new class instance where it's needed.

I've never really seen a case where I think, "dependency injection would be amazing here" I assume there is a case otherwise it wouldn't exist.

Urgh. I just sicked in my mouth.

Die in a hole DI frameworks.

I already have an injection 'framework' it's called a constructor. I already have a factory it's called new