[kwillets]

This is data engineering, where people spend thousands of dollars of their company's money to avoid learning SQL. The place with no Java is across the street (old Soviet joke, originally for meat/fish stores).

[icedchai]

Sad but true. Or they learn "something" about SQL but not about indexes, data types, joins, or even aggregate functions. I've seen some python horror shows that would select * entire tables into lists of dicts, only to do the equivalent of a where clause and a couple of sums.

[_ea1k]

Ouch. I was really hoping this wasn't so common, but I guess it is. I'm sure they heard somewhere that "joins are expensive" or something along those lines, so they solved it!

[icedchai]

There are also other "lets pretend we have big data" patterns I've seen. Running something like AWS Athena or Hadoop over and over, for less than a couple gigs of data that would fit into memory on a laptop from 15 years ago.

[solid_fuel]

Prisma built a whole ORM around that, complete with the client-side joins.

[joseda-hg]

Classic, I remember seeing something like this

SELECT * FROM X, into a C# list, Filter it with LINQ, and then use C# to do calculations

"Why not EF?" "Someone told me it was slower"