Hacker News Reader

Comment by lostjohnny | Hacker News Reader

I think everyone older than 30 does.

I also have the habit of pressing it more than one time, every time I press it.

I'm not even be sure that save will really save.

Is this an age thing? I do the exact same thing. Every time I stop typing I hit ctrl-s between 2-5 times. I don't eve think about it anymore.

My kids are getting to the age where they are doing projects on a computer and I'm constantly telling them to "save early, save often."

I guess it's some form of PTSD from computing in the 90's.

I worked at the help desk when I was in college back in the 90s and our mantra to users (and ourselves) was “save often and make backups”. We figured the more people we could inculcate that practice into, the fewer “I’ve been writing all afternoon and the computer just crashed, I can get my work back, right?” and “My only copy of my thesis was on this floppy and now I’m getting a disk read error, you can fix it, right?” visits we’d get that would end in tears.

It's not an age thing I don't think. I'm 22 and after I finish any tiny section of code I format it and then save. I don't know why, it's just habit now

Yeah, but do you save several times before you're finished that tiny section?

Several times? No, just saving once is sufficient.

Why not twice to be sure?

Because most programs don't do anything if no changes were made between the current state and the last save. VS Code shows which files have changes made since the last save, for example.

Exactly why it doesn't hurt to save a bunch of times to be sure.

> save early, save often.

I got the same advice from my grandfather, who grew up in the Great Depression. I think it was PTSD on his part, too.

It feels like a programmer thing, since unsaved files won't be compiled when you run the program. At least that's where I got the habit from

Programmers have an additional issue with incremental build systems that do not always rebuild everything they should.

My dad was doing support & sysadmin and it was save and make copies, both on-line (it was 5 years before we would start using cloud) and on physical media.

A few months ago, I saw a popular meme on Reddit (ProgrammingHumor, or something like that) where the core of the joke was: "that face when Visual Studio crashes after you've been writing code for 2 hours and forgot to save."

And my reaction was: how do you forget to save? That's muscle memory for me, man! Command-S gets hit five times in as many minutes.

IntelliJ doesn't have "saving", it writes all files to its cache constantly and then to the original files as soon as you alt+tab, and yet I still find myself hitting Ctrl+S constantly, usually as part of like a nervous tic or something, where while I'm thinking I'll save, paste my clipboard, undo, repeat.

How do you code for 2 hours without saving, considering you wouldn't be able to run/test/compile without saving?

I’ve coded for hours early on in a project without compiling/running/testing. But I’m old enough and wise enough to constantly save.

It definitely is! My company recently connected Office to OneDrive, which means everything saves automatically. I still find myself saving after every paragraph.

I ctrl-s or :w every time I take my hands off the keyboard. A friend of mine, considerably younger, was lamenting that their computer crashed while they were working on a 3d model in Maya and they lost an hour's worth of work because they hadn't saved. I was in absolute disbelief. I pressed the issue, there was no good reason to go without saving every time the file changed, it's not like the program got bogged down when they clicked the save button. They trusted the auto save feature. We had two completely different paradigms.

I moved to using an IDE. Everything is saved and always. There isn't even a save button. I also moved from vi/vim quite painlessly and never find ':wq' or 'hhhjjjj' in documents that I have edited, this was a genuine danger once.

With the right tools - an IDE with version control - the quaint notion of saving files can be mostly forgotten and the fear of losing unsaved work banished. Even if over 30 adaptation is possible so long as it is an easy, downhill path with less to do instead of new stuff to learn.

It used to be 'Jesus saves' but now, for me, my motto is to just use an IDE.

VB6’s IDE doesn’t auto save. Ugh.

I do this for ctrl-C copying, because for a short while, years ago I had a keyboard where the C-key would occasionally fail. I have long since replaced this keyboard, but the habit of just hitting ctrl-C more than once is not entirely gone.

I had a similar problem about a decade ago. My muscle memory for editable text became CTRL-X CTRL-V so I could see the the text had been copied.

I still to this day have problems with various MS Office products failing to save or not auto-saving on the latest Office for Mac. So I spam that Cmd+S button as often as I can.

Reply on news.ycombinator.com