4 ms·
1. Never tell me what to do. How about "Why I don't.." instead. I'm not sure why you are qualified to give me an absolutism in the first place considering you
by jawngee 14y ago
1. Never tell me what to do. How about "Why I don't.." instead. I'm not sure why you are qualified to give me an absolutism in the first place considering you've only been a professional developer for 5 years. Now get off my damn lawn.
2. And you've apparently never used Tower.
- joeyespo 14y agoThere's a comment in the article that also recommends Tower. I've personally been looking for a Tortoise replacement. What makes Tower so good?
- jawngee 14y agoIt's pretty much 1:1 to git command line. Most times when someone on my team screws up a commit, it's because they botched the command line (the inverse of this article's claims). Fix it in Tower in a few minutes in a visually simple way that helps them understand what's going on. It also makes submodule usage do what you think it should do.
- sallen 14y agoAgreed. This article is stupid because it extrapolates from a few cases he's seen personally (and it was his coworkers messing up; I'm sure he's such a good developer that he's never made a mistake attributable to the command line tool, like making a typo). And as long as we're being totally unscientific about the whole thing, the most common mistake I've seen when using a version control system has come from people checking in unintentional modifications using the command line tool because it is easy to miss. In a GUI, you can better see what is being committed, and a simple checkbox lets you skip it, while double clicking gives you a diff that makes it so much easier to review every change before you commmit.