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?

[–] bitjunkie@lemmy.world 1 points 10 hours ago

Diming on her own stupidity without realizing it, like all of them do

[–] zenpocalypse@lemm.ee 27 points 1 day ago (2 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.

[–] psivchaz@reddthat.com 2 points 14 hours ago

It sounds like Hollywood tech lingo. Like when you're watching a movie or a TV show and the designated techy character starts just saying computer words that make no actual sense in the real world, but I guess in CSI: Idiottown the hard drives have severe overheating issues.

[–] Akasazh 5 points 23 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 24 points 1 day ago (2 children)

Some interesting facts about excel I learned the hard way.

It only supports about a million or so rows
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 8 points 21 hours ago* (last edited 21 hours ago) (1 children)

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.

[–] blackbirdbiryani@lemmy.world 1 points 4 hours ago (1 children)

Could you import the column in as text to preserve it?

[–] driving_crooner@lemmy.eco.br 1 points 4 hours ago

Sure, but sometimes you need to do a pivot table and get transformed, or you while working you accidentally made it a number, or just because excel being excel it import the number as scientific notation, or any other case.

[–] Mniot@programming.dev 9 points 1 day ago (1 children)

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."

[–] frezik@midwest.social 3 points 12 hours ago* (last edited 12 hours ago)

Some time ago, I heard a story of CS and Econ professors having lunch together. The Econ professor was excited that Excel was going to release a version that blew out the 64k row limit. The CS professor nearly choked on his lunch.

Dependence on Excel has definitely caused bad papers to be published in the Econ space, and has had real world consequences. There was a paper years ago that stated that once a country's debt gets above 120% of GDP, its economy goes into a death spiral. It was passed around as established fact by the sorts of politicians who justify austerity. Problem was, nobody could reproduce the results. Then an Econ undergrad asked the original author for their Excel spreadsheet, and they found a coding error in the formulas. Once corrected, the conclusion disappeared.