Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
It’s not computer’s nor intern’s fault if you don’t save your work for over a week.
Recloning the repo
Next time train interns to use git
Or even just save the file…?
In all seriousness though, losing code sucks hard, but when that happens I always remind myself that the real code is in my head and it’s the ideas and solutions that really matter, and you didn’t lose those. You can always recode something as long as you understand how it worked.
How is not saved if it's even compiled? I smell bs.
As fake as the gif. The monitor is almost falling on its own.
Asbetha7193yI didn't lost code, I lost my SRS, SDD and SPM documents because his program scanned through my files and while they were open he somehow ran in a really fucked up raise condition ... gladly it started from my new partiton instead of one with more data on it ...
His program crawled your filesystem and changed your documents and he didn’t even warn you about that?
I would not be happy.
Condor349443ygit init, and treat Windows like a time bomb that could Win-blow up on ya any time! There's a reason why I'm learning myself to run *everything* on the server in screen whenever I'm using WSL.. the client OS is that reason.