These statements really ring home when i'm thinking about my 20s and coding.

Back then, i'd dive right in, start coding, prove what works, figure it out as I go, then have to adapt the existing code to the figured out design. I was much more attached to that code and didn't want to lose it. Today, if I write code, I plan it out, have a good idea of how the pieces will work and then go implement it. And honestly, if the code gets thrown away, it's not the end of the world.

Code is really a small portion of what engineers do...