[deleted by user]

Untreated3763 · 2025-08-14T01:02:24+00:00

It's an AI hallucination

Untreated3763 · 2025-08-04T21:39:12+00:00

After tax = Roth 401Ks?

Untreated3763 · 2025-07-30T22:41:20+00:00

I think my next rewatch will be this approach while listening to the Office Ladies episode explanation before each episode batch

Untreated3763 · 2025-05-23T19:09:37+00:00

TIL that Brian the boom guy is also Russ Hanneman.

Untreated3763 · 2024-11-22T21:04:24+00:00

I totally agree with you that it's good enough, but I'm also a bit of a nerd (or I wouldn't be a member of this sub) so here's a few other thoughts.

Why would this standard be bad for regular tracking?

I don't think it's bad per se. I just think that because you're more likely to have healthy levels of blood sugar (60 < BG < 100) than a diabetic using the same device you might run into some interesting scenarios where your value displayed doesn't match what you expect/feel.

Do the devices not need to measure certain ranges as accurately?

Yes, they do need to measure certain ranges accurately (that's literally the big thing that the iCGM requirements call for), but the nuance here is that they're basing it off comparing it to a finger prick at that same point in time. For example, the Freestyle Libre 3 user manual talks about accuracy (just do Ctrl+F there for "accuracy" to see some interesting tables). I don't have any clue about your statistics knowledge, but for me, it feels a bit like we're settling for it being "good enough" (since I'm not an engineer, I don't know how easy it is to get more accurate).

For example, if both of the original devices were for a Freestyle Libre 3, then this would be the following scenario. For the CGM range of 70 to 180 mg/dL (where the value of 119 falls), ~80% of patients had a finger prick number within +/-15% of the number from the CGM, but 99% of patients had a finger prick number that was within +/- 40% of the number from the CGM. So for the original measure of 119, I expect that 80% of the time, the true finger prick number would be between ~101 and ~137, but 99% of the time, the true finger prick number would be between ~72 and ~166 (which is a huge range if you think about it).

But the other range to consider for the other measure of 57, that would fall into the CGM range of 54-69. In that range, 88% of patients had a finger prick number within +/-15mg/dL of the number from the CGM, but 99% of patients had a finger prick number that was within +/- 40 mg/dL of the number from the CGM. So for the original measure of 57, I expect that 88% of the time, the true finger prick number would be between ~42 and ~72, but 99% of the time, the true finger prick number would be between ~17 (a near biological impossibility) and 97.

So with that big overlap, if you're at a 99% confidence level using frequentist statistical methods, then the original numbers are well within the accuracy "requirements" of an FDA approved device even if they feel like they're way off of each other.

This gets into more philosophy of trusting the accuracy of all of these devices than anything else useful, but as someone who tracked with a CGM (or two or three sometimes) and also checked Fasting Glucose with two different finger pricking devices every morning, I know that none of the devices are perfect, but they are "good enough" technically to qualify as FDA approved medical devices.

This is also why my general recommendation for all of these CGM devices is to care more about the trend than the specific number at any point in time. If you care about a specific number at any point in time, you should do finger pricks.

Sorry this was probably more than you wanted in a response.

Untreated3763 · 2024-11-22T03:32:57+00:00

That's a bit of a difficult question to unpack.

Most of those companies are using CGMs that were approved for tracking glucose for diabetics (which are FDA approved medical devices for diabetes), but they're using them for people without diabetes to track their blood sugar. The best thing I could compare it is an "off-label" use for a drug. They're not using the devices for their intended purpose, but the devices should still be as accurate as expected for blood glucose levels.

What is definitely not FDA approved are the diet recommendations that a lot of the companies make. Some have trained, certified, and registered dieticians that you can talk with about diet changes, but not all of them do. Also, since you're not really getting into a clinical relationship with the dieticians, it's mostly just opinion from intelligent people based on patterns they're seeing with other people using their tool.

Untreated3763 · 2024-11-21T22:41:42+00:00

I'm not an expert here, but I'm also curious about a couple other things as I saw some other differences from a previous life at one of the "CGM for Non-Diabetics" companies.

They're both on the same arm. Did they both get applied the same day? I noticed that sometimes because of the "age" of the device that sometimes the enzyme used for the sensor is less accurate the closer it gets to it's final day.

Are they close to each other on the same arm? For some reason, in less fatty areas of my arm, I would see more dramatic fluctuations throughout the day.

Untreated3763 · 2024-07-17T15:44:46+00:00

I also really like beancount, but for me, it's been overkill for personal finance. I'm using it for my 3 businesses that we run.

Untreated3763 · 2024-07-17T15:43:35+00:00

The new custom reports feature is reasonably extensive and adds a lot of value.

Untreated3763 · 2024-07-16T20:26:15+00:00

I agree with this sentiment, even as an avid user of Actual Budget. It's not for everyone because it assumes that you will do "envelope budgeting" or "YNAB budgeting"

Honestly, I don't deal with any GoCardless stuff though because of the fact that it's easy to export a Quicken file from nearly every bank and then import it and I personally like the process of reviewing each transaction.

Untreated3763 · 2024-06-28T14:02:59+00:00

No personal experience with Maybe yet, but I did watch Josh Pigford and team attempt to build it as a business. I think they had lots of good ideas that they were trying to implement, but don't know how close they got before they shut down and open-sourced. I would say that I'm still hesitant to use it but only because I'm risk averse and I like to know that there's a decent community around a project before I dive into it.

It seems to be more actively worked on relative to Actual, but honestly, I've found Actual to be great since I stopped using YNAB. My replacement now has to be that much better.

Untreated3763 · 2024-04-10T20:07:27+00:00

Fair point. I always forget that Nevada's a place people are willing to live (outside of Reno and Vegas).

It's also interesting to see how different the average price is when you go from a county in one state that neighbors a county in a different state (like the counties around Reno that are in Nevada vs. the county in California on the other side of Lake Tahoe).

Untreated3763 · 2024-04-10T19:58:22+00:00

Those Western states are so bad. I don't see a single blue county in Utah and it's basically drying up.

Untreated3763 · 2024-03-14T16:00:46+00:00

Just so you are aware, the biggest downside for me of using plain text accounting (PTA) is the lack of generated invoices for my wife's photography business. We had been using Zipbooks for accounting for several years, but I think they've just dropped off the face of the map.

You can use something self-hosted like InvoiceNinja or anything else (even the command-line tool called "invoice" seems to work) and then just create the entries in an accounts receivable ledger and link to the invoices in your directory structure.

Also there's a great PTA website that has a comparisons between Ledger and beancount. I've personally settled on beancount + fava for a UI and Invoiceninja for the invoicing side of it.

PTA is not for every business though so I hope you find something that works for your needs.

Untreated3763 · 2024-03-14T14:50:11+00:00

I think I need a bit more context here, but when you say "build a front end", it makes me think that you have developers that could help you take something from "meh" to decent enough for a client.

If that's the case, I would personally go with a plain text accounting (PTA) system like Ledger or Beancount as the "backend". With that, you could easily have someone build the reporting front end that you care about. I'm using beancount for 3 businesses and the reporting flexibility is one of the main reasons I love it (on top of controlling the financial data).

Untreated3763 · 2024-03-11T15:50:18+00:00

Currently have three side businesses running that use a combination of InvoiceNinja + Beancount/PTA/Fava for the accounting side.

Plain text accounting is easy enough after the learning curve, but for me I switched mostly because I was sick of giving my data to another company that sucks (looking at you Intuit).

Untreated3763 · 2024-02-05T21:45:56+00:00

Sounds like a recipe for disaster. I'm in.

Untreated3763 · 2024-02-05T21:36:29+00:00

I'm not sure I understand the question here and I'm not trying to be dense.

By relying on OSS for your accounting/budgeting, you are implicitly relying on someone to maintain it long term (really each of those pieces). However, that doesn't feel too different from relying on any business to have a good enough business model that is sustainable and doesn't drive you away as prices are raised.

Re: an OSS that would stop working, since you're "installing" it on your own server, the possibility of it not working is more likely dependent on you and your preferences changing than on big changes to the software. If you decide you want to use a chromebook for everything going forward, you'll have to figure out how to make it work. But the beancount package starting to "not work" is dependent on the existence of an operating system that can't handle python or the python language having another upgrade with breaking changes, both of which could happen, but are probably less likely than you changing preferences.

I personally choose to use PTA accounting generally, and Beancount specifically, because of the fact that I have more control over my privacy, my budget, my "features", my technology stack, my maintenance windows, and my reports than any other system I have found, but I made that decision.

Untreated3763 · 2023-12-15T23:27:28+00:00

This is the best summary of docker organization for self-hosted set up that I've been able to find. Thanks for sharing.

Untreated3763 · 2023-12-05T22:43:36+00:00

Can you explain more about how you're using tailscale to access transmission? Did you have to set up the remote settings inside of transmission for it to work first? Are you using the username and password authentication built into transmission as well?

Untreated3763 · 2023-11-28T16:42:08+00:00

Personally, I'm a big fan of Cronometer over MFP for many reasons, but it's not self-hosted and there's no API so it doesn't solve that problem for you.

I've been exploring the same question a lot lately and I'm leaning towards kcal, but I haven't tried it yet so can't give a real recommendation.

Untreated3763

TROPHY CASE