Jump in the discussion.

No email address required.

This is one of my favorite code related things on the internet. Their github issues are also amazing. I sent it to one of my coworkers who is especially big on enterprise Java style code and he was like "this is why some people don't like Java, but honestly it doesn't look bad to me!" lol

Jump in the discussion.

No email address required.

your buddy should try kotlin


Follower of Christ :marseyandjesus: Tech lover, IT Admin, heckin pupper lover and occasionally troll. I hold back feelings or opinions, right or wrong because I dislike conflict.

Jump in the discussion.

No email address required.

A coworker writes stuff like this and will ding you on code reviews if you don't. It's like dude why are we making interfaces with like a single method and factories that just call what is essentially a constructor for a single small class witch no plans on having other classes with similar functionality?

Jump in the discussion.

No email address required.

How many people work on that project? If you only have a small team and never anticipate having a large team, then enterprise Java approaches offer almost no benefits.

A lot of enterprise Java/C# code always feels like it starts from “separation of concerns” (a reasonable principle on its own) and then starts defining literally everything as its own unique “concern” (i.e. “how do I map type A to type B”).

And don't forget an overobsession with encapsulation between application-level objects. For example, take the shitty getter/setter approach a lot of classes use - if you're using both a generic public getter and a generic public setter, just make the class variable public (and try your best to avoid Lombok)…

Jump in the discussion.

No email address required.

OOP and it's consequences have been a disaster for techcels everywhere.

Jump in the discussion.

No email address required.

I think like 7 right now. I get some of the benefits but I feel like it is excessive to set all that up when we have just a single small class we are using it for. Makes something that could be a simple single class into a bunch of different things and multipies the number of things you have to do just to use it.

Jump in the discussion.

No email address required.

Ugh this stuff always bothers me.

Like in your example, just call the ctor. Oh you might add another implementation next year? Fine, when you do that, you can expand the logic.

There's another team at my job that does shit like this. They have a whole "dependency injection framework" and it's always shit to work with. Also provides literally zero benefits. Never have they actually had runtime-configurable alternative implementations of shit.

Jump in the discussion.

No email address required.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.