Git is a reminder why even the best minds in software development sometimes really should talk to UX/UI people.
Oh Shit, Git
21–30 of 237 posts
Re: Oh Shit, Git
#22Re: Oh Shit, Git
#23Just delete the directory and clone it again.
Or you can spend some time once to understand how git works, and never run into a similar situation again. git is built on a beautiful and very simple model, and it's easy to unbreak the repository 99% of time if you understand it (and I'm saying this as a very mediocre programmer).
Re: Oh Shit, Git
#24I’m frustrated if I take a day to work out some something that Jeff Dean mentioned to, uh, a friend, and it took me a day to work it out.
@bradfitz works on TailScale, there’s also a reason he’s a chapter in a book. @jwz is better, by so little you’d never notice, so his chapter is cooler.
What book are you in?
Re: Oh Shit, Git
#25Git is a reminder why even the best minds in software development sometimes really should talk to UX/UI people.
Git was built with a very specific use case and aimed at an extraordinarily technical subset of users. It dominated the world despite the UX flaws, which suggests they really aren't that bad.
Especially if you'd have to lose github, thats the real force
If gh migrated to something else, then a lot of ppl would follow
Re: Oh Shit, Git
#26Re: Oh Shit, Git
#27Git is a reminder why even the best minds in software development sometimes really should talk to UX/UI people.
Git was built with a very specific use case and aimed at an extraordinarily technical subset of users. It dominated the world despite the UX flaws, which suggests they really aren't that bad.
If only that wasn’t the case we’d all be using a sensible source control system now instead of one where people repeatedly say things like “if you just learn the underlying model…”
Re: Oh Shit, Git
#28Re: Oh Shit, Git
#29Git is a reminder why even the best minds in software development sometimes really should talk to UX/UI people.
Git was built with a very specific use case and aimed at an extraordinarily technical subset of users. It dominated the world despite the UX flaws, which suggests they really aren't that bad.
Yes, you need to follow a tutorial to use it effectively. Designing for beginning users is often detrementantal to advanced users, and I object to that being called "user friendly".
I'm not very vocal about git usually because I'm not an expert I have no big complaints, and I'm not that interested in arguing about it. I think there's a lot of us that are perfectly happy with git; we just make less noise.
Re: Oh Shit, Git
#30Earlier quoted context omitted.
Or you can spend some time once to understand how git works, and never run into a similar situation again. git is built on a beautiful and very simple model, and it's easy to unbreak the repository 99% of time if you understand it (and I'm saying this as a very mediocre programmer).
Depends. Sometimes it's easier to tear down everything and start from scratch.