When one finds themselves tooling and toying around alone at the computer. It's simply, you and the machine in a vacuum. The only language that matters at that point is the one you choose to communicate with to the machine, be it a low level or high level language. So long as you have a good grasp of that language, the machine will bend to your will and do what you command it to.

This in itself is enough if you program for you and only you alone. The moment you decide to build software for others, it becomes immediately obvious that you must have a great command of at least two languages. The one you speak to the computer to, and the one you communicate with to other people. In essence when you build software for people. You are an interpreter between the computer and your client who doesn't speak the computer language. A poor grasp of either language will lead to disaster as is the case in any interpretation duty.

I see a lot of desire to learn programming, but yet very few to get a solid grasp of English which happens to be the lingua franca for programmers. My fellow Nairalanders, if you must be a good programmer, then I urge you to get a good grasp of the language. You will need a fine balance across the four cores, speaking, listening, writing and reading.

Speaking is important when you wish to communicate an idea across to someone who is non technical. You must find ways to relate the abstract concept of programming to a layman in a concise way. Listening is also very important. As we all know, natural language is very ambiguous and with passive listening, you are bound to find yourself at a cross road where you will not be able to move forward without going back to your client to reiterate what was already discussed. In as much as we need to stay agile when developing, we want to reduce the back and forth to a minimal or else it will translate into increased development costs due to the time increase in communication.

Writing and reading likewise parallel speaking and listening when it comes to understanding software specifications. They are likewise more so important, because this is the most direct means by which most of us will learn. If you wish to grow, you must read the most important books and papers in the fields that concern you. What you will come to find out is how dense such material usually are even when you have a firm grasp of the prerequisites. Without a good command of the language, you will miss out in understand the latest and relevant research in the industry and have to settle for titbits published in mass media.

I therefore, urge you all to not just obsess about your favourite language, be it, C#, Java, Python, Lisp, etc. But to also obsess about the main language in your region, English, Chinese, German, etc.

I see the angle you are coming from with this. Indeed being well rounded with regards to language definitely is an advantage, especially when business facing.
However, some of the best programmers I know are not the best communicators. They can cut the best code for days but cant write a report to describe it. They cant present a solution without confusing themselves talk less of others. These guys just want to be told what to do and they do it extremely well - Cut Good Code.
So I would second that learning the language of your region is important but if your are a good problem solver you can thrive in this industry. Most times you can just let your code do the talking