• 4
    Once my editor crashed and left me with blank css file, 3500 lines gone. I was 3 hours before deadline. So i rewrite the whole thing by memory in 3 hours and 10 minutes. looooool
  • 5
    After that installed an extension in vscode to save automatically after every edit. Saved my ass many times. 😂
  • 11
    Literally never have never encountered this problem.

    If the app crashes or something; sure. But I feel like any editor worth it's salt caches your work or, at the very least, warns you that you have unsaved work when you try to close it.

    Shit, even Notepad does this.
  • 2
    @Angry Indeed, this hasn't really been an issue for years. Also, anyone writing anything should have *save save save* embedded into their second nature.
  • 10
    What kind of maniac:
    1. Doesn't use an IDE with an auto save/recovery feature.
    2. Writes 500 lines of code in one file.
  • 0
    i see op still using notepad huh...ever read/heard the term IDE somewhere?
  • 1
    Even though VS Code has autosave, I still press Ctrl+S pretty much after each line I typed. It's become such a habit now.
  • 1
  • 2
    I have a habit of pressing Ctrl + s on each word.
  • 2
    I typically wind up saving a file with no changes more often than I forget to save changes.

    And I use vim mostly.
  • 0
    Not like that but I once git blew myself.
    One day I made some changes on a file which took around 2-3 hours, saved the file and closed it. Then I continued with "git commit --amend" instead of "git commit -a --amend" like I usually do. Anyway my next command was "git reset --hard" can't even remember why anymore.
  • 0
    To bright for that
  • 1
    I can’t imagine to write 500 lines without compiling. After few lines I need to see if my code does what it should do. 😕
  • 1
    @JustThat vim-five! Although, I use nvim now.. still.

  • 0
    @Angry ZZ = vim mic-drop
Add Comment