You spend forty minutes figuring out why the vertex normals on your mesh look wrong. You find the cause. You fix it. You move on.
That forty minutes is gone — but the solution doesn't have to be.
The problem with written notes
Most 3D artists keep some kind of notes. A text file. A bookmarked forum thread. A Confluence page that nobody has opened since 2021. The problem with written notes is that they describe a solution rather than showing it. "Go to Mesh Display, make sure Soften Edge is applied before baking normals" is correct, but it is also easy to misread, easy to misremember, and completely useless to someone who doesn't already know roughly where to look.
A three-minute screen recording of you doing the thing is worth ten pages of that.
What the video above is
It's a recording of a Maya session — a polygon sphere, vertex normals visible, a specific display and mesh state that kept causing confusion. Not a tutorial. Not a course. Just a recording of: here is the problem, here is where the option lives, here is the result.
That's it. No intro. No outro. No chapter markers. It starts at the problem and ends at the solution, because that is the only part that matters to the person watching it at 11pm trying to get a mesh ready for rigging.
Why specificity beats comprehensiveness
There are thousands of Maya tutorials online. There are very few recordings of someone solving the exact weird edge case you ran into this afternoon.
The value isn't in covering everything — it's in covering this thing, clearly, with the actual mesh and the actual settings visible. Specificity is what makes it findable and usable. A colleague watching it doesn't need context. They have the same context you had. They just need to see your hands.
The habit worth building
Hit record before you start investigating. You don't know yet whether the next ten minutes will be worth capturing, but the cost of recording and deleting is lower than the cost of solving something twice.
Most of the time you'll delete it. Occasionally you'll have something that would have taken a colleague an hour to figure out on their own, and you can send it to them in a Slack message instead. Over a year that adds up to a meaningful amount of saved time and frustration across a team.
The recordings don't need to be polished. They need to be specific, short, and findable. Name the file after the problem. Put it somewhere shared. Done.
Forty minutes of figuring something out is sunk cost. The solution is an asset. Treat it like one.