c0mptonFP

Unrelated means two things are not related in any sense. Orthogonal means two things are unrelated with respect to a specific property.

Unrelated is more general, and less precise. Orthogonal restricts the "unrelatedness" to the specific property being discussed. It's also a very visual and intuitive word.

It's not only HN btw.

You hit the nail on the head, mostly.

> then you read the room and go with the layer of abstraction needed.

Finding the right layer of abstraction is orthogonal to the write-speak axis. When speaking to my colleagues, I use technical jargon that no layman could understand. None of the topics are simple, or strongly abstracted. The issue of write vs. speak is more about the sentence structure, sentence length, and breadth of vocabulary.

But I generally agree that carefully crafted written language can capture and transport thoughts much, MUCH more effectively.

The sole purpose of guns is to harm/kill. Not comparable to ML.

AFAICS the edit history goes back to May 2022, however the site has existed long before that.

Not convinced

She's doing everything in her power to become famous/viral.

Look at the amount of work she puts into SEO and her own Wikipedia page. She's a Wikipedia editor that edits her own page. Can't get more self-absorbed than that.

Could you tell me more about your experiences with effective waiting culture?

I'm having a hard time believing that a e.g. a high-level manager/exec with 20 meetings per day, and a 60 hour work week is able to be on time with a purely waiting approach.

There are so many people that you need to align with this culture. If it worked for you, wherever you are, I respect that a lot.

A developer who doesn't have a holistic view on their systems is a liability.

Ok, next time an engineer on my team can't stop himself from talking about his SIMD lock-free distributed queue, I'll just keep listening. Maybe I get to sleep in the office too.

Without interruptions, I would not be able to finish meetings on time. EVER.

Information exchange is always the bottleneck in larger organizations, so efficiency of meetings is really important.

I will interrupt someone if I understood their point, and we have different, more pressing items on the agenda. It's not a power play, not psychological warfare or bullying. I just want to get shit done on time.

Neither do magnets.

You can have open ledgers without compromising anonymity, via ZK cryptography.

I wish, brother. I wish it was more like that...

It's popular because these war stories you find in blog posts are pure survivorship bias.

If I'd let every fucking team member go on an exploratory bug hunt whenever they feel like it (hint: that would be always) we would never get anything done.

What if they don't find anything? Is this issue really worth 2 weeks of dev time? That's 15k down the drain for a senior engineer, if not more.

> We need more people and companies like this, who are willing to go beyond "oh it fails randomly sometimes" and track down the underlying issues.

I absolutely disagree. Most capable engineers I know have this urge to go down rabbit holes and fix any issue, this is nothing special.

Everyone wants to be the hero that found a bug deep in the stack, make a glorious pull request, and be celebrated in the community.

I much more value people who have enough self-control to pick meaningful battles, and follow the right priorities.