Yes yes yes. When I&#x27;m coaching junior developers (or developers that like over engineering) this is what I try hammering home more than anything.<p>If you looked at my code at 10-70% solution complete you&#x27;d find so many egregious DRY errors, magic values (likely with a comment above for my own memory), functions that are too long, and a whol ball of mess. If you looked at it 90-100% complete it would be nearly unrecognizable in writing style to what you saw earlier.<p>Figure out how to solve the problem first, spend all your efforts on that, then figure out how to clean up your code and make things nice&#x2F;performant&#x2F;secure&#x2F;etc.<p>I&#x27;ve found that as I&#x27;ve gotten better my sloppy is better than a lot of people&#x27;s clean, which means I&#x27;m spending less time on cleanliness, and getting done faster.