Been buying mullvad for the last 4-5 years but oftentimes I can’t even browse the fucking New York Times website due to low bandwidth, let alone stream anything. At this point, I just keep adding time to my account just in case, without using it.

This. No more juniors, and the skills of the seniors is going to atrophy when all they're doing is review and "move around" code an LLM spat out.

> jack up premiums by 20% unless you force employees to change their password once every 90 days"

Always made me judge my company's security teams as to why they enable this stupidity. Thankfully they got rid of this gradually, nearly 2 years ago now (90 days to 365 days to never). New passwords were just one key l/r/u/d on the keyboard.

Now I'm thinking maybe this is why the app for a govt savings scheme in my country won't allow password autofill at all. Imagine expecting a new password every 90 days and not allowing auto fill - that just makes passwords worse.

> AI to run in loop, fixing compile errors, fixing tests, do builds, run the app and do API calls...

Ah I really wanna trust AI won't "fix" the tests by commenting out the assert statements or changing the comparison inputs willy-nilly. I guess that's something terrible human engineers also do. I review changes to tests even more critically than the actual code.

Oh the sha-256 hashes are precisely what I used for a quick script I put together to parse through various backups of my work laptop in different places (tool changes and laziness). I had 10 different backups going back 4 years, and I wanted to make sure I - 1) preserved all unique files, 2) preserve the latest folder structure they showed up in.

Using sha256 was a no-brainer, at least for me.

For better or worse, I have a habit of clicking the touchpad or a few keys after I shut down my laptop. Just to make sure it's shut down properly. Back in Windows days with HDDs and hibernate, laptops sometimes took minutes to shut down completely, and I don't like closing the lid before shut down is complete.

Now, I end up restarting with that mere act, and have to long-press to shut down again because the shut down option won't show up on login screen.

> shut down option won't show up on login screen.

It does. At least I can see it on my personal MBA and work MBP. To right corner

India basically has this - when creating subscriptions, merchants typically create "mandates" which specify max amount permitted per month, frequency, and duration.

Afterwards, 1) if per month amount is greater than a regulated threshold, manual confirmation is needed. [ This is friction ] , 2) cancelling can be as simple as going to your bank's website and deleting the "mandate".

In all honesty, this is probably a really balanced approach, but the roll out was a real pain, with banks and merchants collaborating on who supports whom, etc. International payments got screwed completely - to this day, I can't subscribe to nytimes, after almost 2.5 years of this.

(A good summary - https://support.stripe.com/questions/rbi-e-mandate-regulatio... )

2100 clusters, 16k nodes, and data is replicated across every node "within a cluster" with nodes placed in different data centers/regions.

That doesn't sound unreasonable, on average. But I suspect the distribution is likely pretty uneven.

(Speaking as an Indian engineer)

Hate to generalize, but this has less to do with "Indian style" but rather adding a lot of fluff to make a problem appear more complex than it is, OR maybe someone set a template that you must write such and such sections, despite there not being relevant content. [ Half the sections from this article could be cut without losing anything ]

In this case, the _former_ really shouldn't have been the case. I for one would love to read a whole lot more about rollback planning, traffic shifting, which query patterns saw most improvements, hardware cost optimizations, if any, etc.