I think in pseudo-code, then figure out what language is best suited for the task.
'cause it's actually a bit of a non-answer, when you think about it. Saying 'pseudo code' means that the language you think in has some informality in its syntax - but presumably you still have some fixed understanding of what it does?
If it has no fixed syntax and no fixed semantics, then is it actually helpful as a mental model? I would argue that it is not.
(Note: I'm not just being antagonistic here, I'm genuinely curious. I don't think in terms of "syntax", so this is all a bit alien to me).
My assertion is that when people say "I think in pseudo-code", they actually mean "an idealised version of language X", where language X is some paradigm or language they understand well.
I just wrote a blog post about this very subject, based on the flood of comments (shameless self-promotion follows):
Loop from 1-100:
if the current number is a multiple of 3, print "fizz"
if the current number is a multiple of 5, print "buzz"
otherwise, print the number
print newline
<?php
for($i=1;$i<=100;$i++) {
if($i % 3 == 0) {echo("Fizz");}
if($i % 5 == 0) {echo("Buzz");}
if($i % 3 != 0 && $i % 5 != 0) {echo($i);}
echo("<br />");
}
?>Overall, I agree with the parent because before you can dive into coding, you have to think of the problem and solution abstractly.
But which language is used for writing out the solution? Whichever is the best tool for that particular problem.
While I may express the solution in Objective-C, PHP or Python, I always think of the solution in terms of logic.
Also, if you have experience in multiple languages (and environments), then you're less likely to be constrained by a single mindset.