jsharpe

Of course it's incomplete. Any explanation of nutrition that doesn't include mention of at least calories, macronutrients and micronutrients isn't useful for understanding what's actually going on or being able to make an effective nutrition plan.

We don't even know if Homer was real. XD

I can see why people would be irritated by 1 and 2 and they happen to me too, but I have just reframed how I think about them.

If someone jumps on something I'm struggling with, I take it as an opportunity to really pay attention to what they're doing and try to learn. They might just be way stronger, but they probably also have some better technique ideas.

For #2, I just take it as a slightly awkward attempt to reach out and socialize. Advice isn't harmful. At worst it's a mild spoiler (oh well), or just wrong (then ignore it). At best it's a great chance to learn something.

I'm awkward and it's rare for me to start a conversation, so I just take someone else talking to me as an opportunity to connect without having to make the awkward first step, and try to spend a minute or two (at least) talking with the person.

I love when I'm climbing alone and working on something really hard for me and some random people just start cheering as I get near the top. :)

Measuring tech skill by how many tabs you have open is like measuring carpentry skill by how disorganized your workshop is.

I think the real answer is that Sora-style AI slop videos just aren't as addictive as we thought they'd be.

I let my kids have access to the app in the hope they would be inoculated against being obsessed with AI video and it actually worked. They got bored in like 2 days.

It simply doesn't compare well with handcrafted short form videos that are already plentiful on TikTok (which I absolutely don't let my kids watch).

If you're interested in making and finishing a game, there is no good argument to be made for writing your own engine unless you have some very very specific rendering requirements (e.g. you want your game to be in hyperbolic space or something, or have 3D portals).

In every other case by writing your own engine you'll be wasting your time on a million already solved problems instead of actually, you know, making a game.

If you're interested in game engine development, or graphics programming, and not so much in finished games, then you can write some engine code as an educational exercise, though.

> Contrariwise, it's possible (but harder) to have no sense of taste and merely copy what most would regard as "good taste" and be perceived as having "good taste."

Not only possible, but exactly what AI does. :)

Exactly. This idea comes up time and time again, but the cost/benefit just doesn't make sense at all. You're adding an unbelievable amount of complex tooling just to avoid running a simple formatter.

The goal of having every developer viewing the code with their own preferences just isn't that important. On every team I've been on, we just use a standard style guide, enforced by formatter, and while not everyone agrees with every rule, it just doesn't matter. You get used to it.

Arguing and obsessing about code formatting is simply useless bikeshedding.

What a strange position this is (from the link): "the future of work is being more than one deviation from the statistical norm"

This by definition can apply to only 16% of people who are at least one deviation above the mean.

What about the other 84%?

I feel the exact same way. I see a lot of benefits to writing by hand, but it is just so unbelievably, painfully SLOW, compared to my typing.

Exactly my thoughts! Thanks for putting it so clearly.