mileszs

Or, perhaps he simply finds it amusing to post his ever-odd thoughts and watch the reaction. Does that have to be cocky?

Or, perhaps I give him a pass for whatever he does, because I enjoy his personality. In any case, it doesn't seem to me that such vitriol is necessary toward another human being, and fellow hacker. If you find him so annoying, why are you paying so much attention?

No. You you do your thing. I'll do this. I don't want to have to run another command to see what lines have changed in my file. I want small, non-intrusive icons in the gutter without doing a damned thing.

I use both. If I need a full diff, fugitive is great. Sometimes I just want to scan to see what lines I changed in a a file. In other words, it is impractical to use this plugin to find out what _files_ you've changed. It is great for finding out what lines in whatever file you've opened have changed.

It's actually a lot easier, unless you have next-to-zero traffic, to ask _them_ to take an action that puts the info in your inbox, rather than dig in logs, which could have that specific user's information buried amongst hundreds of other entries. It's a time-saver.

What if you have insufficient logging (Heroku sans a decent logging plugin, for instance)? What if you built the thing, but it's hosted by a third-party that limits log access? What if you want some non-technical or not-that-technical person to handle the issue?

As hackers, we tend toward "do-it-yourself", but there are a lot of cases where that isn't practical or economical.

I think, essentially, he is saying that you end up spending time maintaining your template, losing much of the benefit of the template, depending on how often you start new apps. I have found this to be true at a certain threshold of complication in the app template. However, if you are indeed starting a brand new Rails app every month, as you said, you likely don't have the same cost, as maintenance to the app template happens on a more regular basis. Even as a consultant, I don't start new Rails apps that often, and side projects tend to involve experimentation outside of what I might consider my "stable" stack.

I don't see it as a "huge Ruby bug". Could you elaborate, please?

I would understand "huge Ruby on Rails bug", though, by convention, it is still a fairly unlikely case.

Edit: I think your edit answers my "Could you elaborate" question somewhat, as you relate a Python library issue to this issue.

They're both good. My open source repos are on Github. My private (thus client-related) repos are on BitBucket. I've been pretty happy with this configuration.

Perhaps it helps that I know a few other companies and developers locally using BitBucket for private repos.

Incidentally, reliability and price are both valid reasons to "use an also-ran copycat", in my personal opinion, if that also-ran copycat is pretty damn good.

I don't think "mentioning Github" is the only piece people are using when deciding to question your communication skills. The word "microcontroller", except in certain extremely specialized situations, should probably not be used with a client. I understand it's a hard pill to swallow. I mean, you're both speaking English. Why does it seem like you're not speaking the same language?

In a way, you're not speaking the same language. Try assuming your clients have no concept of not just programming, but any of the process of building an application or solution to a problem that uses technology. Don't discuss details. They are probably paying you so that they don't have to worry about the details.

By way of example: I have the reverse problem with my wife. She is a nurse. When telling me about her day, she used to fly through a great deal of technical details using an amazing number of acronyms and abbreviations that I found not just unintuitive, but completely incomprehensible. I genuinely care about how her day was, but I found myself exclaiming in exasperation, "I have a clue what any of that means!" She now explains only what is necessary to get the point across, and defines acronyms as she goes along, if necessary. That works, but, in your situation, I'd abstract my communication at least one more level than that.