I understand the bummer that warfarin can be. I have two pieces of advice.
1. Don’t diet the dose, dose the diet. In other words, don’t try to adjust what and how you eat to fit the mg of warfarin you are taking every week.
2. I believe a large percentage of what you hear regarding warfarin is ridiculously overblown and I almost never place limits on what I do because of some fear of a bleeding event (within reason, of course.)
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.
If you have a PHP application and have found that Ruby allowed you to scale or vice versa, it probably just means the skill level of the dev decision makers improved. There are a lot of gotchas and pot holes one can find themselves stumbling into that you really only have to start caring about once you are actually at the point where scale matters.
This I 100% agree with. The parent post was essentially that Rails doesn't scale and "everything else scales better".
Most battle tested languages and frameworks can be adequately scaled if you have the right devs. I think that a lot of the reason we see system rewrites due to scalability is more because startups tend to hire developers that like to "build new things fast" and those aren't necessarily the same as the developers that have already dealt with 1M+ users at petabyte scale.
Once you become that successful sometimes the solution is to bring in people that have solved these problems of scalability previously. This sometimes results in rewrites in whole or in part because their experience is on a different stack.
In one of the PHP to Rails (for scalability) projects I worked on I was contacted quite early in the process. I am a longtime friend with one of the business owners. The existing developers could not scale the product horizontally and were already on the largest instances available at the time so there was no more ability to scale vertically.
They had hired a new technical lead that had extensive experience scaling Rails, but most of the team only knew PHP. My team did both Rails and PHP consulting at the time and we were hired to speed up the rewrite in Rails while the PHP devs were doing a mix of trying to keep things running and learn Rails so they could support after the rewrite.
The first thing I did was review the existing PHP codebase. I then advised that they not switch to Rails because I firmly believed that in about 3 months the PHP version could be refactored to allow for adequate horizontal scalability. The full rewrite was expected to take a little over a year.
The owner agreed that my assessment was probably right, but he still opted for the rewrite because the new lead was competent at scalability and likely would have quit if they stayed on PHP.
I’ve noticed quite a jump in PHP composer package spam recently, too. A lot of just ever so slightly renamed popular packages. A couple even had quite a few stars on their repo.
It’s not easy to stalk animals built to spot predators — especially in the terrain where I’ve seen modern persistence hunters.
Many watering hole types of animals also don’t just fall right over after being struck, particularly with a “rudimentary” weapon. Even if you get a decent shot off, you will still most likely be chasing it for quite a while. Not to mention the dangers of what’s hanging around, looking to take what you (hopefully) managed to score.
