maayank

Or, you could have these conversations without OKRs?

For example, is it less sharp to the point of annoyance when looking at text? Or alternatively, easier on the eyes?

Yes, that’s what I do. The way I read the tailscale post it suggested a magical way to circumvent this credentials bootstrapping dance

> Establishing AWS identity outside of AWS is a headache, and often comes with a chicken-and-egg problem of needing to possess a secret to show you are allowed to get a secret.

> For most stuff here, we can rely on the fact that every connection over Tailscale is encrypted and authenticated to an identity

Mm, okay, but you still have the chicken and egg problem of distributing the creds to join your tailnet.

Isn’t it not that different than distributing aws creds to access secrets manager?

Wow, good catch. Forgot about this part!

Private algotrading? Nice. May the odds be always at your favor!

What are you doing with the workstation that it’s worth the cost?

How do you discharge them safely?

I agree to some degree, it’s a question of extent. If you sell a very specific feature that no one else will use for a 20K annual revenue customer, then it’s not obvious at all it’s beneficial to the company at large. Personally I’ve seen too many cases here where individual sales people still campaign for the sale internally, supposedly for the commission.

I was going to write a response and you wrote it all. Especially in SAAS companies, a "strong" sales team in my experience was an hidden fast-track to becoming an integrations company.

How did you discover that blog? If not seen the vim article first, how did you came to it later?

What do you do for persistence? Simply copying back tmpfs to rootfs on shutdown?

I meant what is your advice regarding how to do it well/what you mean by doing it well, precisely because of what you wrote :) apologies for the unclarity

How to fire well?

I like to say "you can't delegate vision"

I’m genuinely interested to hear criticism re: security in openBSD if any one has an interesting link or take

It’s one of those technologies where there’s merit to use them in some situations but are too often cargo culted.

Nice! Do you enforce these 'budgets' in CI or some such? If so, how?

I would consider (sadly) Matsodon as an anti-example. As much as we all know the issues with “the algorithm”, people find real value in automatic curation that I suspect is best served by a centralized authority.

What do you eat for protein in the current diet?

What was your experience with fish?

Board decides each quarter on behalf of the stockholders whether to pay dividends or reinvest profits to increase the potential of future dividends.

What do you mean by 'variety'?

Tiny nitpick, just for reference

> Konrad Zuse Museum in Hünich

I believe you refer to the museum in Hünfeld

> I work in an industry that requires 2 seperate implementations of all critical software components

Very interesting, what industry if you may discuss it a bit more?

> ISPs often deprioritize traffic from S3

I wonder why

Is it a valid use of the issues mechanism? I’ve always seen it as exclusively a bug report mechanism and the rest as spam. Maybe my etiquette here is too old fashioned

What did you especially like in it?

“Developer time is not a KPI and we pay you the same whether you work 160, 180 or 200 hours a month”

Interesting take, thanks

Awesome read. A real life Nathan Fielder (I mean, the “character” Nathan plays)