volume

neat details shared, might check out later.

Does this apply to Brave browser?

I think you need to go past this common thinking to "just focus on consistency/habits/discipline". You need to get clear about how/why you decide in the present moment. I assume this takes varying amount of time/effort for different people.

I think one needs to unravel our inner state and psychology ... we cannot simply turn on and off. But then, once we understand our inner state/psychology it makes it easier to turn on/off.

> Why does this article claim to know that Twitter might go down due to cost cutting? Isn't there a possibility that their infrastructure is just hugely wasteful?

I see the authors (Sheila Dang, Paresh Dave and Katie Paul) quote "sources".

I agree "elaborate" is the keyword but for a different reason. He doesn't elaborate about what he considers "elaborate" so we have to fill in the blanks.

When I read it, "our most provocative thinkers and writers" made me wonder:

- Given any system don't you have a range of rigid versus loose followers? This looks true from my own observations of the note talking community. - Couldn't normies those who are not "our most provocative thinkers and writers" get value out of such systems? - Is Sasha aspiring to be one of "our most provocative thinkers and writers"? He wants to make his mark on the world so part of this writing is self talk.

Sasha accomplishes his goal. it's provocative writing and has produced a decent HN response. I have no evidence he means what he says because if so, it's a topic of personal preference. Fun and interesting but not immediately valuable (to me).

> A new 500GB hard disk is already in dispatch with Amazon

What if in fact Amazon uses EMC gear underneath

eisenhower matrix and cynefin framework

I had to re-read this a few times. I think you should go 100% full effort with double negatives and rewrite the last part:

> There is no noise here, just socially acceptable noise.

Can you share more about your awx-operator and/or k78s pains? I was tinkering with it this weekend and I'd like to compare notes. I got the basic install via kustomize working just now, because I got stuck with the helm-based method.

I wish all PMs would go on call for a week at least. The OP's stint with on-call will be quite useful in his career since he can better intuitively view infrastructure more holistically. Then if the group is doing sprints, the "firefighting" will more easily get prioritized.

Most places at some scale have some meaningfully defined escalation path. That way you staff people with varying understanding of the system(s).

> This can obviously be fixed with good documentation, but in reality, no one has good enough docs.

One problem I've witnessed related to documentation about on-call issues is the over reliance on the SOP concept. They only commit to one level or one pass of analyzing the issue. They do not future drill down, either by linking to other notes or reviewing the issues deliberately. It's like they read about the 5 Whys and decided why not just 1 why.