Reminds me of the quote by Kent Beck (allegedly):
"Make it work. Make it right. Make it fast".
First throw something together that works, then refactor it to make it "right" (clean, readable etc). Finally optimize it if it's necessary.
Like the author of this article describes it "Write more bad code. [..] Get answers. Learn as much as you can about the problem you’re trying to solve [..] it’s much faster in the long term to write bad code then make it good, than to try to write good code in the first place" https://medium.com/swlh/coding-faster-make-it-work-then-make...
First throw something together that works, then refactor it to make it "right" (clean, readable etc). Finally optimize it if it's necessary.
Like the author of this article describes it "Write more bad code. [..] Get answers. Learn as much as you can about the problem you’re trying to solve [..] it’s much faster in the long term to write bad code then make it good, than to try to write good code in the first place" https://medium.com/swlh/coding-faster-make-it-work-then-make...