That's why I write weird java code. Or at least others perceive it that way. When we talk about the bigger picture everyone in the room thinks Smalltalk is weird and I am the only admirer of its elegance.

Java's stream API must've had the same problem because now we have:
#range
#rangeClosed

And even if you do remember it clearly, two weeks later you are much more likely to brush off/get over the thing that irritated you back then.

Vibe coding doesn't scale.

Has its dangers as well though. You might create a juggernaut product that is a mediocre solution for everything and a perfect solution for absolutely nothing.

Still trying to look for metaphors in this statement...

The super clean way of handling errors!
Totally not a step back!
Not at all C-style!

Fielding would probably say:
“Java got the HTTP part. It missed the REST.”

Me: well yeah, those are fake agile, yours is true agile.
Her: well imagine me defining agile like that in an interview, the interviewer will be shocked!
Me: and that's how you know you don't want to work there.

(2/2)

Aha, so history started with the Jewish conquest of Palestine from the Arabs starting after WWI. Got it. No history before that.

Then how did it?

Why would anyone ever ask such an obvious question?
The answer to which, BTW, is Hamas of course.

It's because the customer is also a dev team. The team lead has some hard rules and conventions like this.

One other comparable stupidity is the rule that abstract classes should prefixed Abstract*.

But yeah, what were we going to do without those mighty builders in place?

When I was introduced to the project, I was told the customer expert made a rule such that each entity has a builder (the pattern).
I asked what if factory fits better... awkward pause.
Leter I took a look at the code of most entities. They had little to no behavior so they weren't even entities.

The interest rates from a central bank?

At least these are a bit more sound-proofed than apartments, unless also sharing a wall.