Somebody Told Me (The User Provider Should Use An Adaptor To Proxy The Query Factory Builder) (youtu.be)

submitted 2 weeks ago by codeinabox@programming.dev to c/programmer_humor@programming.dev

9 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] bleistift2@sopuli.xyz 17 points 2 weeks ago* (last edited 2 weeks ago)

Boy, I recently had to look into the Java backend to figure out… something. I can’t remember.

It turns out that they needed to inject a bean into their class which was itself calling a factory, which according to documentation, instantiated three other classes just to make a fucking HTTP request! What’s worse, that clusterfuck of a (fairly standard) library required the base URL to be declared separately from the actual paths, and both the base URL needed to end with a slash, and each path must begin with one. Every reasonable programmer would assume that this is a mistake because the final path would end up with two slashes, but the library actually required that.

Meanwhile, frontend: fetch('url').then(r => r.json()).then(beHappy)

[-] aaaaaaaaargh@feddit.org 8 points 2 weeks ago* (last edited 2 weeks ago)

But you always get something in return for all those layers and layers of abstraction. For me most of the time it was a lot of Java/Spring features I didn't know existed and after that I realized they were pointless.

[-] DeprecatedCompatV2@programming.dev 7 points 2 weeks ago

Noooo, you have to override 50% of the class methods to hard couple your filter's implementation to an event-bus-style bean with Spring in the package name to avoid NIH! What if someone needs to extend your Authentication Provider in the future but can only use a limited quota of keystrokes to implement their ticket as an inobvious side-effect? How else will they add the aud from your JWT to the MDC? Some kind of pointcut??