5 ms·

I'm with George on this one. I like to finish off a day with the atomic module/query/code I'm working on working nicely (optimized or not; it needs to function

I'm with George on this one. I like to finish off a day with the atomic module/query/code I'm working on working nicely (optimized or not; it needs to function). Somehow, in my mind, it's like closing the trailing bracket. I like to finish the day 'clean'. Sure, this might cause the next day to be a slower start, but you have to balance this out against the peace of mind you get from leaving the office and having no worry about. That is worth a lot (and might cause me to sleep better and be more productive the next day?) It's like doing the dinner dishes before going to bed so you don't have to wake up to them (or not enjoying the rest of the evening because you think you'll have to do them in the morning). Like George, I'll often plan my next day ahead so that I know what I'm going to do to hit the ground running (Optimize the code I wrote last night, add input error correction, cough add comments or tighten up the format ...) All these things aside. Do what works for you!

mmahemoff 13y ago
As the OP, I get that mentality and have it too. One could call it an extremely mild and very normal kind of OCD we all have. For that reason, there are times (or moods) when I do the completion thing. But because of the motivation benefits, I also try to bend my brain to focus more on the checkin as the snapshot that must be pristine in any time slice, and the editor as just a flowing set of arbitrary frames between checkins.
- owenversteeg 13y ago
  Personally I try to make the code work by the end of the day as kind of a motivational thing. (Like you described above.) Also, to be pedantic, I think it would actually be a mild kind of OCPD.
  - collyw 13y ago
    I notice a definite sense of satisfaction if I finish the day with things working as opposed to not working (especially if I have been working on that feature for more than a day). Though the scope of my tasks varies so much it is difficult to "try and make the code work by the end of the day". I don't think I ever plan anything that I think should take more than a day, but more often than not downloading a new library and configuring it to work should be simple and takes as much time as any coding. (Still it will likely be quicker than me writing all the functionality and tests myself).

mmahemoff 13y ago

As the OP, I get that mentality and have it too. One could call it an extremely mild and very normal kind of OCD we all have. For that reason, there are times (or moods) when I do the completion thing. But because of the motivation benefits, I also try to bend my brain to focus more on the checkin as the snapshot that must be pristine in any time slice, and the editor as just a flowing set of arbitrary frames between checkins.

owenversteeg 13y ago
Personally I try to make the code work by the end of the day as kind of a motivational thing. (Like you described above.) Also, to be pedantic, I think it would actually be a mild kind of OCPD.
- collyw 13y ago
  I notice a definite sense of satisfaction if I finish the day with things working as opposed to not working (especially if I have been working on that feature for more than a day). Though the scope of my tasks varies so much it is difficult to "try and make the code work by the end of the day". I don't think I ever plan anything that I think should take more than a day, but more often than not downloading a new library and configuring it to work should be simple and takes as much time as any coding. (Still it will likely be quicker than me writing all the functionality and tests myself).