Using a few terrabytes of memory and a stack of processors as high as my knee so they can recreate Excel in a badly rendered .aspx page built in 2003.

[–] [email protected] 7 points 1 month ago (1 children)

We have a table with literally three columns. One is an id, another a filename and a third a path. Guess which one was picked as the primary key?

Never seen something so stupid in 28 years of computing. Including my studies.

[–] [email protected] 3 points 1 month ago

Well, you don't want to waste space by adding the same file path twice

[–] [email protected] 2 points 1 month ago (1 children)

As a dev, I had to fix an O( n! ) algorithm once because the outsourced developer that wrote it had no clue about anything. This algorithm was making database queries. To an on-device database, granted, so no network requests, but jesus christ man. I questioned the sanity of the world that time, and haven’t stopped since.

[–] [email protected] 1 points 1 month ago

Oh yeah, I love people who stick SQL lookups in a For Loop. Even better, the coder who puts conditional if (but no then/else) clauses around a dozen raw text execution commands that fire in sequence. So you're making six distinct lookups per iteration rather than answering your question in a single query and referencing the results from memory.

Internal screaming