I've recommended this exact talk many times! It's excellent.

Related (but not identical), Facebook research just released an open source pdf -> markdown reader (that does a good job w/ equations in latex).

https://facebookresearch.github.io/nougat/

I've used it to convert 40 page pdfs into text, and it did an impressive job.

I've had really good results with it so far. I'm using it in the Huggingface Transformers library, and it's been great for my workflow.

I loved seeing his technique. This is a 2 min video of him cutting up a raw chicken https://www.youtube.com/watch?v=xfDsNRXPKE8. He's going slow because he's explaining, but it's so smooth he's still fast.

Can you expand a bit more about what you mean when you say you're a competitive typist? are these in person tournaments?

Yeah! Whilst usually a side show to real events there's a bunch of virtual and in person events.

Two years there was an event in the UK dedicated to typing. Last year the US. Virtual tournaments happen frequently throughout the year. The most famous one is likely the yearly event hosted by Keymash[0].

Octahedron is also a famous player in the scene. He hosts a Discord server for proficient typists and regularly puts on events.

[0] https://keymash.io/

How good is proficient? I just use a QWERTY keyword and my max is 143wpm, usually stable around 115wpm and after 10+ minutes of typing slows down to 100WPM. Is that proficient enough? Because I know of people who type at 200-300 WPM with their custom keyboards

Do people use steno keyboards for this (and why not)? The scores I'm seeing there are certainly impressive for ordinary keyboards but nothing close to the ridiculous records stenographers get.

that seems like it would be against the spirit of the competition. Like entering a car into a marathon.

I completely agree with this. I've been working on my own 30 day challenge to boost my typing speed, and the reason is similar to what's stated in this article: it's about latency, it's not the seconds saved.

It's mentioned in the article, but I mostly think of it as: the faster one types, the shorter the iteration time. When you can type roughly as fast as you'd normally speak, it's a totally different experience than t-y-p-i-n-g each word of a sentence.

I kinda agree, but I've also been humbled time and time again by older devs who literally hunt and peck with two fingers. I even asked one how she fixed so many nasty bugs each week while barely knowing how to type. her response: "I think deeply about problem, then type correct solution first or second time".

You can type quickly and still think deeply about the solution or whatever. Typing fast won't help when you're stepping through the code one line at a time, and it won't help when you're just sitting there with your eyes closed at your desk waiting to find out what to do next. But it is still helpful when you're talking to people in Slack.

Sure, I think the depth of thinking or problem solving is clearly important.

But, I don't think your claim is in tension with the article's claim that being able to type fast lowers a barrier (or provides a benefit) that's more than simply the "time it takes to literally type".

There's more there there.

It looks like it renewed automatically on the 17th every month, and then... it was reactivated on the 20th? I think this lends credibility to the idea that someone on the account tried to watch something 3 days after the subscription ended, couldn't without resubscribing, and simply clicked to restart the subscription. Obviously, it could be as you described it as well.

A simple test would be to see what happens if you try to, today, try to watch something on Netflix. Does it allow you to start watching shows? Or does it ask you to do something like restart a subscription? What do you see today?

Very nice! I've been a fan of your other data viz gallery work w/ python especially. I love how clearly you explain how to build up these results as well.

Thanks! Glad to hear this!

Which part of the horizon of the ocean was lower than another? I'm asking if looking East would be higher than South?

This was looking west, and left part of view was lower than center oart. On right side of the view the ocean was blocked but I expect it to be lower there too (so highest in center of view)

You state in the top level comment that this claim stains the article: "Stating that git breaks Jupyter notebooks is quite a flex."

But you are saying here: "If you leave git diffs in your files, whether Jupyter notebooks or otherwise, and run/compile them... They will break."

Have you changed your mind in this thread? Or what's your objection?

I'm suggesting that git only breaks Jupyter notebooks (or anything else) if you do not know what to expect from git.

But if you don't know that git modifies files when conflicts, then you're an interesting and rather unexpected audience, I assume.

Meaning that for the typical git user, meaning, knowing about git diffs, the behavior is expected hence not broken. The files end up in an expected broken state, but git does not break them per se.

If you still disagree, let's just settle that we disagree and be done with it.

There could be a time advantage, where the probability weighted expected benefits of starting N years ahead of time is much larger than the sum spent preparing.

You could think of it as purchasing an option, which businesses definitely do.