It amazes me at times how many little things can come up within the span of one day to try to make my life difficult.
Sometimes it’s my own fault.
Sometimes it’s not.
For example I recently found out that I needed to transfer a domain name from one registrar to another registrar. It isn’t a terribly difficult thing to do, but it always throws me for at least one loop, because no one does it the same way.
After fiddling around with it for about a half hour I finally hit on the correct sequence of things and am now waiting for the authorization stuff to go through. Then all I need to do is finish by recieivng the domain name in my regular registrar’s account.
You experience it too. Things come up and need to be dealt with fairly quickly.
I call those things fires.
Fires are meant to be put out.
I think this is also kind of how I go about writing code. I figure out which is the “biggest” or “next biggest” problem that needs to be taken care of. Then I attack that with everything I’ve got. Once that fire is put out I can move to the next small blaze.
Eventually this leads to a complete, mostly functional, piece of work. (usually)
I’ve tried numerous methods to keep myself productive. Lists. Special lists. Reminders. Time blocking. Etc…
At the end of the day, those things kind of worked… but I’ve not stuck to any of them because it simply takes too much time an energy to maintain the way of doing things. The method of keeping track of what needed to be done got in the way of actually getting things done. That doesn’t make a whole lot of sense.
Instead I’ve kind of moved to this new mentality. Fix things that need to be fixed now. Do things that need to be done now. Stop when you need a break.
Eventually you will get to the end of the project.
Knowing when to stop is the important thing. I think.
So here I go. I’ve got a few fires to put out today related to this post from the other day.