4 ms·
>> "I haven't taken the time to understand my version control system and so every little thing I do is foreign and strange. Therefore I am resentful." It seems
by DenisM 18y ago
>> "I haven't taken the time to understand my version control system and so every little thing I do is foreign and strange. Therefore I am resentful."
It seems to me you look down on such opinion? That's what usability is about - make things easy enough to learn so that users are not recentful.
- KirinDave 18y ago>> It seems to me you look down on such opinion? That's what usability is about - make things easy enough to learn so that users are not recentful. We're software engineers. It is our job to understand more complex software models. Git's usability isn't terrible, it is just a more complex model that requires a more thorough understanding of the underlying principles. And given how trivial it is to find and read such data, my sympathy is limited. What's more, git's usability is a radical improvement path. Between services for remote repos (like github and gitorious) and better and better command line tools (GitX, for example). At some point you have to bite the bullet and understand your tools. We're seeing a lot of this reluctance in the industry as people are forced to confront distributed concepts.
- DenisM 18y agoI guess the question is which part of the learning curve is there for a reason and which part is preventable. Someone has already asked the question - is Mercurial any less powerful for being easier to use? I am sitting on the sidelines (svn) and waiting for the dust to settle. My only interest is to have one dcvs emerge with all the best in it that this field can offer.
- KirinDave 18y agoMercurial is marginally less powerful (it's maybe 6 months behind git in features, perpetually). This is not a deal-breaker (except that I don't like Mercurial's equivalent of cheap local branches, these patch queues are just an awkward model for thinking about it), but then there is the speed issue. Git is incredibly fast, so fast that you almost never notice it working even for massive amounts of data.
- timr 18y ago"We're software engineers. It is our job to understand more complex software models. Git's usability isn't terrible, it is just a more complex model that requires a more thorough understanding of the underlying principles." My job is not to spend time understanding how to use the version-control flavor of the week -- my job is to write software. You may not realize it, but you're advancing the usual, dressed-up, ad hominem attack of the perspective-challenged nerd: "tool Y is EASY if you just try to learn it!" (the implication being that if you don't want to spend time on a yak-shaving expedition to learn tool Y -- when tool X works just fine -- then you're lazy, dumb, or both.) Version control is a tool. Good tools let me do my job and get out of the way. Bad tools force me to spend a lot of time "understanding" them before I can be productive.
- thwarted 18y agoNo one is telling you you have to learn how to use the version-control flavor of the week if your project doesn't currently use it and your project is serviced just fine by some other version control flavor that everyone is already familiar with and is productive using. However, it's isn't very productive to have to deal with the same problems every day when using tool X, especially if taking a few hours to learn tool Y and switch to it would solve those problems.
- moonpolysoft 18y agoSo I guess that most programming languages would qualify as bad tools to you then? Seeing as how they force you to spend a lot of time "understanding" them before you can be productive.
- timr 18y agoMy job isn't to learn version-control systems. Time spent learning a programming language is a direct investment in productivity; time spent learning a version control system is, at best, a required distraction.
- KirinDave 18y agoYour job is most certainly to maintain a working and current toolchain. This includes programming languages and the tools that produce software in tandem with you. This isn't just for your employer, it's for the sake of your own career. Or do you want to be like those poor men who came before us, knowing and learning only COBOL, who now complain that software engineering is a young person's game? If I interview a software engineer and they don't know how to use a version control system and actively express disdain for the concept of making sure that the progress of development is captured, then I would not recommend we hire them. Anyone who's had git-bisect save them a huge effort locating a bug would probably feel the same way. Version control is every bit as important as your editor, debugger linker, and binary examination tools. If you don't know how to use them, you're not ready to start playing the game on a professional level. You might say that I'm using Ad Hominem here, but I don't feel it's that way. There are minimum standards for software engineers who want to develop software professionally, and using version control and understanding why we use version control is pretty high up on the list. If a basketball player isn't ready for the NBA, it isn't Ad Hominem to tell him his game needs more work, even though he may feel very insulted by the concept.