semitones

This seems highly cynical. If the current company means practically nothing to them, why would they be bothering with it at all, especially given that they could be doing almost anything else they wanted, given their generational wealth?

Yeah I dislike it when people just paste chatgpt outputs. If you use ChatGPT, you should (imo) use it to _help_ you write your own response - it's output is similar to a Google search, and you use that info to edit your own response

> Having decentralised authentication means that onboarding and offboarding need to have a bunch of tedious manual steps, or custom automation.

Furthermore, SAML SSO alone does not save you from worrying about this, ideally you'd also implement SCIM, to have actually automated + real-time identity updates, which is yet another protocol separate from SAML.

> I got an email from Bumble a few years ago that said I was in the top x percent of people swiped on.

Was this humble brag relevant to the rest of your point?

not every comment needs to be inclusive

at this point it is an old problem set, the solutions are everywhere and easy to find, at the very least for the first 100 problems. for those problems (at the very least) it is the responsibility of the participant to not look at solutions.

If you're running a popular company then people will easily have a good understanding of the ballpark of your net worth anyway

This sounds like human-generated nonsense

Brilliant!

In my experience, the way to solve [1] and [2] is to design a game state that can also _fully_ describe the state of the UI, including animation cues.

This gave me a chuckle too - such a familiar experience

He responded to you because he thinks you can still be saved

Do you actually understand what's going here?

Kubernetes has a steep learning curve, and certainly a lot of complexity, but when used appropriately for the right case, by god it's glorious

When I need to understand a personal experience, or digest a problem I'm working on, I often talk to myself and record a voice memo. I rarely listen back to the voice memos (although they are super nice to have as they serve as a historical archive of my states and progression as a person), the main benefit is in having the conversation with myself.

By forcing myself to verbalize what I am thinking and feeling, I always end up better understanding it. If I am dealing with an unpleasant situation, I can always find a way to feel better about it, or create a plan that I believe in, if I talk about it with myself.

Really, it's a form of therapy - it's not too dissimilar from the exercise one engages in with a therapist, except of course in this case you don't have a professional that can react to your outputs. Instead, the onus is on you to check yourself and self-process, which is very powerful (although of course there are limits to what you can achieve in a vacuum).

I find it effective to first elaborate upon my perspectives this way to myself, and only then share them with friends afterwards, such that they get a more cohesive presentation.

On HN, if a post is paywalled, and someone posts a link in the comments that is similar to the post, or to archive, then in my experience 100% of the time it's been an unpaywalled version. Doesn't need any explanation on HN

100%

I suppose it doesn't matter if it is a human, or a bot delivering the message, if the message is boring

This made me laugh _really_ loudly, thank you

How do I wake up and escape the matrix? Please teach us master

I wonder if saying that "it's all encoded in DNA (which is only 6 billion bits)" is accurate. Every time life (considering only humans for now, to simplify) arises, in addition to the DNA (the "code"), you also have the rest of the first cell (the zygote), which already has an "expression" of that code (which may contain additional information beyond what is already in the code), + the entire environment of the mother (which obviously provides additional information).

This makes me think that we need far more than just 6 billion bits to actually encode the entire process of new life formation (each instance always piggy-backs off the previous, and always provides processes/information).

> I don't like the rule where it's any part of the athlete's body first to cross the line, it should be the first athlete to ENTIRELY cross the line, no part of them still remains before the line, not even their trailing foot.

What's the difference?

> to approach native performance.

The same way one "approaches the sun" when they take the stairs?

I, like many others here, echo this sentiment. While I disliked working in ads, the experience of working with that repo+tooling is unmatched by anything else in my career.

There is science that supports the cognitive benefits of walking, that much is true

Aren't all tools, essentially, just one API call away from "leaking data"?

The last line made me emotional. Thank you for sharing this story, it was well-written. I'm sorry for your loss.

> I also think legitimacy by proxy is gross

I disagree, legitimacy by proxy is a very useful initial signal. Someone who works on the gRPC team at a large API distributor is more likely to have better advice on best practices for protobufs, than someone who works on optimizing ray-tracers for TempleOS. Relying on proxies, and likelihoods, is crucial for the timely processing of information. We heavily rely on at least some level of trust - otherwise we would have to completely verify every single thing that anyone says, before we can begin to do anything with the information.

I see your reasoning but disagree with it being an example of the shirky principle.

Even once you get "really fit" you don't stop needing the gym, so I don't think "prolonging the need for the gym" is something a gym can actually do, or would want to do. If anything, it's the most fit people that have the most consistent gym habits.

On the contrary, to go off on your example, it might actually be _against_ the gym's interest to serve high calorie smoothies, the reason being that those pursuing a calorie deficit are likely to become discouraged by the lack of results over time, and would be more likely to abandon the gym altogether.

Gyms are usually optimized for weightlifting and equipment-based exercises, which typically lean more towards performance and hypertrophy/strength training, in which case you need high-calorie nutrient-dense foods to be able to actually see results.

However, yes, if you go there for a Zumba session to try to lose weight and then you have three smoothies, you are still gonna be gaining weight. (I'd argue this is still _not_ in the gym's best interest)

It might be the case that, the "hotter" the code paths that you're writing are (the more they get executed), the more difficult it is to write that code, where as for "colder" paths (of which there are so many more), the code isn't as difficult but there is a lot more overhead of managing complexity, business priorities, process, communication, etc.

Linux kernel code is probably some of the hottest code on the planet, and the developers/community understand that contributors need to be able to do exactly what you are doing - spending months toiling over a few hundred lines, and making sure that they are as perfect as can be, because literally billions or even _trillions_ of systems will depend on that code path. It is understood that in order to get it correct, performant, and maintainable, there is no other option other than to have a skilled developer take on a very high cognitive load in order to correctly implement the task.

For colder code paths, like business logic (e.g. customer registers, happens "once" per customer), that logic evolves with the team, the team evolves with the company, the company evolves with the business, the business evolves with the market, which evolves with the world. The code might be pretty simple and easy to write, but the conversations around priorities and complexity and "why are we doing this" take up the lions share of the mental effort around it. Also exhausting...

TLDR it is much harder to write systems code than it is to write python code that makes a call to an API and saves a record in a database, and working on the former _perhaps_ gives you more opportunity to be shielded from typical "software engineering" toil of business communication.