one interesting thing about FAFO'ing my way into things is that I am forced to think about solutions to problems just by observing behavior of my own allocations.

yeh sure maybe I can read it in a book, but idk, it's not the same. I can read the theory, but not grasp the full intuition behind it unless I am experiencing it practically.

"oh this has too much turnover, maybe doing xyz should work better, oh right this guy already wrote about it in his book."

at least for me, I get bored out of theoretical hypothesis too fast, maybe to my detriment but that's just how it is. even when I started learning to code was never about learning the proper way of using this or that structure by watching youtube videos or reading books, but just by building something that was useful for my job and figure out the details along the way.

obviously the big stuff like that takes you out of the game , like proper risk management, might be good to learn the safe heuristics first, rather than blowing up an entire book by doing dumb stuff.

but the optimization details, idk, I just find out why I need them when I am in the game.