I was thinking about this all last week. Monday I set a goal of mapping out our infrastructure to see what we could cleanup. Tuesday came and i still hadn't even logged in. Wednesday came and I thought
This is going to bore the crap out of me, but it needs doing. How can I make it exciting?
Thursday came, no bright ideas to make it exciting, so I just dove into a pomodorro session. Twenty five minutes later I had made a good start and mapped out all vms we used. Five pomodorros later, I was done! At least for that cloud provider.
It reminded me of something I learned from the Coursera "Learning how to learn" course recently, but is still not at the front of my mind:
Focus on the process, not the outcome.
Doing so in this instance I always had a quick feedback loop, every twenty five minutes, so it never felt boring. If I tried to sit down and focus solely on getting it done entirely I would have been frustrated. I do this when coding all the time, it just never occured to me to do it for other tasks!
In my case, I think of it as an input based rather than the output based, by doing an output based you're focused on how many tasks you've finished and be demotivated afterward if you didn't finish any, but by tackling the task as an input based, which time, in this case, you'll be much more motivated as you're seeing progress over the time you've worked on the task.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I was thinking about this all last week. Monday I set a goal of mapping out our infrastructure to see what we could cleanup. Tuesday came and i still hadn't even logged in. Wednesday came and I thought
Thursday came, no bright ideas to make it exciting, so I just dove into a pomodorro session. Twenty five minutes later I had made a good start and mapped out all vms we used. Five pomodorros later, I was done! At least for that cloud provider.
It reminded me of something I learned from the Coursera "Learning how to learn" course recently, but is still not at the front of my mind:
Doing so in this instance I always had a quick feedback loop, every twenty five minutes, so it never felt boring. If I tried to sit down and focus solely on getting it done entirely I would have been frustrated. I do this when coding all the time, it just never occured to me to do it for other tasks!
In my case, I think of it as an input based rather than the output based, by doing an output based you're focused on how many tasks you've finished and be demotivated afterward if you didn't finish any, but by tackling the task as an input based, which time, in this case, you'll be much more motivated as you're seeing progress over the time you've worked on the task.