C++

Your "computer logic" shouldn't be the same for every language because not every language use the same logic. IE: If you are trying to solve problems in a functional programming ambient by applying procedural ways of thinking then you are wasting a lot of potential and simply coding the wrong way.

1º I never said every language is OO. At least read yo shit.

2º Like Jason said, your logic will work for more than just programming.
You know that right? You know that when you apply for a programming job(dev) they will test your logic. And not everything about these tests have to do with programming, but your capability to think correctly. As you encounter problems every single day. (I mean every....)

Learning from language to language is just syntax. You can't obviously apply the same logic everywhere. But that's the biggest challenge, training your brain to find different solutions for different problems. When your brain is capable of programming, it won't change that much from Programming language to Programming language.
You will just need to apply different syntax or maybe even logic, but that doesn't mean that you will need to built up your logic again like you did at your first language, of course not.

The most epic solutions for problems won't even require you to know the language. You can pretty much have a decent conversation about a programming logic problem without the need of knowing the language.

Actually when I started to program a few years ago, I started by doing Pseudo-Code and Flow-charts. What was the next step? The easiest.. Write the same thing using C Syntax (Or whatever syntax you could have used). All the logic was on the paper already, so what's the problem?
I got used to always have a pen and a paper with me to train my logic first with paper. Then apply it. (Using charts, mainly when I used to Program with Linked Lists and Pointers)

----

TL;DR: Brain Logic is the most important factor here. Not the only I know. But..

That in a nutshell is any-software-job-interview.. lot of times they don't even care about if you whiteboard a problem in C++/C#/VB or even pseudo code, but they want to see you think things through & be able to not only grasp the problem (usually there's some gotchas involved you'll miss if you rush right in), but also be articulate enough to explain it to the interviewer after which you can scribble out in the language of your choice (or relevant to the position naturally).

And yes proper design like Jason mentioned is KEY to not having to rewrite your app 6 times, or have to gut it just because you need to add a feature. I've worked with/for people who think taking a week or two up front to do solid design is a 'waste of development time' and then are shocked when they loose 3-9 months in a rewrite that wasn't anticipated... For me the design part is the fun part.. the grunt work of actually coding it.. meh that's easy and some code monkey could do that

From a professional perspective Jason & Brinuz have a good mindset and an good basic understanding of how the software dev business world operates I unfortunately don't see around here too often with all the 'OMG i'M a L33t H4x0r wh0 kn0w5 C++ !' .

Scuarplex DOES make a valid point about learning things the 'right' way per each language, you obviously don't always approach things the same way you do in C++ vs C# vs say Java or (and sometimes you can't - multiple inheritance anyone?) and i've seen all too often inexperienced developers claiming they 'know' a language and then try to shoehorn in practices that really have no place in that particular language.

In the end (also in reference to ' that other' thread) There's a tool for every job - sometimes it's asm, sometimes C++ , PHP, Java or (and yes this is coming from someone who used to be a hardcore C++ only developer) even .NET There's stuff to nitpick and 'hate' about all of them, but they're all proven development languages & tools to get a specific job done.

(talk about rambling.. think I got you beat there Jason haha)

He said s0beit