• Iā€™ve heard a lot of talk about how multitasking decreases performance compared to single-tasking, but unlike situations where there is a physical interruption such as a phone call, if there are multiple tasks running in parallel, simply switching tasks at your own timing is the same as single-tasking, and the performance will be the same. If you design properly with this in mind, performance should improve.

    • Imagine creating your own scheduled micro-threads instead of creating native OS threads.
  • So, when I increased the load to 2-3 times what it had been before with that design, it was interesting to see patterns in the various things that were being taken out and what kind of things were being taken out. Self-load test.

    • Almost shrugging off a physical exam.
    • I didnā€™t apply for a day off work this weekend.
    • I havenā€™t gotten around to preparing 4 hours worth of workshop materials at all.
    • I havenā€™t responded to your email about adding errata to the book (I remembered when I was writing the above).
  • The health checkup thing is a bug where you should check both the schedule and the task list, but you only look at the task list, start working on it, and forget about the schedule.

  • A bug that evaporates from the brain stack as a result of unnecessary procrastination without registering it in the task list, even though the application for working on holidays should be submitted immediately when it is decided that it will be treated as working on holidays.

    • Maybe this case started out with ā€œIā€™ll check if itā€™s treated as a holiday work,ā€ but in that case, the ā€œcheck the result and act on itā€ task should be loaded into the schedule after the appropriate time when waiting for someone elseā€™s IO.
  • Creating workshop materials is a typical bad task.

    • The first step is not clear, the goal is not clear, the deadline is not clear, the level of requirements is not clear, etc.
    • As a first step, I left it piled on the task ā€œ1 Pomodoro writing out about the workshop materialsā€.
    • Itā€™s funny that you didnā€™t modify the task there when you thought of doing it and didnā€™t do it because you thought, ā€œOh, I have to refer to that documentā€ or something.
  • Having substituted your email inbox for a task list, you are distracted by emails for long-term tasks, and one-off tasks that you can hit back immediately are buried.

  • When thereā€™s more than one screen of data in the inbox, itā€™s not in the proper state to be an inbox.

  • You canā€™t even do the errata email, you canā€™t perform the task if you donā€™t have the book in hand!

    • And the book is at the office now, so you canā€™t run it until Tuesday!
    • Errata email 3 days old and has been in my email inbox for a long time and has not been addressed!
    • I donā€™t think inbox should be used as a task listā€¦
  • I had a notebook in Evernote at hand called ā€œinboxā€ and a notebook called ā€œtodayā€™s tasksā€ and a notebook called ā€œthis weekā€™s tasksā€ and that worked fine when the majority of the tasks were R&D.

    • However, as the wait for othersā€™ IOs increased, many modifications became necessary.
    • First of all, if you erase a task at the point when ā€œyour task is finished (you handed the ball to the other party),ā€ you will forget about it as it is when the ball is not returned from the other party.
    • If you pile them up as a task of ā€œwait for the response and do the work,ā€ itā€™s fine when the number is small, as it has been, but when the number increases, the habit of ā€œskimming and skippingā€ occurs, and you still forget.
    • So I decided to pile it up in the form of a task called ā€œPrompt if not - on Thursday.
      • So much for the premise of what I am going to write about.
  • So, even though I was not aware of it, there are many ā€œthings to do at specific times (small schedules)ā€ appearing here in addition to ā€œthings I performā€ in the ā€œtasksā€.

  • What happened as a result of not noticing this change in data content?

  • I thought it was wrong to write such a detailed schedule in my notebook because there is a lot of it and it is characterized as ā€œif I get a reply right away, I will do it without waiting for the due dateā€. I forgot to look at ā€œTodayā€™s Tasksā€.

  • The question is, in the first place, was it necessary to separate them into separate notebooks on Evernote?

  • Evernote, moving information between notes is not easy. Opening a note in a separate window to cut and paste is sterile and I canā€™t do it on my iPhone.

    • If you want to separate and organize your notebooks, they need to be easy to move around.
    • If we try to achieve this in Evernote, we could make one task into one notebook and realize it by moving notebooks around, but it seems like we are splitting a disposable chopstick with a hatchet.
  • The other method is to write everything in one notebook. I have some concerns about too much information and not having too much warbling, but this one seems to be better.

Facebook 2015


This page is auto-translated from /nishio/ćƒžćƒ«ćƒć‚æć‚¹ć‚Æ実éؓ2015 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. Iā€™m very happy to spread my thought to non-Japanese readers.