FinnLeSueur

Thanks for the message! It's always nice to hear from others in the same position.

Re sport: I'm not too concerned about it, honestly. I do a lot of backcountry adventuring, rock climbing and pack rafting and I'm not about to stop because of an elevated increase bleed risk. I won't push it right to the edge, but I'll keep enjoying life.

Re diet: I agree! Drastically altering my diet isn't something I particularly want to do. I'm quite happy to adjust my dose as necessary.

Yeah, absolutely! I hear it whenever the space I'm in is relatively quiet. I also hear it a lot while wearing earbuds and listening to something, especially while walking. I presume it will be quite loud when I get back to running, but perhaps it'll be covered up by the sounds of my suffering.

As for the annoying: nah. It never bothered me, although I've been told that some people find it hard to get used to. Apparently, I made a groan of realisation in ICU post-surgery when my partner described the high pitch metallic clock/watch ticking noise to my parents to help them identify it. My partner pretends to be annoyed by it, but she doesn't _really_ mind.

I (29) had my aortic valve replaced (On-X mechanical) and an aortic graft done literally 8 weeks ago. The full procedure is called a Bentall[1]. It's pretty wild.

The mechanical valve was the best option for me as an active young person because it should last my whole life. Tissue values wear out in about ~15 years from what I've read. Sometimes closer to 10 if you are an active person. The warfarin and INR management is a little bit of a bummer, but I was provided with an INR testing device free of charge, which was rad.

I also wrote a blog post[2] about some of my experiences, although I've yet to write anything about the time post-op.

  [1]: https://en.wikipedia.org/wiki/Bentall_procedure
  [2]: https://finn.lesueur.nz/posts/a-heart-murmur/

If you open the article you will find this as the 4th paragraph:

> So, a lengthy discussion began about what to do instead. Earlier this summer, the CSSWG debated between Option 1, Option 2 and Option 3. Of those, Option 3 won. Since then, two more options have been proposed, Option 4 and Option 5. If you remember various details discussed across 53+ issues, put all of those older ideas aside. At this point, we are only debating between Option 3, 4 and 5, as described in this article through the set of examples below.

The article states:

> ... to ensure that an up-to-date version of our dataset is easily available for those who need it, and will work to improve its readability and reduce its size so there is less friction for end users...

I haven't read the article - only the abstract, but it does report: "No perforations or screening-related deaths occurred within 30 days after colonoscopy." I guess something could have happened later than 30 days but we'd need the full article for that.

Interestingly, SAP is used by the metal health services/psychology of my local District Health Board. It gets a hilariously bad rap for its usability, but I presume it gets the job done well because they're still using it!

It does, notably, have an integration problem because the rest of the DHB services don't use it.

That does seem aggressively high. Alfred (MacOS), which this appears to take some design hints from, idles at about 49mb and 0.0-0.1% CPU usage on my Macbook.

Oh man, Welcome to Night Vale is fantastic. I’m glad to see a reference!