I was scared of reflog too. Had to use it for the first time recently after I accidentally’d a branch that I hadn’t pushed to remote yet. I was so glad that I could recover it all in <5 commands.
Title text: If that doesn’t fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of ‘It’s really pretty simple, just think of branches as…’ and eventually you’ll learn the commands that will fix everything.
Now I want to go play Cultist Simulator or Book of Hours. This list is also a list of the sorts of cards the games use to represent the narrative/puzzle you’re playing through. Highly recommend.
There’s some truth to it. I’ve seen devs not clarify something from the designs with other stakeholders due to lack of social skills. You end up with something they implemented to the spec, but makes no sense it reality.
Don’t just summarize the content though, summarize the rationale or how things connect. I can read your diff myself to see what changed, I want to know the logical connections, the reason you did X and not Y, etc.
Or just say “stuff” and provide that context in the PR description separately, no need to overdo the commit log on a feature branch if you’re using squash merges from your PR.
In internet terms: It’s just a soyjak holding a box with data who is pointing at another soyjak holding a box with data who is pointing at another {insert N-3 of the same soyjaks} soyjak with a box with data without an arm to point with
each commit points to the one before. additionally a commit stores which lines in which files changed compared to the previous commit. a branch points to a particular commit.
There’s a guy out there who made a reversible NES emulator, meaning it can run games backwards and come to the correct state. He made a brilliant post on Reddit /r/programming linking his ideas for the emulator to quantum mechanics.
Then he was asked why he didn’t distribute his program in git. He said that he didn’t know git.
To me, that’s a pretty good example of the difference between computer science and software engineering.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.