GissaMittJobb

General purpose: Kebab case

But really, follow the conventions of what you're working on. For example, I'd use pascal case when working on a Java/Kotlin project, and snake case when working on a Python project.

Not saying there's any reason to switch, but I believe you can load CSV's into sqlite.

Datasette would be something that I would try for CSV's as well, that seems like an interesting piece of technology I haven't had reason to use yet.

Finally there's always Jupiter Notebook and any respectable DataFrame-solution.

Not to knock spreadsheet-solutions too much - I certainly see their value and use them frequently - but if I had to do something that warranted writing VBA, I'd probably reach for a tool I could combine with some form of VCS like Git at least.

I don't know if it matches your desire for easy install of small disk space, but it might make up for it in other arenas - Ruby is my new-found love when making simple scripts. Being able to mostly emulate the shell integration that bash has by just using backticks to call a shell command is the killer feature in my book.

Naturally, but by then it's no longer milk, it's tofu.

Basically cheese but made out of soy, afaik.

Oat every day of the week honestly

Out of all the things you can make out of soy, why milk? Tofu exists and it's grand-master based food. I'll smash several plates of mapo tofu without hesitation. Soy sauce, edamame, all ridiculously good shit.

I'm sure they make enough money to not care. Being in the part of the company that brings in the dough is generally a pretty good position to be in as well.

While Rust would probably have been a good choice for implementing a new browser, I don't think Swift deserves the criticism it's getting in this thread:

• Swift was created by the same person who created Rust, and has many of the same nice traits
• Swift is a modern language that is easy for plenty of developers to pick up; I'd place it in the same family as Rust and Kotlin
• Swift grants access to a large pool of native iOS/Mac developers

Podcasts often dynamically generate ads at the point of download, making the SponsorBlock-approach unviable: since the media is expected to be variable-length you can't store media positions that map to advertisement segments.

Healthcare is pretty rough, I'd be willing to bet that the grass actually is greener in this case.

Actual unironic gigachad moment