r/computerscience • u/[deleted] • Jan 18 '20
Knowing a programming language is more than working with one.
Short rant. I saw some video about some 11 year old genius who claimed to know 19 programming languages. Now he may very well know all 19 extensively, ill give him the benefit of the doubt, but where do we draw the line? I have personally worked with close to that many languages. I dont consider the fact that I can write a program in a language to mean that I know that language. I only know maybe one or 2 languages. Anyway, I just get kind of salty when I hear people saying they “know” all these programming languages. No you do not.
85
u/BrippingTalls Jan 18 '20
Claiming to "know a language" is a red flag for someone who lacks a formal education in computer science.
Knowledge of mathematics, data structures, and algorithms will allow you to use any language you want. It then becomes a matter of choosing the best language for solving a particular problem.
20
u/400Volts Jan 18 '20
Yeah, the difference between "knowing a language" and "knowing how to program" is like the difference between knowing a bunch of Japanese words and being able to speak Japanese
3
Jan 18 '20
i'm a programmer with no formal education and this certainly used to be true for me. i thought programming was all about learning various programming languages. this is how various external forces (pr groups publishing astroturf written content, recruiting agencies, hiring managers, tv portrayals of IT, etc) present programming, because it's the only way a layman can arbitrarily measure a programmer's value. the need for people who fundamentally don't understand what we do to be able to quantify what we do is sometimes very destructive.
2
u/username_of_arity_n Jan 19 '20 edited Jan 19 '20
I agree, generally, but there's outliers like C++.
The whole language is full of idiosyncrasies and undefined behavior, supports a bunch of (often totally incompatible) paradigms, and requires particular domain knowledge (binary compatibility, linkage, platform-specifics, etc.). In that situation you need at least one person who is "fluent" in (a given "dialect" of) that language and you need an appropriate team dynamic to keep things from getting out of control.
So it may matter, depending on the language, the problem space, and the organization.
1
u/alpha-201 Jan 18 '20
Completely agree. It’s why I find it puzzling for job adverts to say “3+ years experience with C#”.
25
Jan 18 '20
Read an article about child prodigies, it’s interesting in that they tend to not do anything original - ie they aren’t in general geniuses who invent new things in their field. But instead are able to focus on an existing subject and have an abnormal desire to learn it.
In this case it could be that this kid has this drive to learn programming languages. And sure he’ll probably know them. But might not have spent time on the other aspects of comp sci.
I’ve used loads of languages in my time; general programming languages, domain specific ones etc and the’lly be someone who only knows a bit of a single language but is able todo something I’ll never be able to and that’s frigging annoying.
Speaking of which I saw a YouTube video of guy showing how to program in PowerPoint (using slides to store state etc.) it was interesting as approach was quite different and pretty smart todo that.
4
Jan 18 '20
I think, without really knowing very much about it so this is all just a hunch, that children with extremely good (or even eidetic) memory can be prodigies because, in relation to their peers, their abilities are so advanced. Whether or not these children are geniuses or become so probably depends on whether or not their creativity, imagination or however you characterise it, matches their powers of recall.
2
u/MayorOfBubbleTown Jan 18 '20
I was a kid that loved playing around with different programming languages and thinking a lot about what happens on a low level when a program runs. Took way too long for me to realize I wasn't very interested in the things I was building because I was more interested in compilers and interpreters.
16
u/Peter_See Jan 18 '20
If you are a reasonably experienced programmer, it shouldnt take you very long to "learn" any language, especially since if you know what you are looking for you can look it up. Especially if we are only considering functional programming languages (not logical resolution languages like prolog or golog), generally you just need to know: how do I define functions, arguments, logical comparisons and disjunctives (if, else) and loops and then function calls. Rest is just semantic syntax. Maybe onces you get advanced you can learn the nuiances of a language like how for example python can pass functions as arguments, but thats more of a neat feature than an essential one. What takes time and is hard to learn is how to program efficiently, design principles, how to use datastructures, and of course math.
8
2
u/SV-97 Jan 18 '20
Well it depends on what you consider "knowing a language". I can write functioning code in quite a few languages (10 or so?) and would thus say I know them - but I certainly can't write idiomatic code in all of them, know their tooling etc.. There also are languages that are fairly easy to learn (e.g. Factor) and others that are nearly impossible to learn completely (e.g. C++) or languages that you can write functioning good code in - but that code may not be considered idiomatic (e.g. Haskell 98 and modern Haskell or old C and modern C or old FORTRAN and modern FORTRAN etc.) - so people that only learn simpler languages could very well know how to write idiomatic code in lots of languages
And lastly it's worth considering that the more languages you already know the easier it is to pick up new ones
2
u/tripmytrigger Jan 18 '20
I agree and I would also like to add that a lot of programming languages just have different syntax which can be easily memorized by any person. Does that make you into a good programmer? No, because it's not just about a fully functioning code. Let's say person A and B writes a code that can do the same task. Person A uses 3 lines and person B uses 1000 lines, can you really say that person A or B did a better job?
2
u/mymar101 Jan 18 '20
It's kind of like someone claiming to know 20 spoken languages. Those kinds of people are very rare and spend all of their time practicing or learning them. I personally know French English, a smattering of Italian and German. I also know some Russian. Most all of the Italian German and Russian comes from me being a classical musician, meaning I can tell you how to say play faster! Or slower. But not give you directions. Why would you need to know 19 programming languages? I personally only learn what I need to know to get a job done. Or out of curiosity.
2
u/alpha-201 Jan 18 '20
I feel like once you know a few languages you can basically pick up any and start programming in it. Like if you know C# then Dart and Typescript are a breeze.
What interests me as what is counted in this number and where do you draw the line? HTML, css, SQL, graphql, json, xml?
2
2
u/edgargonzalesII Jan 19 '20
I know like 10 languages on my resume and even have projects too back that up. But if you ask me anything on languages that I havent worked with in over a year (so anything that isn't python, C#, Java, or JS), then I'm screwed to answer.
3
Jan 18 '20
Who cares it’s a kid and it’s still pretty impressive that he’s worked with 19 languages at any level
2
1
u/_________KB_________ Jan 18 '20
I'd argue that having a working knowledge of a language is by definition "knowing" that language. Whether or not that knowledge is beginner, intermediate, or expert level is a whole different story.
1
u/pickausernamehesaid Jan 18 '20
I hate it when someone says: "Well he has X language on his resume, so he'll be perfect for this role." I've seen people put Python on their resume after an intro to CS class, but that doesn't mean they will just be able to jump into any project with that language.
1
1
Jan 19 '20
In my opinion, the most important part of software development doesn’t include the language. The most important parts in my view, are all process and conceptual.
Requirements, domain exploration and design, technical specification, developing use cases and stories which all help inform the architecture. Building your development pipeline and processes, building algorithms. Finally you have the iteration and delivery process, which is really important for software quality.
The language will not solve all your problems. Personally I maintain to this day that the most important part of development is communication / requirements. If you clearly identify the business domain, the language is unimportant unless there’s some specific thing you’re looking for.
That’s my two bits worth.
Side note: even computer science doesn’t cover all these topics. Compsci tends to be math and algo heavy with little focus on product delivery and running development from a business perspective. It can get a little academic about problems rather than practical.
1
u/JOHNNYB2K15 Jan 21 '20
Quality over quantity is how I like to view programming, and if the kid can make high level programs in each of the languages, I'd be impressed. And no cheating either; each language needs to be somewhat different and not just a syntax change (a jump between C and Java, for example, would be valid).
1
61
u/[deleted] Jan 18 '20
Its just like human language. I can say hello in 20 but know 3 well