3 ms·

Progress over perfection is what I keep telling myself all day. My brain automatically goes on to investigating something else when I’m faced with my projects.

Progress over perfection is what I keep telling myself all day. My brain automatically goes on to investigating something else when I’m faced with my projects. “Oh wait how do we get our terminal to look that cool?”. I’m working on my first project involving a DB and a CRUD Java program that will talk to a website, potentially. I am too concerned about “am I doing this the right way”? Things like how I’m setting up my db table, or “is one is enough or I should use more”, if people will look into it and say “wow this guy is dumb” or whatever. They all prevent me from just pushing forward and improving later. I’m too scared of someone telling me to fix shit even though I actually enjoy learning so much I’d probably like that. I wish I could just go in my brain and turn that off, I’d be living in the future.

beaconstudios 6y ago
I've made this mistake in the past, but I don't any more. The difference is that rather than closing my feedback loop over the code/architecture itself (so the cycle of working is start feature => code => look at code => code, which obviously never leads to starting new features), I close the loop over the experience (becoming start feature => code => use/test the feature => start new feature). This way your focus is on the product and your working cycle involves incrementally adding features, not navel-gazing at your code. So basically, bring yourself out of the code and actually try the product whenever a feature is done; context-switch from coder to user.