You have 1 wish...

I once looked through a textbook from my friend's MBA course. The first thing I noticed was in a highlighted box in the chapter on business negotiating: "Your skill at negotiating will affect the outcome of the negotiations."

These are the people that make 10X what I make.

I learned this in my first statics class, and I have a BS in business administration.

It would be funnier if the genie says "there are two rules"

I once worked for a Japanese company where I had to make a presentation. In Excel, I shit you not. Then we had one of our "shadow" managers make a Japanese translation of the same thing. It took me two days to get the kerning and print layout right, especially with that weird english typeface that is Japanese standard, I hate to think how long the translator took to get their version right.

This is the way

I only ever encountered Access was once many years ago and I was warned that it had issues with multiple users.

i...isn't that the entire point of excel? what is it for if not to store data?

similarly i remember a reddit comment that broke my brain, saying no one should be using excel, they should be using a 'cell matrix organizer' or similar. we all can name 5 off the top of our heads

No simple way to join tables though, which is still pretty shocking to me.

Employers get what they demand, what they deserve. Anyway excel works as a database until around 1 million entries...

I feel you. Working in healthcare, ms office is the only thing consistently installed site wide I can take advantage of to run a db.

I work as a network tech for a globally spanning ISP specializing in fiber services, handling major maintenances that are service effecting for business and government customers (SLAs are in effect). These maintenances are planned and tracked through various excel sheets - housed either in a shared network drive (so yeah, we may run into issues where multiple people are trying to edit the same doc at once), or excel tables in a SharePoint.

Prior to the merger of companies I recently went through, we had actual database systems to track this stuff that worked just fine. And now we're relying on the same shit a grad student would use to track their doctorate progress. It'll work until it doesn't. Looking forward to the shit-show if it gets me overtime.

How about last week?

Why yes this comic made me think of our users, why do you ask?

Fun fact: most of the electronic voting machines in the 2000 presidential election used Access to store vote counts. Access, the "database" with a user-editable audit table.

ADO or DAO?

What the fuck. Thanks for sharing!

I mean it's a simple file format so it'll perform better because it doesn't have to decode any complex formats or protocols.

Big O? Never heard of it!

CSV is great but the byte loss on numbers is sometimes gruesome.

Except PowerPoint is actually quite nice to make quick, easy and good looking visualizations and brochures without having to deal with Word

Error 0x2e8da08150469

Even Genie have standards.

Iirc tables are actually treated similar to databases on the backend.

I mean it will work, but for a blog I'd store the pages in markdown files, to make it easier to edit. For context, look into how Hugo works

A few circumstances to consider...

If it's just your own little tool and you don't intend to share it with others: do whatever you want. SQL or NoSQL or JSON, it doesn't matter. Use your own judgement.

In my experience tho most homegrown JSON-based "databases" tend to load all data into the memory, simply because they are very simplistic (serialize everything into JSON and write to disk, deserialize everything into a struct). If your dataset is too big for that, just go straight for a full-fledged database.

TinyDB literally does this. in general its more of does this work for my use case and am i aware of its limitations.

If it works then it works.

yep, though IO might bottleneck you at some point, and then you can happily switch to mongoDB

one of our partners we have to integrate with at work sends us reports in ms access format. it's not fun, especially when everything is running in lambda and there doesn't seem to be any good libraries for reading ms access files that would easily run in lambda.

A million rows sounds like a lot until you need more than that

In my experience it doesn't work well when you have more than a couple people editing the file. My company had a group of ten modifying the same file in live time; it led to huge desync problems.