All i said is for some people.. the best way to learn about something is to get both hands into it... there is only so much one can read from a book or watch... some people get nothing from that and NEED to be all hands on in order to really make the connection fully and to comprehend it. It's much akin to dealing with architects and engineers.... on paper everything sounds fantastic... looks fantastic.. and should work... but in the actual heart of it, in the physical reality of it, quite often what sounded/looked good can be COMPLETELY the opposite. So it's only a suggestion provide the resources are available to do it with that consideration that IF something were to go wrong, it wouldn't be a loss, the possibility is ALWAYS there, so if a machine/computer you don't care about dying is available to be played with and disassembled/reassembled as a learning tool... it's a great way to do it. Overclocking.. toying with bios settings.... generally buggering up these settings (overclocking aside) won't do harm and can be reset.... however they are time consuming and they do directly impact what can be done on the machine. I just know that out of all the certified and "knowledgable" people building pc's in other businesses, it kinda drives me up the wall when i see a machine come in onto my work bench setup in IDE mode on the sata ports with a SSD... and running in legacy bios mode when the OS and system is fully capable of UEFI (specially today when i see a system setup so poorly... that it effectively boots 10x slower and performance is potentially cut in half due to their poor setup methods giving custom/commissioned builders a bad rep).