You must log in or register to comment.
Why would Santa need two separate tables for this?
don’t underestimate database design in production environments
Exactly, Santa’s always watching and audit logs get complicated
I would make two separate views.
CREATE VIEW NiceList AS SELECT * FROM Children WHERE behavior = 'nice' AND parent.income > 40000; CREATE VIEW NaughtyList AS SELECT * FROM Children WHERE behavior = 'naughty';The income is a nice touch.
The poor kids can’t even afford coal and fall through the cracks.
Only the nice ones, the naughty poor children get free coal
But not the poor nice ones
The poor nice ones get beaten by the naughty rich ones.
… and by the “nice” rich ones.
Why are we using magic strings for behavior?
Feel free to fork my comment.
CREATE VIEW NiceList AS SELECT * FROM Children WHERE behavior > 2000 AND parent.income > 40000; CREATE VIEW NaughtyList AS SELECT * FROM Children WHERE behavior <= 2000;
Professionals do seem to use excel.
Holy fuck is it painful for anyone that knows what they are doing.15000 rows. 120 columns. One sheet. Creation date: 2011. A dedicated computer. Working at a multinational company is bad for mental health.
And then OneDrive comes along, someone accidentally saved “to the cloud” (IE the default windows location of OneDrive). And of course someone (you) has to fix all the desync bullshit.
Fuck excel, fuck Microsoft, fuck OneDrive!Thank god my company is transitioning to a decent no code solution (nocobase plus literally anything that can interact with postgres - currently n8n but not yet limited to that. It’s a transition from excel, literally anything is better! (Tho, nocobase is awesome, non has it’s perks)).
Many parentheses, soz.
Fuck excel, use a database!
In all honesty, I feel like proper database solutions are just not as accessible to laypeople as they’d need to be. It’s easy to create a table in Excel, enter arbitrary values and share it. It’s also not particularly hard to create a second table and add some simple formula for a lookup. More complicated logic can be learned as you go.
By comparison, something like, say, Access needs more effort and understanding of data structures. You can eyeball a spreadsheet and just enter values without worrying about types, data integrity or anything. Never mind setting up actual database servers.
Yes, obviously those “proper” definitions would be more reliable, but particularly when the use cases aren’t entirely clear from the outset and new ones keep getting tacked on to an existing solution, it’s just more convenient in the moment to use a fairly low-effort solution until the whole thing becomes a clusterfuck of “low-effort” solutions.
It becomes a matter of platform gravity: By now, so many people are used to Excel and so much infrastructure is built around it that even a new, better and more laypeople-friendly data handling tool would have a hard time getting a foot in that door.
I consider myself pretty knowledgeable with most computing tasks, not particularly great with basic spreadsheets, but unless there’s some kind of usable frontend to reliably manage a database, I mostly see databases as:
“A magic box that holds tons of cryptic information, would be tedious to open, risky to edit, risky to backup or migrate or update, and could corrupt at any moment.”
Maybe I should put more effort into learning DBs besides initializing them in a Docker compose and praying, but for human readable information that’s meant to be shared, I think you’re bang on the money when it comes to why spreadsheets are still so popular!
As someone who interacts with databases regularly… Yeah, that sounds about right.
I was recently working with another team’s feature to handle data retrieval for the end user, pretty front end but it was far too tightly coupled with db management concepts. How is a non-technical person supposed to know the difference between an inner join and a left join?
Not too long ago I suggested using cross apply to a senior dev I work with and they admitted they weren’t sure what that does or how to use it. People who don’t regularly work with databases have no chance.
It’s a lot of individual tables because Santa’s excel struggles with anything past a few hundred thousand rows. It’s not just names, but addresses, lists of desires, and so on.
There are around 2 billion children. If you wonder why he skips so many children, it’s not religion or poverty, it’s because Santa’s files got corrupted.
In an unfortunate coincidence, the tables were sorted by the children’s parents’ annual income, so it was the poor kids whose data was lost. That’s why rich kids get more presents.
It’s a honeypot. Any attempt at SQL injection is logged on the Naughty List.
Separate scanned PDF per person, as an image, no OCR, 3MB in size
You mean the Normal File Format?
edit: there’s an updated version of this where the only way to get at the document is to download it from the unofficial Whatsapp group.
Good guy Tim tryin to make sure everyone has a Merry Christmas. Sounds like nice list material to me.
The real pros don’t even link or connect them. You have to know the others exist.
They are connected. In my head.
lame bobby tables rip-off
Listen, there’s room in SQL for more than one input sanitization joke.
