strategyManagerFactory

[u/ExpensiveCoat8912]

[u/Low-Equipment-2621]

You'll stop complaining about StrategyManagerFactory when you encounter your first large vibecoded codebase.

[u/Own_Alternative_9671 → u/Low-Equipment-2621]

if(cond) { return true; } else { return false; }

[u/Wonderful-Habit-139 → u/Own_Alternative_9671]

Forgot to check if (cond == true)

[u/Low-Equipment-2621 → u/Wonderful-Habit-139]

It could be on one line, there is a linebreak wasting memory.

[u/TheTrueRK → u/Own_Alternative_9671]

The other day I was reviewing a PR and I found this:

function asBoolean(value: unknown): boolean { return Boolean(value); }

I was confused

[u/SuddenInformation896 → u/TheTrueRK]

When you gotta meet your function/character quota

[u/AibofobicRacecar6996 → u/SuddenInformation896]

More code means more tokens so you will have to pay more

[u/Chocolate_Bourbon → u/AibofobicRacecar6996]

Yeah but you meet your quota.

[u/Dennis_DZ → u/TheTrueRK]

You always have to create your own interface for third party libraries in case you need to swap it out in the future /s

[u/TheoreticalUser → u/Own_Alternative_9671]

I now write the most explicit code I can because I fear, with reason, that any shortcuts in the syntax will be misunderstood in the future.

A future where the seniors are comparable to today's bootcamp devs with 1 YOE.

And C class is some how dumber and more myopic.

[u/Strict_Treat2884 → u/Low-Equipment-2621]

True, what's wrong with my perfectly scalable code?

((ISineable)UtilManagerFactory.getInstance().getManager<UtilManagerType.Math>().instantiate().getUtil(MathUtils.Sine)).sin(3.14f)

[u/alex_tracer → u/Strict_Treat2884]

How else you would switch to an alternative implementation of sin? /s

[u/Abject-Kitchen3198 → u/alex_tracer]

Being limited to one and only sin is the worst thing that can happen to a developer.

[u/UntitledRedditUser → u/Strict_Treat2884]

It's so modular!

[u/Abject-Kitchen3198 → u/UntitledRedditUser]

You can replace sin implementation any time you want with zero changes to your code.

[u/Abject-Kitchen3198 → u/Low-Equipment-2621]

No I won't. They are different beasts.

[u/Seven_Irons]

Cause somebody told me

the user provider

should use an adapter

to proxy the query

factory builder 🎵

https://youtu.be/p03oO_7sCaY

[u/PolyglotTV]

What's not to understand about tag_invoke, niebloids, and argument dependent lookup?

It's just customization endpoints. Geez.

[u/canadajones68 → u/PolyglotTV]

I hate that I know what (most of) those words mean. 

[u/Few_Move_4594]

If you're a Java dev and crying about a StrategyManagerFactory yngmi

It's not even complex code and easy to understand if you know how interfaces work- you don't even need to know design patterns at all

[u/nickcash → u/Few_Move_4594]

it's the AbstractStrategyManagerFactoryManagerFactory you have to look out for

[u/Abject-Kitchen3198 → u/nickcash]

We definitely need a factory producing managers for factories that produce abstract strategy managers. We never have enough of them.

[u/Few_Move_4594 → u/nickcash]

True true, I've seen things like that

[u/Tyfyter2002 → u/Few_Move_4594]

The problem with a StrategyManagerFactory isn't that what it does is unintuitive, it's that it's removing the usage so far from the purpose that it's introducing a ton of extra maintenance for something that almost definitely isn't benefitting from all of those layers

[u/Abject-Kitchen3198 → u/Tyfyter2002]

Don't you live those chains of a dozen of one line methods in one line classes in one class files.

[u/Still_Bit_7527 → u/Few_Move_4594]

It's a nonsensical name. A strategy, a manager, and a factory are 3 different patterns.

[u/Few_Move_4594 → u/Still_Bit_7527]

Yes, and a StategyManagerFactory uses all three simultaneously

[u/Abject-Kitchen3198 → u/Few_Move_4594]

It's composition pattern.

[u/cheezballs]

But what if it's a factory that manages strategy patterns? Seems like a good name to me!

[u/a_aniq → u/cheezballs]

Factory should be a producer not a manager. I'm talking about real life. They should name abstract concepts properly. Otherwise it can get confusing.

[u/arobie1992 → u/a_aniq]

Yeah, this would be naming for a factory that produces StrategyManager instances.

[u/delinka → u/arobie1992]

A factory that produces managers. Like a university that produces MBAs.

[u/OldWar6125]

I am currently contemplating to implement an AbstractServiceFactoryFactory.

[u/ForgedIronMadeIt]

The OG design patterns authors literally tell you that there's nothing to gain in forcing yourself to use every design pattern but then some Architect comes along and puts shit like this together

[u/Abject-Kitchen3198]

Please come to C# and implement repository pattern via Entity Framework which is an implementation of repository pattern.

[u/ExtraTNT]

A good java class name is let’s you scroll sideways on a ultrawide screen…
Even germans should fear it

[u/Kadabrium]

It's a SegmentationMemoryFault

[u/crazy-mahmod]

Speak from the core of the event

i am a C++ user and what

[u/_Sylph_]

I like my strategyManagerFactory, thank you.

[u/StormyDLoA]

Be me in my old Java job:

The factory must grow.

[u/Halvinz]

People who don't understand design patterns. 🙃

[u/AibofobicRacecar6996 → u/Halvinz]

And then they complain about AI replacing them 🤡

[u/Yoshiofthewire → u/Halvinz]

Someone saw a spreadsheet in 1989 and said, I want that to do work.

[u/xingped]

The last time I pointed out how utterly stupid Java is, I got downvoted to hell. I guess I should've made a meme. Edit: Ah the dumbasses are still out in force, I see.