I got married (answers both questions, I'm afraid). I often wonder if that is a really bad way of doing things since I tend to simply do what my wife wants. If I want "me time", I need to tell her in advance so she can put it in my schedule. However, I've always been super easy going in that respect. My wife loves organising things and trying to optimise stuff so that everything fits. She even optimises the meal prep…
For me, at home, it works in a similar way. There is a downside though. I'm very very forgetful, so sometimes, my wife needs to remind me to do a certain task 3 or 4 times before I actually do it. I started noting things down to avoid forgetting as this puts some strain on our relationship.
Ask HN: How do you schedule your life?
31–37 of 37 posts
Re: Ask HN: How do you schedule your life?
#32I use Todoist to plan my life (and work), and try to stick to it. If you are interested to know what is Todoist and how does it work, I have written a blog post on it. Have a read. https://www.kashifaziz.me/todoist-productivity-tips.html/
Re: Ask HN: How do you schedule your life?
#331. Writing everything down
I make sure to write down every event, task etc as soon as I can, and then process it. This makes sure that I don't keep things in my head. Just this alone gives huge returns.
2. One week at a time
I organise my life one week at a time. First, write down all your time commitments for the week (things you've already committed to doing). Then look at the time you have left. Once you have that, look at your backlog of tasks/things you want to do (from element 1) and select the things that you can reasonably do in that week. I then schedule these tasks roughly for each day.
I found that setting a few tasks for a day meant that I was able to focus on one or two tasks, rather than dealing with the weight of all my different life facets at once. This was especially useful to me during university, when I was balancing multiple subjects and clubs.
3. Plan, record, reflect cycle
This part is quite simple, and could also work on its own. First you plan your week (See 2), then during the week you write down notes for yourself. This could be: - Where you failed (e.g. I was late for work today) - How you felt (e.g. I really enjoyed hanging out with x friend) - Any random thoughts/observations (e.g. I tend to get scared by strangers in hats)
I tend to set goals for each week, and then record relevant metrics (e.g. Hours on my phone if I'm trying to cut down, or days taking my medication)
Once the week is done, I do a reflection over the past week and look at what I want to change for the following week. Because I iterate weekly, there's no harm in me trying radical things with each week as an experiment.
Just the weekly iteration has been incredibly valuable for me, and has lead to some great insights.
Re: Ask HN: How do you schedule your life?
#34Re: Ask HN: How do you schedule your life?
#35Re: Ask HN: How do you schedule your life?
#36On micro level, I don't have a schedule. I try to cultivate habits. I.e. for past month I managed to wake 30 mins earlier than my daughter to drink my tea in peace and do some quick workout :-) It really helps me with the structure of the day.
Re: Ask HN: How do you schedule your life?
#37I've got a few different complimentary systems for different things: - For working out, I rely on habit. I forced myself to go to the gym at a certain time for long enough that I just feel like doing it now, so I go automatically. - For personal projects, I work off a queue based system. While I'm working on a task, I try to minimize task-switching, but if I come up with a new idea, or something else I want or need t…
How do you keep track of your queue? Also is it FIFO, LIFO or a priority model? My queue seems to bloat, then I tried to mitigated that by telling myself if something is in the queue for X amount of time remove it. Nowadays that removal just becomes a JIRA story but it's rather inefficient for me.
That usually means I end up sort of ping-ponging between feature development and refactoring/tech debt. I develop features until I feel like structural issues are annoying/slowing me down, and then I focus on code quality until I can move fast again.
But honestly it's a very loose system and it's fairly sensitive to what I am most driven to work on in a particular time period. But I'm not really trying to micro-optimize the project, my main goal is to have a system which lets me be consistently productive. That means it's loose enough to not get in my way when I'm in flow-state, and it's organized enough that I can have a list of achievable goals to work through when I'm lacking in intrinsic motivation.
I also don't mind having a pretty huge back-log. When I'm totally uninspired it's nice to be able to pick up on ideas I haven't thought about in weeks and play around with them with fresh eyes.
edit:
> It's a pretty loose priority system, with the basic heuristic being that I try to choose the task that brings the most value to the project at the given moment.
I built my own very simple tool for that. It's a bit redundant since there's a lot of great tools out there, but it does everything I want and nothing I don't, and it's very low friction/distraction free.