4 ms·

> Every fifteen minutes or so, as I wrote this story, I moved my cursor northward to click on the disk in the Microsoft Word toolbar that indicates “Save.” Gos

> Every fifteen minutes or so, as I wrote this story, I moved my cursor northward to click on the disk in the Microsoft Word toolbar that indicates “Save.” Gosh, cmd+S / ctrl+s doesn't work? Am I the only paranoiac that saves work every few seconds? Are all developers like that?

dylan604 9y ago
no, you're not alone. the following keyboard sequence is practically muscle memory: ;<return><return><cmd-s> if it's the end of a line of code followed quickly by another line of code, i just keep going. if there's a spot in the code where i decide to separate with a blank line, it's like a natural break point that deserves being saved. of the voices in my head, the one i tend to listen to the most is the one in the back screaming "Save, save often"!
- shawabawa3 9y ago
  I have problems sometimes adding an import in golang, then habitually hitting save which runs `go fmt` which removes the import. Sometimes it takes me 4 attempts before i can force myself to not save
- jjuhl 9y ago
  My voice doesn't scream "save often" as much as "commit often" - once it's in a commit "git" has your back and you can always collapse it into other commits, ammend it, rebase or cherry-pick it, whatever.. It's not safe until it's a commit - saving is .. meh .. sure, needs to be done. Commit is what matters - then it is safe - at the very least I can dig it out of "git reflog".
jacquesm 9y ago
> Am I the only paranoiac that saves work every few seconds? Are all developers like that? Only the ones that worked with buggy text editors prone to crashing.
reaperducer 9y ago
I picked up the "save" muscle memory from word processing on a Commodore 64. Compute!'s SpeedScript, and later Paperback Writer both used C= S to save a document. And back in eight bit days, computers had more crashes than a wet NASCAR track. You learned strategies to keep from losing an entire afternoon's work.
paulryanrogers 9y ago
Auto save is the cure

dylan604 9y ago

no, you're not alone. the following keyboard sequence is practically muscle memory: ;<return><return><cmd-s> if it's the end of a line of code followed quickly by another line of code, i just keep going. if there's a spot in the code where i decide to separate with a blank line, it's like a natural break point that deserves being saved. of the voices in my head, the one i tend to listen to the most is the one in the back screaming "Save, save often"!

shawabawa3 9y ago
I have problems sometimes adding an import in golang, then habitually hitting save which runs `go fmt` which removes the import. Sometimes it takes me 4 attempts before i can force myself to not save
jjuhl 9y ago
My voice doesn't scream "save often" as much as "commit often" - once it's in a commit "git" has your back and you can always collapse it into other commits, ammend it, rebase or cherry-pick it, whatever.. It's not safe until it's a commit - saving is .. meh .. sure, needs to be done. Commit is what matters - then it is safe - at the very least I can dig it out of "git reflog".

jacquesm 9y ago

> Am I the only paranoiac that saves work every few seconds? Are all developers like that? Only the ones that worked with buggy text editors prone to crashing.

reaperducer 9y ago

I picked up the "save" muscle memory from word processing on a Commodore 64. Compute!'s SpeedScript, and later Paperback Writer both used C= S to save a document. And back in eight bit days, computers had more crashes than a wet NASCAR track. You learned strategies to keep from losing an entire afternoon's work.

paulryanrogers 9y ago

Auto save is the cure