Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
erandria166914dIf we want to stage/unstage files, why not create a stage/unstage commands?
If we want to change current branch, why not use the branch command?
another disclaimer: I'm not saying let's write a wrapper.
Guess we're writing a wrapper, boys!
I'm new to git so I make a manual copy of src before rebasing because I'm afraid I'll do something catastrophic......
Like, I have a local feature branch where I squash my commits into one before merging back to master. Is this OK? It doesn't seem to fuck anything up from what I can tell.
Last week I pushed a feature branch in case my PC would die. But when I rebased that one I got a lot of conflicts that had nothing to do with my feature branch. It was like I was squashing all of master so I had to travel back in time and solve every old merge conflict on master again before even getting to my feature branch commits. Sounds familiar? Where did I fuck up?
Thankfully this time a tool took care of tidying up commits and merging when my pull request got accepted. I'm still puzzled tho...
Fast-Nop1407214dGit's UI is total crap because it was thrown together without any thought beyond somehow allowing feature access.
This way of development is completely wrong because it is backwards, and the result is just as shitty as expected when disregarding any best practices with UI design.
The ONLY domain where that is OK is for programs that are not meant for human interaction, i.e. programs that talk to other programs. Think compilers called via build systems, or something like Apache. These are the ones where you need configurability over anything else because you set it up exactly once and then don't touch it anymore.
Doing that for an interactive program like Git results in a total disaster.
VaderNT30214d@erandria it's not just you. Over the years there have been dozens of articles criticizing Git.
Once you understand Git's internals (I recommend "Git from bottom up") you get what its incantations do... but Git's shitty interface remains shitty. And as long as there's enough fanboys shouting down criticism nothing will improve.
Toxic tool, toxic community. I avoid Git whenever I can.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job