"Don't worry about writing perfect code, rather make it work somehow, perfection will come later." I think your advice is true, esp for education and Worse is

"Don't worry about writing perfect code, rather make it work somehow, perfection will come later." I think your advice is true, esp for education and Worse is Better effect. I think the follow-up is wrong for two reasons: 1. Useful code tends to stick around long time getting extended more than refactored for quality. 2. Due to the methods involved, the highest, quality designs usually need to be designed for that upfront. Certain decisions will favor reaching the goal. So, my advice for high-quality outcome is to design for it with simple constructs, straight-forward composition, and plenty of docs made on the way. Gives someone a better start if they want to try to perfect it years down the line.