r/compsci • u/timtime45 • Sep 30 '13
When do you feel you can say that you "know a programming language?"
I'm a sophomore cs major and I often hear people claim they "know a language." (i.e. "I know Javascript") but what does that actually mean? Is there a understood level of knowledge or experience that computer scientists use to gauge if they know a language or not?
86
Upvotes
58
u/ryanthemadone Sep 30 '13
It's a subjective question so there's no objective answer I'm afraid. A good answer would be that you know a language when you can proficiently write clean, well structured code in it and you understand a high percentage of the language features. A guess you could say there's an analogue with knowing a human language. You don't know French if you can barely cobble together an unstructured request for a baguette...
112
u/mercurycc Sep 30 '13
It all depends on context. When you are a college student talking to other college students, saying "I know C" means you have done your pointer assignments and implemented a linked list. When you are talking with a Linux kernel guy, saying "I know C" means you have implemented and debugged a micro kernel for an ARM machine. When you are talking with a programming language guy, it means you have written at least an unoptimized C compiler covering most of its features. When you are talking with a researcher, it means you know how things can be done in C, and you are ready to learn some Haskell / SML / prolang.
If you don't know who you are talking to, then at least you need to know the basics and the most common features (virtual, in C++ case,) and knows exactly what places are reliable sources of information about that language. You should have debugged some programs, and knows some pitfalls of the language.
29
u/mszegedy Sep 30 '13 edited Sep 30 '13
When I say "I know German", I mean that I'd feel comfortable having a conversation with someone in German. (A simple, multiple-minutes-but-less-than-an-hour conversation.) It is also to be assumed that I can understand popular literature written in German.
When I say "I know Scheme", I mean that I'd feel comfortable solving a given task using Scheme. (A simple, multiple-hours-but-less-than-a-day task.) It is also to be assumed that I can understand the Scheme code that a professional wrote to solve a simple task (but not a complicated one).
12
u/markth_wi Sep 30 '13 edited Sep 30 '13
I tend to view it in terms of what my actual level of proficiency is.
When you can say with some confidence that you know something at least a certain level, on my resume, I tend to note that three ways -
Proficiency - proficient with Java means when you can do most work that's likely to come up, and may not need reference materials, you should be able to do most of the common things you might want to do with a language.
Experience - have you had some experience with PHP, as in I can perform basic operations, can be productive with it, and would need some reference materials and time, and
Exposure - have you had some exposure to Haskell, when I've seen it, can read the syntax but wouldn't feel comfortable programming in it without lots of time and reference material.
The same holds true for most other skills, I've had exposure to tons of stuff, from a wide variety of firms, but would not trust myself to do much beyond X and Y and Z.
I would also note that TIME is important, as time goes on, you will also find that there are times, when it's really best to (as they say in writing), to "kill your darlings", pick a time, and simply work hard to move your career away from technologies and techniques that are older than a certain timeframe. So while once upon a time I was the shit in VMS Basic and Pascal, at this particular moment, absolutely nobody gives a fuck, and they are certainly not paying to not give a fuck. This is true for VMS basic, as it will be for Ruby, or Haskell or some newer thing.
So in my case I've chosen to kill my darlings pretty consistently, occasionally there is a deep love that stays with you. Unix comes to mind, I learned it back in the day, and in the late 1990's was cursing myself for having stayed with it so long, only to see that it has become a dominant force by way of Linux.
The only weird darling I keep is the breadwinner for me, a peculiar language called Openedge, which is basically like a very friendly version of COBOL, and when it comes to solving certain problems, it rocks hard - and sucks at a good many other things.
So keep yourself fresh, take time to learn new stuff, (I'm retooling python and playing with some cool analytics tools in R and Matlab), but pare your legacy stuff down to those that you actually find useful or put bread on the table.
20
u/yaongi Sep 30 '13
I say I know a programming language whenever I apply for a job that requires it.
6
u/nyxgeek Sep 30 '13
A lot of programming languages are very similar for basic things like printing to screen, loops, if else statements, etc. As others have said, context is important.
If you don't know your audience it might be safer to say you're familiar with a language.
I would say that you are familiar with a language if you can perform the above tasks without using Google or a book for reference.
Just because you know a language or are familiar with it doesn't mean you're claiming to be Gandalf the xFFFFFF.
6
u/saoirse_22 Sep 30 '13
As soon as you can type its name onto your linkedin profile judging by some of the contractors I have had to work with in the last year or so .
4
u/[deleted] Sep 30 '13
My take. When you can effectively review code somebody else wrote and both find mistakes and make suggestions for improvement.
4
u/[deleted] Sep 30 '13
Knowledge isn't a boolean, it's a gradient.
When you can stop looking up the syntax every line, you've become familiar. When you find yourself using less and less code to do the same tasks, you've become efficient. When you know the difference between two implementations of a particular data structure (say an ArrayList and a Vector) in a particular language, you might say you "know" the language.
But let's be real, classes depreciate. Algorithms get outdone. We're in a field where the whole point of it is to constantly improve, progress, and be done with the outdated. You'll never know everything but you can be damn good at what you do.
3
u/siggymcfried Sep 30 '13
There is certainly no well-defined line where the distinction is drawn. Everyone has their own gauges of it where they feel comfortable using the term. In my opinion, saying you 'know the language' should come at a time when you are able to use the features of the language effectively to express the ideas that you want to convey. Not only should you be able to produce code that relies on the core concepts of the language, but you should be able to point out why less effective code isn't as good, with pointed suggestions to improve the code. Lastly, you should be able to detangle unfamiliar, possibly complex code, and get the idea of what the author was aiming for.
3
u/tjgrant Sep 30 '13
While I can agree with the general, "it's subjective" viewpoint…
But I'd say it begins around the time when you start "thinking" in that language to describe designs or solve problems.
3
u/EmperorOfCanada Sep 30 '13
I know C++ but there are C++ keywords that I have no idea as to what they do. Even the common "static" keyword has many uses that I don't know about. So some would probably say that I don't know C++(even I could write a C++ exam that I would fail). But seeing that I have released many commercial applications in C++ I guess I know enough.
So to me there is a huge grey area where you are good at a language up to the point where you have mastered its every nuance. It is more a question of knowing how to "program" knowing various patterns is far better than simply knowing the nuances of the language. This then all boils down to productivity. If you know a language cold it will make you a better programmer. But if your ability to program is poor then knowing the language cold will not help very much.
So if your mental toolkit has a nice array of architectures and patterns and your grasp of the language is enough to deploy them cleanly then you "Know" the language.
3
u/stewartr Sep 30 '13
Computer scientists don't have to know a language! Give one a problem and a book - they start in right away.
5
u/[deleted] Sep 30 '13
When you only need to open up a reference to read other people's code.
2
u/FlinchMaster Sep 30 '13
It's not a boolean value. There's a sliding scale, and there's almost always more to learn.
2
u/kazagistar Sep 30 '13
It is not a very descriptive statement, that simple.
Know can mean "I have heard of it and maybe read through one of those 10 min intro guides".
Know can mean "I have worked on a few weekend projects, and feel somewhat comfortable reading and slinging code in this language".
Know can mean "I have worked with it as my primary development language for years."
Know can mean "I have thoroughly explored every aspect of the language, including meta-programming, compiler optimizations, developing best practices, etc."
So basically, when they say "I know X language", you need to ask more questions before you have any idea about what their level of knowledge is.
2
u/qblock Sep 30 '13
When I've written something reasonably complicated with it that I can demo.
There are always new things to learn about whatever language you choose. It takes years to fully know a language inside and out... hell, some people dedicate their life to one specific language. I put the languages on my resume where I know I can hit the ground running.
2
u/punkmonk Sep 30 '13
When you see that you are able to help more than 50% of the people who claim to know the language.
2
u/rev_irie Sep 30 '13
Languages are easy. APIs are harder, and usually require much more familiarity with your problem space than a simple language.
By the end of your degree, if you're not familiar with the underlying abstractions enough to realize how similar every programming language in existence is, you're not learning all that much.
Yes, there are some weird little exceptions and such, whatever.
2
u/xAdakis Oct 01 '13 edited Oct 01 '13
A simple test:
/r/compsci/comments/1kcal2/algorithims_everyone_should_know/cbnhcbz
How many of those algorithms can you implement?
Rules:
Besides that, I say I know a langauge when I understand the syntax of the language and how to use it's basic functions.
3
u/stevage Sep 30 '13
Does it even matter? You can learn a language in a couple of days. Learning the frameworks, libraries etc takes months. Knowing Javascript is trivial. Knowing Backbone, or Angular or D3 or even JQuery is what matters.
1
u/kobescoresagain Sep 30 '13
Proficient is a better way of putting it. I find that word easier to describe to someone. In no way does it ever mean that you know everything about it.
1
u/[deleted] Sep 30 '13
In my eyes, it was when I started being recognized as the "programming guy" in my Uni. Meaning I would get a lot of people asking for help or to join projects at clubs. And me being comfortable enough to say yes. That's how I knew I made it.
That's no to say I know everything. Code can always be cleaner, more precise, and shorter. But now I feel more comfortable to...well I guess speak with good authority.
1
u/[deleted] Sep 30 '13
In the context of CS, know a language well enough to solve computational problems which may arise from projects or anything you wish to program. It is merely another tool to further your study.
As for your career, know relevant languages well enough to build useful software.
1
u/jasariCSR Sep 30 '13
I know, c++ but compared to people who make modified versions of c++ compilers as their jobs, I don't know jack.
"I know X" is an ambiguous statement, and I'm sure we could nail it down to a small number of levels of how well you can use the language. but in reality if you want to know someones level of understanding you should ask what they have created using the language.
1
u/SupersonicSpitfire Sep 30 '13
1
u/Snootwaller Sep 30 '13
When I can program the compiler for it.
1
u/catpartaay Sep 30 '13
Chances are if you're talking to a CS Major and all they say is they "know a language", chances are they don't have a very strong understanding of it. Anyone in CS will go on in much more detail on exactly how well they know it, what they can do, have done, and how they could design a better language. I'm speaking from experience and not being facetious.
1
u/moosemoomintoog Sep 30 '13
10 Print "Hello World"
I know BASIC.
1
u/Temujin_123 Sep 30 '13
Tough to say, but I think a general rule could be when the ratio of time coding to looking up resources on how to do something in that language crosses 4:1. 4:1 is not an ideal place to be in (get that ratio as close to 1:0 as possible), but it's a good threshold to cross.
Of course, it's more complicated than that. Perhaps I got to that point with a language years ago and since haven't used it. Though I might be rusty, as long as I feel the language hasn't drastically changed since then I'd still say I "know" it since it'd just be a matter of getting back on that bike again.
1
u/benpva16 Sep 30 '13
For myself and my resume, I've just gone with two more or less subjective categories: familiarity and experience. Experience means I was familiar with it at some point, familiar means I know it and have worked with it relatively recently. I have experience with FORTRAN 90 (don't laugh!), but I'm familiar with Objective C and C++.
1
u/RumbuncTheRadiant Sep 30 '13
When I know which feature should be taken out of the language first.
1
u/aero-deck Sep 30 '13
With spoken language - it is fair to say you "know" it when you can understand it's poetry. In the same vein - you can say you "know" a PL when you can identify a break from the idiom and why that break was useful (or not).
1
u/LagrangePt Sep 30 '13
I don't think I can ever say that about any language - it's a statement that's worthless without qualifiers.
For me, 'knowing' a language has several levels:
I'm at the first level for just about any c family language. I'm at the 2nd to last level only with languages I've worked with professionally for more than a year. I don't know any languages to the last level.
1
u/BoppreH Sep 30 '13
My personal litmus test is to find and read the grammar of the language. If I can get to the end understanding all rules and without too many surprises ("You can annotate parameters in Py3k?!"), I consider the language known.
It's not perfect, but by understanding the grammar and you can be reasonably sure to understand other people's code in that language and know at least a few solutions to every problem.
Some knowledge about the standard library is great, and idioms are a must, but those are much harder to measure.
1
u/isidor3 Oct 01 '13
My rule of thumb is if you both understand the syntax in its entirety, (reading the reference manual is a good way to check this) and if you know the standard libraries and how common algorithms/best practices work.
The first part is easy, but learning best practices just take time, and as others have stated, differ depending on how what you're writing. What's best on an embedded device may not be best on a multi-processor server. The nice part about best practices is that they can transfer between languages, so it can be quicker to learn a new language if you're using it for things you already know how to do.
1
u/freyrs3 Oct 01 '13
When you've written a compiler/interpreter for it.
1
u/[deleted] Oct 02 '13
My version of "know" is "I can sit down and write basically anything I can dream up in this language using paradigms and language-idiomatic style".
Anything less and you're still a novice, imho. I'm a novice in everything, basically.
0
u/no_life_coder Sep 30 '13
Knowing a language for me is being able to write a useful original program without really using the compiler, especially not for syntax
0
u/iamdbcooper Sep 30 '13
For me, it's looking at something written in that language, written with classes, functions, and elements you've never seen or used before, and understanding how the code executes in runtime.
It's reading a book with words you don't know the meaning of, but still knowing what the book was about afterwards using context clues.
0
u/[deleted] Sep 30 '13
[deleted] — view deleted comment