this is fun but doesnt really say that much.

its not like they instantly reviewed their own docs; the hiring bar and comparisons changed

possion distribution is what i learned in university for describing this kind of event?

the book is underutilized?

No I learned it in university like most of us did but 10+ years in tech I have never once seen somebody reach out for it in situations like this one where it is a natural fit.

Few people understand it well, even though it's effectively a binomial distribution (easy to grok) but with special constraints.

thats just the same problem though, ig you arent using it regularly you are going to forget that part of your shell functions

1. Develop the instinct of "I probably have a shell function for that, if it isn't already obvious; and if I don't, I need to fix that"

2. Give your shell functions a common prefix, and/or big-endian naming convention (e.g. things that help you with git start with `@git-`)

3. Tab completion is your friend.

I wholeheartedly agree that it's the same, but I fundamentally disagree about it being a "problem", or at least, one worth caring about. I don't honestly believe that typing out the extra 35 characters that are filled in by the helper function I gave here would solve anything that comes close to the convenience of not needing to memorize them.

i guess your difficulty is that half the commands i can write off hand and the other half i cant, and i only really care to understand the parts of the data model that i actually touch.

like, i dont really need to know all the stash details when i only stash one thing at a time, very temporarily

i also dont really care to know all the origin and remote definitions stuff when i only touch it once per project or so.

i could certainly draw graphs of what different git repos look like, but what makes it salient to know the rest of the details unless im actually building git itself? if youre using every git feature regularly you're probably doing something wrong

Your comment hits the nail on what I wrote.

I couldn’t care less about stashing commands.

I do care about … if someone understands origins and not by definition because developer needs to know what is his local version and what is on the server and how those two affect each other. Bonus points if they understand server is not special in Git and their colleagues copy on their laptop can be origin as well.

Drawing graphs of what different repos look like? That’s irrelevant.

Irrelevant if one understands that Git uses DAG and is content addressable store.

You see someone might know those hard words but when working daily with Git reasoning about rebase or merge, cleaning up their own work with interactive rebase, making pull/merge requests or resolving conflicts it is much easier if one knows what is local what is remote and how Git stores data.

You also learn it once. In my 15 years of using Git I basically didn’t learn much new commands but having mental model of how it works was my tool to fix any problems other people had. Knowing commands or definitions is secondary.

> like, i dont really need to know all the stash details when i only stash one thing at a time, very temporarily

If I were hiring, I would care about whether you can `git help stash`, skim over it (bonus points for actually using the pager competently) and figure out what you need to do.

but in actuality, its all about how you use it.

you can dump your thoughts and constraints you can think of, and have it work through untangling, or use it as a summarizing notepad, or yo prototype what you are thinking about in different variations.

its no replacement for pen and paper, but no typed or drawn on tablet picture comes close to a real notebook to scribble on its entirely a thinking tool, as much as a skip-thinking tool

sounds like an easy buy, if it wasnt already way expensive.

i guess we'll actually find out if he gave away useful nvidia secrets in years from now, but by then the tech might not matter all that much to Nvidia.

he was cheating on his wife before now, and Nvidia was doing just fine

A forward PE of 11 ain't expensive. It's the cheapest it has been in a decade.

do you have a count on how many times claude has committed that file?

i bet most of the commited ones were done by claude because nobody else us gonna care to make it

so i guess the main safety aspect of anthropic with regards to ai is that theyre trying to speedrun some other disaster instead?

I suspect the rational calculus is that if you abscond with billions while destroying the planet, the billions will protect your for the remaining 80 or so years of your life. Which is of course safer than not having the billions in the theoretically inevitably destroyed planet.

This is how you get concrete poured down your doomsday bunker air ducts...

i don't know how much of it has been thrown out/superceded, but Thinking Fast and Slow would suggest it actually makes you slow down to think about the material, rather than jumping past.

"Force you to think" as long as the meaning isnt changed, isnt a bad thing

It is when the forcing results from negligence rather than deliberation. In those cases, you're not being confronted with an alien, difficult, or profound concept? You're being given a broken version of a boringly ordinary concept, and wasting your brainpower on papering over an orthographic or grammatical crack that should have been cleaned up by the author, or the editor, or one of the test readers.

In these cases, you're not thinking about the material; you're thinking about carelessly it's been put together, and how little regard the author appears to have for the audience.

The piece makes the point that a novel is about immersion in the text. Slowing down to think about the material is the opposite of the goal

Spelling errors (especially in professionally published text) break my suspension of disbelief or train of thought and make me question both the author and editor’s language abilities. That’s not the kind of thinking I set out to do when reading.

Not sure about that. I mean, you misspelled “superseded” and this prompted me to take some time to write this reply. Maybe I will remember your point better for so doing, but is it really the best way to reflect on the topic?

youve missed the joke, that the descriptions used to be swapped

Well, I mean, they still are for most of the public.

Sorry - I think you're right. I had a hard time telling with several of the early comments in this thread. (The new ones are more serious) What's that rule about it being tough to tell on the internet?