C++ is a play on the increment operator (++) in C. The language was originally called C With Classes, but this was dropped in favour of the less wordy C++ or C increment. To describe a language which was C but a step improved / increased.
I can only speak for my personal preference but if you could show good works for that period of time I don't see it being an issue. Use the few years and huge vacation to contribute to major open source projects, stay current and keep coding. I don't see why it should be an issue. It shows flexibility, aptitude, and a drive to better the self.
I don't think they actually have a higher failure rate than other large scale web applications. They are just very open about their failures and data. http://status.github.com/ reports an uptime of 99.8% for the month. Not _fantastic_ but very very good.
There are already two letters which serve this purpose. Eð /ɛð/ (capital Ð, small ð;) and Þorn (capital Þ, small þ;) What's the point of yet another letter?
"[The greatest seducers in history] aggressively escalated physically with every woman they were flirting with. They began touching them immediately, kept great body language and eye contact... Even when a girl rejects your advances, she KNOWS that you desire her. That's hot. It arouses her physically and psychologically."
"Decide that you're going to sit in a position where you can rub her leg and back. Physically pick her up and sit her on your lap. Don't ask for permission. Be dominant. Force her to rebuff your advances."
"Pull out your cock and put her hand on it. Remember, she is letting you do this because you have established yourself as a LEADER. Don't ask for permission, GRAB HER HAND, and put it right on your dick."
--
This is not okay. This is sexual assault trumped up as "Dating Advice".
While I am not a mod on SO I have been on the site for a while and have been answering for most of that time. As such I do have edit rights on questions general and have the ability to recommend posts for deletion.
Generally speaking mods close questions for quality reasons or because they don't fit the format of the site. The F.A.Q. is fairly explicit about what SO is for and while I can only speak for my self, I do my best to adhere to those rules when closing questions.
As for locking questions, that is a bit more subjective but in most cases they are locked because they are well known and they have been solved. Being that there is no need for additional answers they are closed such that you don't have the spam issue of "Thanks" posts.
I doubt that there is a systemic pattern of censorship and rather what you see is the normal operations of a very large and famous Q.A. site with a very specific purpose.
Google just started considering .io as a gccTLD ( which is basically just a ccTLD which they consider as a gTLD ( which means they don't consider it localized but rather a generic TLD ))
I just buy straight from nic.io. You only have to fill out the forms once and while I did do it a few years ago I don't remember it being all that bad.
The first thing that jumps to mind is "Why are you forcing your self to do
this?". Which I won't address, but it might be something worth seriously asking
your self. If you don't like it, why are you wasting the cycles?
I find in programming, like in many creative disciplines, there isn't a singular
Aha! moment but rather a series of them. One must continuously learn and
work. The process is generally prodigious amount of toil and frustration for
brilliant moments of elation and clarity.
The ability to do large projects comes from doing large projects. You can read
all you want about project management and software design but until you are in
the thick of it, none of that matters.
I became a much more liberated and free programmer when I accepted that all of
my code is crap. In point of fact, most code is crap and in light of that I
strive not to write good code but to write better code than I did
yesterday.
In short, forget about worrying. If you want an idea of organization then read
through the source of a large project. Better yet, start one. Think through the
issues that arise as you try to manage a large project. You will fail, this is
okay, good even. Learn through failure and don't invest your self in your
code. You are not your code. Be proud of your success and toil but don't worry
what others think. We were all bad programmers once and most of us still are.
Note: This is based on my personal taste and experience. I am a professional in
the IT industry with over ten years programming experience. Not a huge amount I
guess, but definitely not that shabby. Currently I am not a professional
programmer per-say, but it makes up a large amount of my daily work.