this post was submitted on 03 Jun 2026
738 points (99.6% liked)
People Twitter
10031 readers
680 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a pic of the tweet or similar. No direct links to the tweet.
- No bullying or international politcs
- Be excellent to each other.
- Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician. Archive.is the best way.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One time at work I was tasked with writing a python script to compare two data sources. Like, you give it two CSVs and a primary key, and it tells you what data is in one but not the other, or mismatched, and so on. This worked fine and was in git, so anyone can use it.
My boss then asks if I can "put it on a website so anyone can use it".
This team has never done web development. Nothing for that is set up. Like, I could spin up a quick Django app or similar, but there's a lot of stuff to do and potentially fuck up.
I said "that sounds like a lot of research and ongoing maintenance costs. I think it'd be better to just check out and run the script"
Luckily for me he said "oh, okay"
How big were the CSVs? That sounds like a standard thing most spreadsheet apps can do already, unless the data size made traditional apps unusable.
The biggest ones I've seen are 1.2GB.
Why this company uses gigabyte CSVs is a separate problem.
(Also sometimes they want to compare a CSV to what's in a database, which the script can also do but I didn't mention in the post)
That makes sense. I have been asked to write a program that does a standard spreadsheet function on multiple occasions, so I was just curious. Sometimes people just don't know the tools at hand, want to offload their work, or think an over complicated workflow is a better workflow. I can see how it was actually useful in your case though.