this post was submitted on 16 Mar 2025
714 points (98.9% liked)

Programmer Humor

21564 readers
2159 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] RussianBot8453@lemmy.world 82 points 9 hours ago (2 children)

I'm a data engineer that processes 2 billion row 3000 column datasets every day, and I open shit in Excel with more than 60k rows. What the hell is this chick talking about?

[–] zenpocalypse@lemm.ee 20 points 7 hours ago (1 children)

Seems like a good excuse to someone who doesn't know what they're doing and needs an excuse because why they haven't completed it yet?

The whole post is complete bs in multiple ways. So weird.

[–] Akasazh@feddit.nl 3 points 5 hours ago

If you work for a boss that fundamentally misunderstands what you are doing, then misleading them into thinking you're 'hard at work, making decisions with consequences' is the theatre you put up to keep the cash flowing.

It's one of the fundamental flows of autocracy, people try and represent what you want them to

[–] person420@lemmynsfw.com 22 points 8 hours ago (2 children)

Some interesting facts about excel I learned the hard way.

  1. It only supports about a million or so rows
  2. It completely screws up numbers if the column is a number and the number is over 15 digits long.

Not really related to what you said, but I'm still sore about the bad data import that caused me days of work to clean up.

[–] driving_crooner@lemmy.eco.br 3 points 4 hours ago* (last edited 4 hours ago)

It completely screws up numbers if the column is a number and the number is over 15 digits long.

I work in insurance in Brazil, by standards of our regulatory body, claims numbers must be a string of 20 numbers (zfill(20) if needed). You can't imagine the amount of times excel had fucked me up rounding down the claim numbers, this is one of the first things I teach to my interns and juniors when they're working with the claims databases.

[–] Mniot@programming.dev 4 points 6 hours ago

The row limitation seems, to me, like an actually-good thing. Excel is for data where you might conceivably scroll up and down looking at it and 1M is definitely beyond the ability of a human even to just skim looking for something different.

An older version of Excel could only handle 64k rows and I had a client who wanted large amounts of data in Excel format. "Oh sorry, it's a Microsoft limitation," I was thrilled to say. "I have no choice but to give you a useful summarization of the data instead of 800k rows (each 1000 columns wide) of raw data."