Learn More
Resend Email
59
AlgoRythm
6y

Actual pro tip: don't push only when you are done with code. Always push when you are done with coding session. Minimize the possibility of data loss and always have your code on the server.

rant
Favorite
Ranter
Comments
  • 12
    6y
    Or work on a branch, push small changes, then merge once you're done with the thing .
  • 1
    6y
    ... Unless you are drunk, then sober you will welcome the data loss!
  • 6
    6y
    also, don't push too hard while on the toilet, just don't do that
  • 3
    6y
    @webdev are these experience words?? XD
  • 1
    6y
    ++! I have forgotten lots of code on my commute between two stations simply because I didn't push. Man, fixing superficial merge conflicts because you had to re-write your code is *so* not fun
  • 0
    6y
    But please, never push not compilable code!
  • 0
    6y
    @geaz Honestly, I'd still do it (working on multiple workspaces every day taught me that) so that I can begin where I left off instead of writing it all again. If it's a big project, I'd use a dev branch or something.
  • 0
    6y
    On a private branch, perhaps.
    Git is not a backup tool, as @Lasagna has pointed out.
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment