Me, I use plain-text accounting (hledger) that automatically imports the CSVs from my bank and categorizes transactions automatically, and I wrote some quick scripts using Python to import the PDFs from my brokerages and paystubs. It's not automated pulls but I only have a handful of accounts so it's really not a pain to manually pull statements once a month and run the import scripts. It takes me longer to reconcile everything to the penny then it does to do the imports, and it's a whale of a lot faster than manually entering through GNUCash. Plus, it's plain text so all you need is vim, git, and the command line.

But that's still more of a hassle than putting the carton of that yellow plastic liquid in the microwave for a minute and a half. People will prefer their slops and the farmer brings it right to you; what could possibly be a better life?

So on QNX, the spawned process does all the dynamic linking. The spawning process just sends an asynchronous message to the process manager and then gets on with things in a very deterministic manner as befitting a hard realtime system.

Also, consumer credit was illegal until the same time period, and only legalized for people with vaginas in the mid-1970s. That alone might have made all the difference with marriage and fertility (which after all are only mildly related).

Imagine how your choices would expand if unlike your mother, you did not need to become Mrs. John Doe to be able to move out of your father's house.

Enthusiam and neat ideas are not sufficient to certify a development tool for functional safety.

The problem does not appear to be in C++.

Most of our customers use C, probably for historic reasons but also because it is much much easier to reason about and that becomes very important when auditing for functional safety certification. If someone's life depends on your software, you really want to be able to reason about its correctness because orange jumpsuits enhance no one's complexion.

Many of customers are now using C++. From the problems they have reported, well, they just shouldn't. It's not that it is a bad language (it isn't) or that it is inherently unsafe (it really isn't: exceptions are safer than propagating return values as long as you use them in exception conditions, because not catching one will return you to a designed safe state very quickly, and RAII is the best thing since sliced cheese). It's that cutting and pasting from Stack Overflow, and now vibe coding, makes for massive codebases that are next to impossible to reason about. I now see a lot of problems from customers where my first reaction is "don't write code like that" and "you can write bad JavaScript code in any language, can't you?". While it butters my bread and I enjoy the language, I really recommend against using C++ for safety-certified embedded software. Stick to C.

Or, I can pick up 100 shares of an index ETF for a few thousand and have someone else do all the work for me including rebalancing and doing all the other required calculations (lot tracking and cost basis calculations etc.).

Given that when a hive goes queenless the workers start laying eggs including in the royal chambers they're desperately building, and since the workers are unfertilized all of the eggs are haploids that hatch into drones, it has probably happened many times throughout apian history. No drag queens have been spotted.

No amount of cartoons or colourful bouncy animation of pictures on the screen can replace simply displaying text when what you need to do is display text on the screen. And it turns out that text is a really good way to display information.

A picture is worth a thousand words but why would you use 1000 words when only one or two will do?

C'mon litle guy. You can make yourself famous. Be brave and let go of the wall of that leg vein. Say good bye to that comfy cankle and enter into your full glory.

21 days left. I don't plan to look back.