Yup.

• Always check the Subscriptions page first
• Check Watch Later list, after that
• scroll the Home page, after that

Have never seen a link to a “Trending” page or a “Trending Now” list in any of those spots.

Sounds loke she found the line for being a fall guy that she wasn’t willing to cross.

Not that anyone really believed Elon isn’t calling all the shots here.

I don’t do budgeting, per-se. For personal expenses, the idea of pre-planning everything we’re going to spend just seems like overkill. Maybe that’s just cause we’re not close enough to the poverty line for real financial hardship. But I find a reactive approach works well, rather than proactive.

I keep an accounting ledger that I update every 1-2 weeks. The ledger is just a big Excel (actually LibreOffice Calc) file that I setup with some formulas and pie charts to make it easy to see when expenses are outpacing income, and what our biggest expenses are if we need to cut down for a while (spoilers: it’s utilities and food).

I’ve tried a handful of different free accounting applications in the past, but never found one I liked for the above purposes. I ended up starting a project to make my own, like a year ago, but I haven’t gotten around to finishing it. The spreadsheet approach has been working well enough. All the custom app would do is help automate the data entry.

Bacon Cheeseburger.

Dude, you obviously have never set FOOT on a farm or tractor, in your LIFE. Stop spreading misinformation.

These are raw marshmallows. Yeah, it’s unbelievable how big they are, but that’s just cause they’re fresh and haven’t dried out yet.

Parallel Processing Unit: PPU

Me. I came here to get AWAY from reddit, why the hell would I use it anymore?

I mean… I’d try it… but I’d have an actual dinner planned for later

Not one single mention for Gone in Sixty Seconds?

Lemmings… do I have bad taste?

That’s a perfectly valid approach, yes. We do exactly this, at work. It’s pretty common, if not ubiquitous, to have your database schema consist of not only structure, but data as well. We call it static data, and it’s all defined in deployable scripts, just like our tables and views are. If ISO makes changes to the dataset, then it’s just a table update to match it. And ISO is nice about keeping backwards compatibility inb their standards.

Since this is not strictly your own data, you could also go with just storing the code value on your tables, and letting the UI layer do the lookup, either with built-in features of your language/framework, or with a static csv file, like you mention. You may not want to do this for static data that is entirely your own, like, say, a status or type enum, since it makes your database schema less-self-descriptive, and more prone to becoming invalid.

You could also set the country code up as a not-strictly-enforced foreign key, where your app will lookup additional info (E.G. the proper name) for a country code, if it’s a standard one, but just skip that if it’s not a standard one.

It’s up to you what you think is most appropriate.