I just accidentally blew away an airplane-ride's worth of work because I mixed up the arguments combined with -f. Here's the thing: I'm not mad. The first time I made this mistake, I was furious. I had lost weeks of an assignment in college because I messed up a symlink.
-
-
Show this thread
-
But I've learned. Now I commit early and commit often. So while I lost a small amount of work, the majority is recoverable with simple git checkout.
Show this thread -
The difference between a junior/senior engineer isn't whether you remember the argument order for ln, tar, etc. The difference is in accepting that you're going to mess up, and adjusting your workflow to accommodate personal failure. </opinion>
Show this thread
End of conversation
New conversation -
-
-
Amen, brother.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
that's easy, it's always the opposite of what you just typed
-
Kind of like a USB-B port.pic.twitter.com/GEhmW54ywW
This media may contain sensitive material. Learn more
End of conversation
New conversation -
-
-
Feeling your pain. My brain refuses to hold the -p HOST:CONTAINER pattern for Docker containers. Yes, I just wrote this tweet, yet the next time I start a container manually I will seize up and forget.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The one thing I was told that made it finally stick: it's the same as if you were copying the file. `cp sourcefile destinationfile` `ln -s sourcefile destinationLINK` That being said, I'm still unsure enough that I googled it to make sure before tweeting this :D.
-
But what if you think of the source as the local link that links to a destination .
End of conversation
New conversation -
-
-
I once messed up dd's if and of, writing 10GB of data to the root filesystem on a production machine. Learned to be a bit more careful after that. :)
-
Yeah, dd is one of the commands that I always check five or six times just because I don't trust myself to read it correctly.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
with