3 ms·

I don't think this method can work for me because I hate cognitively switching from one task to another.

• CydeWeys 11y ago
  Even if the tasks are related, in that they both involve writing code in the same project? I find that I can handle that pretty well, and I'm distracted a lot less by coding on two different parts of a project simultaneously than by trying to simultaneously do coding and also doing a task of a different type, like reading/writing documentation or email. If you think about it, some really complicated coding sessions require keeping the state of many pieces of the program in your mind simultaneously (see, e.g., this: http://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-a-programmer/ http://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-... ), including code in many different files. This is actually more difficult cognitively than simply working on two separate simple and well-contained coding tasks simultaneously.
  • firebones 11y ago
    There's a writing tip that you don't quit until you know what the first sentence you're going to write the next day is. I haven't tried this for coding, but the equivalent would be not to start running a test until you know what the next function/method/commit you're going to make is. Even if you have to screw around looking for potential problems in your code, or potential places to refactor, don't run the tests until you know what that next thing is going to be. Here's the actual Hemingway quote: The best way is always to stop when you are going good and when you know what will happen next. If you do that every day when you are writing a novel you will never be stuck. That is the most valuable thing I can tell you so try to remember it.