141–147 of 147 posts
I'm really curious how much longer github can offer so much free service. It's not just git but effectively free web hosting as well, at least for statically served pages. It seems like it's only a matter of time before something will have to give. Either they'll have to start throttling web serving or cover the site in ads like sourceforge or something I guess I'd better sign up and start paying ASAP to help be part…
Most of developers in my countries 're using SVN. I don't use SVN at all, and i'm failing to convince my partner that Git is better than SVN, just because i don't believe in hardware stability.
This is why I love git (and distributed version control systems in general). For the most part a short downtime isn't the end of the world. When it comes back up I'll push my changes and that'll be that.
While I actually agree with you, as I look at GitHub as "somewhat reasonable git hosting", that is not how many (if not even most) projects actually use the website, so it is an unfair analysis: people seriously often use (and even encourage others to use) GitHub as the only web presence for their project, using a Readme.md to build a landing page; meanwhile, for many people, GitHub is how they handle incoming bug re…
http://www.verbosity.ca/hosting-your-own-git-based-shared-re...
That's a really nice status dashboard, tracking and publicly displaying your 98th% is really cool. On the other hand stuff like this: "13:17 UTC We are seeing unicorns ..." Comes off as un-professional at exactly the wrong moment.
No, adding a touch of humor is highly professional, not to mention good marketing.
Remember, they are not marketing to enterprise managers, rural Utah programmers, or corporate 80's programmers in suits, but to todays and tomorrows "hip" programmers.
Now, some of today's programmers arguably square and adhere to BS 50's professionalism ideas (where professional = boring, somber and well groomed) but most would take the unicorns over any kind of "professional" copy text.
Earlier quoted context omitted.
Other posters have noted where the terminology comes from. But you should really learn to take the meaning of an unknown term from context if you don't know what it means. As for the accusations of unprofessionalism -- I'll take vivid metaphor [1] like "seeing unicorns" over a dull monotone description like "our site is experiencing server errors." [1] As other replies have pointed out, in this case it's not a metaph…
May be just a matter of preference but for me "our site is experiencing server errors" is much clearer communication than "seeing unicorns." The latter requires me to learn a new terminology in a high pressure environment for no good reason . And if "seeing unicorns" was a code word for a specific kind of errors, then again I would rather have a more descriptive terminology and not one that I may confuse for an insid…
If you don't already know that "unicorns" means in this context, then you are not a GitHub user, and thus it being down is not a "high pressure environment".
Most of developers in my countries 're using SVN. I don't use SVN at all, and i'm failing to convince my partner that Git is better than SVN, just because i don't believe in hardware stability.
What does hardware stability have to do with it?