Rimworld Dev Tracker

Image at original resolution:

Soon...

This guide on contract writing could also be a guide on how to write a game design.

Almost every single point applies: Single-topic paragraphs, whitespace, hierarchical bullet points, charts/tables, math examples..

Specifically chapter 7:

Avoiding perverse incentives and data misinterpretation is a decent reason to not put metrics into your game.

Goodhart's Law can't catch you if you don't have the measure in the first place.

Hail the Supreme Gander.

Podcasts are named after the iPod, an obsolete technology.

You used to connect your iPod to a computer to download podcasts, then listen to those while out and about.

We still call them podcasts though.

I think these daily limits highlight what working hard really means in practice:

1. Being consistent through many days and years, not short-term intense effort.
2. Allocating effort on the tasks that best move you towards the goal, not on the tasks you enjoy working on. /5

If I switch tasks, I can do about 1.5-2 of those entire things before the whole brain is too tired.

So if I max out 2 tasks, I can't even do gaming afterwards! I have to fall back to really low-brain activities like feed-scrolling. I hate this feeling of mental incapacity. /4

On a good day I can do:
- Gaming 10 hours
- Coding 7 hours
- Reading (interesting book) 5 hours
- Paperwork 5 hours
- Game design 4.5 hours
- Reading (difficult book) 3 hours
- Article/book writing 3 hours
- Article/book editing 2.5 hours /3

The fatigue is task-specific. Each task has its own gas tank, and burns its tank at its own rate. There's also a universal limit.

After years of self-observation, I even know how long I can do specific tasks... /2

I believe in working very hard when you're trying to do something special.

But after a certain amount of effort, willpower is irrelevant. Like an exhausted muscle, the brain just stops working well. I look at the screen and... nothing comes to mind. /1

I made an Instagram for casual/life stuff