Hacker News new | ask | show | jobs
by cookingwithrye 4695 days ago
I understand where you're coming from, but I strongly disagree.

I've worked with multiple living counterexamples to your point - they only knew one language (sometimes old and non-maintained), but they could blow the next whiz-kid out of the water in terms of logical thinking and its application to software development.

IMO the only requirement to being a "programmer" is "programming", and restricting it any way beyond that hurts the field.

The guy that's been doing systems programming in C++ for 10 years should probably be considered a "programmer" despite not knowing the latest compile-to-js language of the week.

1 comments

I'm not even talking about the little languages that just come in and out of fashion all the time.

If you know c++ you could basically roll right into C#, Java, PHP, etc in under a week and be doing real work in them. Maybe you wouldn't have the intricacies down immediately but you could be doing production code level work very quickly.

You could, but I wouldn't recommend it.

Learning a new language, say C++ -> Java is WAY more than just learning the syntax. There are best practices for solving certain kinds of problems in each language that differ between language.

Sure, there is a high level similarity between the solutions (hey, its just the observer pattern, right?), but there are also likely (IME) to be many critical differences in the details.

You could probably write C++ code in C#, Java and PHP, but it would be hideous. I've seen Fortran written in C, and Pascal written in C++, and C written in Java, and it's generally an unholy mess.
That may be true for many languages, but if those people never roll into that sort of situation it's probably fair to still call them programmers.