Sure guidance is great. As much as I was a 14 year old know it all pain in the ass, my old highschool CS teacher taught me the most important lessons of development: memorable variable names, syntax formatting, and saving frequently.<p>However, there were at least a thousand programs I&#x27;d written before and after that involved huge if&#x2F;else and case statements because I didn&#x27;t know better or couldn&#x27;t anticipate growth. Copy&#x2F;paste code littered throughout.<p>All of that &#x27;bad&#x27; code was there because I wasn&#x27;t worrying about making my code good (and barely knew what good code should look like), I was trying to make it work and solve a problem. That bad code made all of us who we are today- someone who starts their coding journey out only trying to write good code will never get finished, and probably give up.<p>Hell, I&#x27;m 33 and have been writing code since I was 9 and am considered a &#x27;rockstar&#x27; developer and architect by my peers (which is probably more of an indictment of their judgement) and I often still disregard the ugly for the path to the solution, then go back and refactor&#x2F;cleanup&#x2F;make portable after I have large blocks of code written. The only difference now is that my ugly is a WHOLE LOT prettier than my best used to be.