loading...

How To Be Productive + Avoid “Analysis Paralysis”

Cubicle Buddha on August 05, 2019

You’re staring at the blank screen and you have no idea what to write. Or maybe you’re staring at a bug in some software you have to fix. Every car... [Read Full]
markdown guide
 

Nice writeup, giving "permission to write something shitty" is really sound advice i think. :)

Code-wise writing something that work like shit is a good way to get a prototype you can refactor and fix into the ideal, rather than obsessing about details that might not end up mattering for the end product.

The trick is to make sure to that everyone involved knows that time for refactoring and fixing will be needed after.

Otherwise it can be problematic..

 

I totally agree. I have an article in my queue about creating a culture of refactoring so people “are always refactoring.”

But yea, good point about putting bad code in that doesn’t get refactored. I guess if you know your team isn’t into refactoring, you can refactor it yourself before you ever commit it to Github?

 

The vomit draft is how I start 99% of everything I write!! Good tips.

 

Haha thank you so much. I write about this stuff because I struggle a lot with procrastination myself. Right now I’m procrastinating on sleeping by “checking up on email and dev.to” haha

 
 
 

Glad to hear it. CubicleBuddha.com is all about learning to fail fast so you can get happy! 😍

 
 

Yea it struck me as soon as I heard it. Thank you so much for the comment @dvddpl :)

code of conduct - report abuse