6 ms·
> 1. Exploration & Execution. I found myself really liking this section. Unfortunately, I think it was because it helped validate my inner fears that manifest
by codeodor 15y ago
> 1. Exploration & Execution.
I found myself really liking this section. Unfortunately, I think it was because it helped validate my inner fears that manifest as procrastination.
Overall, I liked the article, but be wary of using those early stages as a excuse on which to continue doing nothing.
- eric-hu 15y agoSo how do you get around your excuses to do nothing? What have you found to be most effective and least effective? I have some pretty terrible procrastination
- jdunlop 15y agoThe key is to make sure you always have goals. They can't be too big or complex, or you'll find a way to not do them! While it's generally acceptable to make goals that are as large as a days work, I find that even that is too big when you have issues with procrastination. Too big: - Setup new server Better version: - Install Debian - Install MySQL - Setup database/permissions, deploy database snapshot - Install Jetty - deploy latest build There are two wins here, the tasks are small enough that you'll feel progress and want to keep going, and it will force you to really plan out your work before starting. If your task was just "Setup server", and you got stuck half way through, you might feel there is still so far to go and you'll end up breaking for the day. Then the cycle begins, and you won't want to pick it back up.
- codeodor 15y agoI'm still learning to identify my sources of procrastination, so I'm not sure I've found anything effective yet. On the other hand, I have done a couple of test/soft-launches this year, and have lost my fear of failing on those. That's more than I had done in the prior 10 years of being a programmer with aspirations, so it's progress. I still struggle with probably doing too much before testing an idea, but I also struggle with doing too little, so I'm trying to find a balance. Learning, still, really.