Because that vertical bar is just how Reddit displays blockquote by default and has nothing to do with the Markdown our comments are written in or the HTML it is converted to.
Now that I think about it, that makes no sense. I cannot imagine why it is not "| this".
The angle-bracket is the conventional quote-marker in text-format e-mail and newsgroups. Aside from that convention, the vertical bar is also confusable for letters (lowercase ell, uppercase eye) in ambiguous contexts, and it's visually easier to count quote levels with angle-brackets (which take up more space) than vertical bars.
Well, that's markdown for you :) I see your point, though. I'd guess that ">" is a much more prevalent character than "|". There was a time (long, long ago) that even ASCII wasn't supposed to work in all languages. In the place of "|", some languages' equivalent of 7-bit characters used their own accented letters. For example Denmark and Norway had "ø" instead of "|", Finland, Sweden, Germany and Hungary had "ö", France and French Canada had "ù", Ireland had "í", Italy had "ò", Portugal had "ç", Spain and Cuba had "ñ", Malta had "Ż" and Yugoslavia had "đ". Furthermore, a lot of home computers had completely different interpretations of ASCII (Commodore 64 had a weird symbol where "|" should be, for example)
In short, "|" wasn't a character that existed universally. In order to make the indentation in email (this was a time before web) and BBSes and newsgroups and whatever, the ">" was adopted.
Again, that's just my guess (but it makes sense to me at least :))
Every developer should use an SCM - not "be interested in it", unless they are developing one.
This is unnecessary pedantry. Being competent with the tools of your job requires a level of necessary interest. I am very interested in understanding how to use my text editor, but I am not interested in writing my own.
SCMs are necessarily complicated; there are a lot of operations they need to support. The fact that we have so many people saying that git's interface sucks and then coming up with an alternative interface that is equally awful seems to indicate this is more a human problem, notably the Hurricane Lantern Effect.
TBH saying a developer shouldn't be interested in SCM is like saying an author shouldn't be interested in proper contents and indexing. SCM is in some senses a table of contents into our software's history. Older systems give you a "as it comes" indexing system that is crude. Git is useful (among other things) because it allows us to impose more order on our history than we could otherwise achieve.
Mastering git is why I never, ever have a minor edit stashed in with my current story. My history looks like I've never discovered a simple task in the middle of another task. It is as if all the world is magical. All the minor issues that might roadblock my task get magically solved before the first line of code was cut on the new task.
This makes it incredibly easy to see how and what got done. Changes aren't splattered over the course of history like with svn but ordered in such a way that a person coming in can see how it all fitted together. There are never disruptive unrelated edits in my changes. Like an index into the history of your software project rather than a random assortment of change sets that come in whatever order they come in.
TBH saying a developer shouldn't be interested in SCM is like saying an author shouldn't be interested in proper contents and indexing.
You might be interested to know that there are plenty of people who do indexing work, and plenty of authors who hire them. Indexing is a specialized skill that requires careful attention and is often tedious. It's not something all authors should or do know about. Similarly, tables of contents are often the work of editors as much as authors. (Source: one of my parents is a published author and former contract indexer.)
Yeah, we know. Also, we imagine there used to be a lot more people in the book indexing occupation before computers came along and automated so much.
That's what git and other SCMs try to do: they automate away the processes of maintaining history so you don't need to hire a full-time SCM maintainer to do it.
an electronics engineer, maybe. An electrician less so: they should have a rough idea of how it works, yes, but the type of electrical circuit an electrician has to deal withis very different in all but the basics from those inside a multimeter.
I didn't say that. I said that the electronics in a multimeter are very different from that of a house. I wouldn't expect someone with a lot of experience and knowledge in one to be competent in another.
37
u/[deleted] Jun 19 '14
Every developer should use an SCM - not "be interested in it", unless they are developing one. The ideal SCM would be invisible to the developer.
Analogies, analogies...