That’s basically how I did it.
To properly learn it using this method, create a directory that contains only text files and sub directories and treat it like a real project. Add files, delete them, play around with updating the repository. Try and go back a few updates and see how the things react. Since it’s not a real project there’s no risk of loss, but you’ll still get to see the effects of what you do.
I spent the last 6 months working on a feature. Found out 2 weeks before release that it was being postponed.
As a Jr. Full Stack, I’m in this picture and I don’t like it.
I work with Java. And I’m definitely ‘rose tinted glasses’ because I also learned to code in Java. But I’m the opposite.
Do you use Java at home?
Fuck no, I want to stay sane.
God damn it, I hate this hacker crap!
pi = 3.1±0.05
Gotta allow for a little uncertainty, just to absolutely ruin everything.
Well there’s your problem. You need to get a cabinet.
The book is better than the movie, and Jurassic Park is one of my favourite movies.
My sibling ran into this issue once. I’m not sure if it’s a setting or a default, but vscode would assume they were working in a blank repo until they made a commit.
Sounds like this person had the project (without source control) in another IDE, tried out VSCode, and it assumed that it was all ‘changes’. I don’t use VSCode, do I can’t say for certain, but I know my sibling lost ~4 hours of project set up for the same reason (though they immediately realized it was their fault).