Never Solve the Same Problem from Scratch Twice

But this notebook became useful to store not common errors that I couldn't fine solution on web. Normally it is related to some new tech or very specific scenario.

I remember having the same ah-ha in my first year or 2 programming professionally ten years ago.

I started a wiki on a stick or something like that. Lasted all of 6 months.

The same problems don't recur because you get better at stopping them recurring. You become better at root cause, making sure that someone getting the project from version control doesn't have to remember to press button y slowly with their left forefinger, do a backwards roll, shout 'all hail torvalds' 3 times backwards before the build runs.

You also get better at debugging generally, so simply reading the stack trace/error message/error event lets you predict the cause without having to consult your list.