Andrej Karpathy

And so you're not going to be bothered and you have solid chunks of time to do work.

So I like those periods, night owl by default.

And then I think productive time, basically, what I like to do is you need to build some momentum on a problem without too much distraction.

And you need to load your RAM, your working memory, with that problem.

And then you need to be obsessed with it when you're taking a shower, when you're falling asleep.

You need to be obsessed with the problem, and it's fully in your memory, and you're ready to wake up and work on it right there.

So I can't talk about one day basically in isolation because it's a whole process.

When I want to get productive in the problem, I feel like I need a span of a few days where I can really get in on that problem.

And I don't want to be interrupted.

And I'm going to just be completely obsessed with that problem.

And that's where I do most of my good work, I would say.

Yeah, basically I need to load my working memory with the problem and I need to be productive because there's always a huge fixed cost to approaching any problem.

I was struggling with this, for example, at Tesla because I want to work on a small side project.

But okay, you first need to figure out, okay, I need to SSH into my cluster.

I need to bring up a VS Code editor so I can work on this.

I run into some stupid error because of some reason.

You're not at a point where you can be just productive right away.

You are facing barriers.

And so it's about really...

Removing all that barrier and you're able to go into the problem and you have the full problem loaded in your memory.