|
|
|
|
|
by tailspin2019
1557 days ago
|
|
I have the exact same experience as you. I’m also focusing a lot on building routines at the moment. They’re helping, but it’s hard work! Would you care to elaborate on what sort of routines you’re working on implementing? |
|
I also added a "day done" timer, means, at 18:30 no more work, no matter what. I stop and make my dinner meal.
My morning routine (the 7:00 wakeup call) had the most impact. This call basically initiates a sequence of actions: Wakeup, taking shower, breakfast and PAPERWORK. This goes until 9:00 which is the time where I start my work day.
My next step will be to integrate running into my morning routine as the first action. That being said, knowing that I will do my paperwork the next day at a given time helped the most. I don't have a lot of paperwork or urgent paperwork so this works for me.
When a new routine is integrated and becomes a normal part of my life, I start with integrating the next routine and so on.
One thing I noticed though is, no matter what the routine is and how you plan it, at some point you have to do it and overcome your procrastination. You have to find something that works for you. In the end you have to do the action and just not "plan" it.
I plan my routines in a way where I know I'm not "overwhelmed". You gotta be true to yourself :)
Oh and I should mention that I also have days set where I definately will do certain things. For example, I chose Sunday to be my day where I experiment with some cool programming stuff that I wanted to do. That could be a new library I found, programming language or whatever. But no pressure, it's just my "experiement" day where I look into things I'm curious about.
I also clean my "backlog" on that day in the evening. I have a bookmark folder called "backlog" where I move things I want to read or visit later.
Just knowing I have my fix dates and times to do certain things is really satisfying. I'm not sure how to describe it. But it feels relieving.
In the last startup I worked for, I had a certain behavior of what I call "goal-driven stopping". Instead of stopping my work based on the current time, I stopped when I was satisfied with the work/code I have done and if I didn't fix that bug or feature (the goal) I kept going. This was super bad because I wouldn't stop for lunch and instead kept going. Sometimes it was so bad that I would my 1st or 2nd meal that day in the late evening. For some reason I pressured myself for reason I myself made up.
I learned to not to do this with the help of routines :)