But which “you” matters here? Is it the you of the current moment, next hour, tomorrow, next month, etc…?

Any activity you do regularly and consistently will bring about different emotions and states of mind on different days. Some days you can’t wait to get started and some times you go weeks of having no motivation towards it.

I’m on a journey right now of hiking 50 miles a week. On most days, being able to get in nature for an hour or more is such a serene and grounding experience that brings me a lot of joy. But there are weeks where I don’t want to get out there, and even when I get started I don’t want to be there. But looking back, I see those days as part of the whole experience. I have retroactive enjoyment and pride in having pushed myself (type 2 fun) and I know that the subsequent 50 mile weeks are easier and more enjoyable because I kept the consistency up.

Yes, it is good to take breaks from things when you’re not enjoying them anymore. This allows you to reevaluate and get back your motivating “why”. But it can also be extremely hard to get back into a routine after a relatively short break. Anyone who has not exercised for a few weeks will know that feeling of weakness when they get started again.

I'd argue that the problem when you don't feel motivated (provided it's not because of a lack of sleep, hydration, or nutrition that's making you feel tired) is that you are not learning something new. This is why it's important to vary the location, or time, or who you go hiking with etc. If you add some variety to your activity, you will feel more motivated because you'll get to learn/experience something new, which is intrinsically exciting and rewarding.

For (b), would also be really awesome if they explained how they chose these numbers. Given how specific it is, a salary of 197,819 seems to be derived from some function (e.g. average salary for a senior engineer position in SF).

I believe it is Top 10% salary for a senior engineer position in SF using industry benchmarks. ( DHH used to tweet a lot about Remote )

Heads up, I get an invalid certificate error when trying to visit your site.

> and if you move to a state with no income tax, you might not even lose almost any net income.

If you relocate from NY to a no tax state, but are still basically working for the NY office, you might be taxed as a telecommuter in NY and still need to pay NY income tax.

I'm not sure how this works for a multi-state company like Stripe, but I've had to do this when I transitioned to working remotely for a NY based startup.

Why is it useless for actually protecting users? Is it easily circumventable or is it just that there are simpler attack vectors that don't require modifying kernel code?

Most iPhone attacks that users care about are those where attackers target sensitive user information and exfiltrate it–other ones don't really make sense on the platform. For this, typical attack vectors are a messaging app exploit (which is entirely outside of the control of Apple, FWIW), a web browser exploit coupled with a sandbox escape, or perhaps a bug in a Wi-Fi or Bluetooth driver; none of which typically require modifying kernel code in order to implement. The group of people that wants to patch the kernel, or extend it, is essentially nobody but security researchers and jailbreakers for whom the rationale to do something like this is often "because I should be able to do this". Thus, the feature is ineffective at addressing or preventing actual attacks that users care about and very effective at preventing people from tinkering with iPhones.

I think you're conflating 'attacks possible and thus more often seen in the wild' with 'attacks users don't care about'. People would very much care about exploits that become persistent if those happened.

Attacks against iOS that become persistent do not exist in the wild to my knowledge, nor did attacks that overwrote kernel text. They just do not exist because there is no reason to do this because it's substantially easier to find other things to exploit.

I just don't see how 'preventing such attacks is just to annoy jailbreakers' follows from any of this, though. Like, it's a narrative but the logic doesn't add up to me. There are really good reasons to also defend against complex attacks, attacks that require physical access, you name it. I don't want my iMessages leaking stuff because someone sent it a funny message, I also want my phone to remain reasonably secure if I hand it to a TSA agent.

Perhaps Apple has some sort of model where this is helping, but as it stands this makes the lives of security researchers and jailbreakers annoying and it does not close a hole that previous attacks were using (they are still using the same techniques!) Neither of your examples involve patching the kernel–the first is finding a bug in iMessage in userspace, and the second is handled by an entirely separate chip. My perspective is literally just "I want Apple to prevent exploits against my iPhone, and also not make jailbreaking worse for no reason" and this feature is "makes exploits no harder because no attacker cares that this exists" and "makes jailbreaking way more annoying". There's no balance between the two here, it's just negatives all around.

I didn't say either of these patched the kernel (one is in userspace, the other one is, well, you don't know where it since I didn't describe one) just that the difficulty and complexity of some potential exploit doesn't mean the exploit isn't important both to Apple and end-users.

You were arguing that some of Apple's mitigations are only aligned Apple's business interests and not those of end-users. I don't think you've said much to really show this is true, other than in your specific case. Not wanting the phone to be jailbreakable, to provide some assurance that when you buy an Apple phone, it's running Apple's software as designed by Apple and that it can't easily and surreptitiously replaced with something else is a perfectly reasonable consumer expectation very much in line with what Apple explicitly sells and promises of the product and services it comes with. The 'for no reason' bit just seems obviously inaccurate.

I respect wanting or needing to do this with just the builtin datetime module. For everyone else, I recommend relativedelta from the dateutil package: https://dateutil.readthedocs.io/en/stable/relativedelta.html

e.g.:

  >>> from dateutil.relativedelta import relativedelta
  >>> date = datetime.utcnow().date()
  >>> date
  datetime.date(2020, 2, 29)
  >>> date + relativedelta(years=1)
  datetime.date(2021, 2, 28)

I added to here: https://stackoverflow.com/a/60468711/634824

Thanks.