Hacker News Reader

Comment by ghshephard | Hacker News Reader

One way to opt out of the brownout would have been to switch to new Auth back in September of last year. Or November of last year after the first brown out.

Because the next brownout is permanent - and that will be an even bigger PITA.

I think it's extraordinarily powerful to have these brownouts for organizations that don't make the change when they should have (which was last year).

View on HN

> One way to opt out of the brownout would have been to switch to new Auth back in September of last year. Or November of last year after the first brown out.

The point of the brown out is to help people find cases where they’ve missed this. So “opt out by doing it beforehand” isn’t a viable solution.

The last brownout was a quarter ago. A lot of new things can get introduced in that time that still do it wrong.

So why would it be better to learn about those things when the brownout was permanent?

Seems like very short-sighted thinking.

I think the idea is that once you know what is going on you can opt out, so that you can put fixing it on your next sprint instead of having to drop everything and fix it right now so you don't lose 24 hours of productivity.

I 100% understand that - The point I'm trying to make is- the next "brown out" is permanent - so instead of 24 hours, next time you will have a permanent loss of productivity. I.E. Why are there devices being deployed that are still broken? Because in a few months, they are never coming back until they are fixed.

The idea is to make brownouts increasingly painful - just letting them be a short period of time, or let people "Opt. Out" doesn't service the purpose here - which is to make it absolutely clear that the service is going away.

> Because the next brownout is permanent - and that will be an even bigger PITA.

more like a blackout.

Reply on news.ycombinator.com