14 ms·
The traits of a proficient programmer
- mod 10y ago> But the place where the intermediate programmer tends to get stuck ... is thinking that the difference between a beginner and an expert can be measured in how much stuff you know. > And at its essence, proficiency is about "why you do things a certain way"—It's the difference between understanding each of the parts of a problem individually, and understanding how the parts fit into the whole. So I guess it is about stuff you know. The article then goes into further specifics about how you have to know when to apply what you know.
- vonmoltke 10y agoI interpret "stuff you know" as easily-recallable facts. Obviously at the highest level view knowledge is what separates a beginner from an expert. Knowledge is much more than "stuff you know", though. It is about understanding why, knowing how to handle non-textbook situations, and knowing where to find the facts you need when you need them.
- collyw 10y agoI think he is arguing for having depth as well as breadth of knowledge. Certainly when I am looking at CVs and see every framework under the sun listed when we are looking for a Django dev, I assume they have done the Django tutorial, maybe a little more then moved onto the next framework.
- 1propionyl 10y agoI wish it was considered acceptable to provide bar charts of relative self assessed competency with a set of tools. With error bars of courses.
- crispyambulance 10y agoIt is not acceptable because it is utterly meaningless. There's no way that a scale can represent something that is intrinsically subjective.
- atoko 10y agoIt might be subjective but it's a good indicator to how much guidance the person needs initially. I think it would be useful.
- SubiculumCode 10y agoSubjective ratings often predict reality quite well.
- cema 10y agoAnd yet, people are often asked to estimate their level of specific knowledge "on the scale of 1 to 10".
- gr3yh47 10y agoon my resume I list specific skills (i.e. AWS, Node.js) under several categories (i.e. ops, programming) and for each skill listed i format them bold, italic, plaintext with a legend showing that those map to adept, proficient, and working knowledge
- abraae 10y agoSuccessFactors HR product used to do this (may still do). You had to drag and drop your skills within a kind of bell curve. It forced you to prioritise only one or two as your super skills, then a larger number that were your next top skills, and finally a whole bunch of stuff at the lower level. It worked well, though it was in no way the final word on this kind of very challenging problem.
- CoolGuySteve 10y agoA dungeons and dragons player would recognize this as the semantic difference between the "intelligence" and "wisdom" stats.
- gaius 10y agoOr in The Wrath Of Khan where Kirk and Spock realize Khan's intelligence but inexperience are his weakness in the Mutara Nebula.
- TheOtherHobbes 10y agoNo, it's not about stuff you know. This was posted recently, but it was so good it's worth repeating: http://blog.robertelder.org/50-interviews-with-facebook-twitter-amazon-others/ http://blog.robertelder.org/50-interviews-with-facebook-twit... The interesting point is the distinction between skill and talent. Skill is close to competence. You can solve well-defined problems using standard tools and practices. Talent is close to proficiency. You can not only improvise good solutions for novel problems, but you can also prioritise problems intelligently to achieve strategic goals, because you have a clear view of how the codebase fits into your business or project. Without talent you can waste a lot of time by picking the wrong tools, or using tools in the wrong ways. Even though your code may be perfectly correct, the solution built with the code can still be completely wrong or useless. In fact talent is somewhat orthogonal to skill. You can have an untrained version of that overview talent, but it's not so useful if it isn't grounded in skill. When you have both, you have real proficiency - good code doing the right things to solve the right problems.
- encoderer 10y ago> Talent is close to proficiency. You can not only improvise good solutions for novel problems, but you can also prioritise problems intelligently to achieve strategic goals, because you have a clear view of how the codebase fits into your business or project. Calling that aspect talent and not just another skill is somewhat elitist I think. It can be learned. It's just another skill. (Haven't read the link.)
- mod 10y agoThat's just skill and superior skill. Both require you to know stuff. And in programming, skill is just knowing more stuff (knowing how to apply things). In other trades, skills might be swinging a hammer well or being able to chop potatoes really quickly.
- rabidrat 10y agoI think you're splitting hairs. The parent and OP are saying there is a qualitative difference, and by saying "just X and better X" you're trying to say that the difference is merely quantitative. In my experience, when someone makes a claim of qualitative difference, and someone else insists that the difference is merely quantitative, it's because the latter person has not themselves seen the quality of the difference. This applies in many fields. And that's compatible with my personal understanding here as well. As someone who has been programming for 30+ years and is generally considered proficient, I agree with the parent that the difference is qualitative. This explains a lot of the times when I look at what senior developers are doing and think "yes, that tool is generally useful, but not this time". And it gets frustrating then when they start arguing about "best practices" but I'm trying to make a larger point about "this project".
- deleted 10y ago[deleted]
- adekok 10y agoI'm sure everyone has worked with someone who has memorized a lot, but doesn't know how to do much. Their productivity is limited. There are also people with innate "know how", who can get things done without much background knowledge. They just know how things work. My $0.02 is that experts have both of the above skills. They know a lot more than average people, and have better techniques for doing things. My experience has been that once you reach a certain level of expertise, it's better to "know how", than to know things. For the software I've written, I just forget about the minor details, and have to look them up again. The details aren't important, and just aren't worth remembering. In contrast, remembering the problems and solutions is much more important. The solutions can be applied to multiple problems in a way that simple "memorization of facts" cannot.
- rimantas 10y agoBeing expert means having ability to recognise certain patterns and having skills to apply then. So yes details don't matter much if pattern recognition works fine (and it's ability to work is in some degree dependant on ignoring non-essential details). Which details don't matter is aldo learned through experience. There is a danger of miscategorizing if one gets too confindent and sloppy.
- Digit-Al 10y agoYeah. I used to work with a guy who mainly knew databases, but also had to do some C# as part of his job. He did loads of MS certifications, just to have them on his CV, but was clueless and usually had to ask me how to do anything more than the most simple programming tasks.
- WestCoastJustin 10y agoHere's the supporting "A Five-Stage Model of the Mental Activities Involved in Directed Skill Acquisition" reference link for anyone interested. http://www.dtic.mil/get-tr-doc/pdf?AD=ADA084551 http://www.dtic.mil/get-tr-doc/pdf?AD=ADA084551
- mgrennan 10y agoThis is where the use of "Older" IT people would help. Take all the new ideas and innervation and filter it through the 60 year old IT guy (Knowledge experts). Explain your ideas well with examples. Lesson how that problem has been solved before. Don't build new ideas on old code. Find shortcuts to the results. Don't be naive. Ignorant is better. Naive is not knowing your don't know. Ignorant is knowing your don't know.
- mgrennan 10y agoYes I'm 60 with deep knowledge. Electronics, assembler, system / language / application development, data structures and flow design, protocol design, UI design and now working on AI.
- mlvljr 10y ago..to replace thyself when retired? sorry :)
- BatFastard 10y agoDang it, he has a year on me! I will never get hired ;-)
- acupofnope 10y agoPlease excuse my curiosity: would you consider your work to be more hands on or managerial or both? Have you ever felt overwhelmed with the sheer amount of 'topics' out there?
- Rexxar 10y agoI'm maybe too cynical but I always think the main motivation of such articles is to pretend the author is a very good programmer with the implicit assumption that "if you have an opinion about what make a good programmer, you necessarily should be a very good programmer".
- hkon 10y agoIt's the next logical step after you write a piece which characterizes bad programmers... Same thing only one level lower imo.
- gaius 10y agoESR built his reputation that way for sure
- gtrubetskoy 10y agoI would add to that that I fail to see how much of said advice is unique to programmers and not just human beings in anything they do. Why would you want to be a proficient programmer and not just proficient, period? And if so, are programmers the best source of wisdom really?
- acbabis 10y agoMy criticism of the article would be that there isn't really anything to disagree with. Most STEM people already understand that analytical ability is more important than knowledge; and the people struggling with this are unlikely to gain that understanding from an article. From that perspective, I think you might be right. The article won't accomplish much except make the writer look good. But you're also right that this is cynical. If we're optimistic, this article could serve to give people already possessing some analytical ability a friendly nudge to learn and dissect a new concept.
- rimantas 10y agoMost STEM people should know, that analytical ability relies a lot on knowledge. You cannot analyse how something is made up unless you are able to recognise parts, their relationships and dependences. You need those chunks, patterns in your brain only then you can see them elsewhere and understand the working of the whole.
- yawz 10y agoA competent programmer knows that tomatoes are fruits. A proficient programmer doesn't put tomatoes in a fruit salad. :)
- the_watcher 10y agoI like this. It can be applied in a much broader range of professions than just programming, but it's a nice, memorable analogy.
- Noseshine 10y agoI'm missing an option for the guy who could not care less whether or not a tomato is a fruit or not, because he knows it does not matter at all for his purposes. IMHO the real expert knows what knowledge is relevant and what knowledge is for forum discussions that are just used to kill time.
- st3v3r 10y agoHow does it not? When making a fruit salad, the knowledge that tomatoes don't go in fruit salad seems pretty relevant.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- Noseshine 10y agoYou don't have to know that tomatoes are fruit for that? Your reply makes no sense at all. I say "you don't need to know H" and your reply is "but you do need to know Y"! Not to mention that specifically your reply is something only worth knowing when when does know that tomatoes are fruit, and not when one doesn't.
- Noseshine 10y ago
- SubiculumCode 10y agoSeriously, I misread the title as "Traits of a(n) ancient programmer" My first thought was "proficient"
- SubiculumCode 10y agoand the correct answer to the original title is 'ancient.'
- choward 10y agoNo mention of testing?
- rimantas 10y agoNo mention of scrum, agile and pair programming either. Strange, huh? I'd say *DD is nice-to-have but orthogonal to being proficient. Or sometimes just counter-productive, if all it is is cargo-culting with zero understanding.
- rhizome 10y agoI think testing has inherent benefits regardless of understanding.
- awkward_yeti 10y ago> Pick a small number of specific skills you're simply good but not great at. I am struggling with this one since forever, what are the skills-set a programmer should enumerate through ? like how good they can connect to a DB provider ? or how quickly they can set up a web server ? what qualifies as a skill in this context ?
- ysavir 10y agoUltimately, it doesn't matter. The point of the exercise isn't to get better at those specific skills, but to develop an understanding of high-end proficiency, which you can later apply to other subjects. Like many (proper) learning sets, the content of the exercise is irrelevant compared to the deeper lesson.
- awkward_yeti 10y agoYes I can see the deeper meaning of the exercise, yet, it helps to know what we're talking about specifically. I am not proficient yet, and I would like to be, and I don't think it's one of those (When it happens you'll know it) moments, I believe there is a clear set of skills we need to work through first in order to see the forest for the trees. My question therefore is, what are those skills exactly ?
- practicingdev 10y agoThe web of foundational skills for software development is vast enough that you can't really build it out from the bottom up. What you can do though, is start with small projects and try to understand every piece involved in them, and why you did things the way you did. Repeat this with increasingly complicated projects, testing and synthesizing what you learned.
- awkward_yeti 10y agoSo cross reference the common experiences from different small projects. That does make sense. Have you done that ? Or are you doing it at the moment ? because some hints of those projects ideas will be awesome.
- jcbeard 10y agoProbably the most important bit of the entire article, which you can probably get from many self help career books (applies to all, not just programmers): "Ask others to explain why they do things, but don't just accept dogmatic reasoning. Demand examples and inquire about context, so that you can try to imagine what it is like to be in their shoes. Doing this is tremendously valuable because it allows you to see the strengths and weaknesses of ideas in their natural habitats." One thing I can add is always question. There's a reason kids ask tons of questions, they want to know. Asking questions not only increases your own knowledge, and that of the person answering, but it also creates a culture where complacency is extinct. The one thing I hate more than people that litter are people that say "oh, well, that's the way I've always done it." There's lots more I dislike above that, but...complacency is the death of innovation. Then again, sometimes things just work....but that shouldn't stop you from trying to improve it.
- mVChr 10y agoThis reminds me of the woman who was teaching her daughter to cook a pot roast the way she remembered her mom doing it. You take the meat, cut off four inches from one end and throw that away, put the rest in the pan in the oven at 350 for 3 hours. One holiday when the daughter was hosting grandma came over early to help and saw her cutting the end off the pot roast. She asked why and the daughter said that was how her mom said she did it. "Oh child, I only did that because our pan was too small!"
- xom 10y agoA WarCraft III commentator told the story of how he once saw a pro, during the opening, send his Demon Hunter to the healing fountain on a certain map, and he started doing the same with the same timing on that map. One day he met the pro in person and asked why he'd done it, and the pro said, To see if the opponent's Blademaster was there.
- tbihl 10y agoCan you explain? I'm familiar with the mechanics and abilities, but probably not the tactics.
- okreallywtf 10y agoDespite the reception this article seems to be getting here I find it speaks to me pretty directly and summarizes some observations I've been making lately. I consider myself an intermediate developer (at just under 3 years out of school at my first job) and I feel like for the first year or two I increased my competence rapidly (and with it, salary thankfully) but I'm at a point where without branching out into other areas it will be more difficult to continue acquiring pure competence or I will do so at a flat or decreasing rate because of the increasing complexity of concepts left to improve upon (within my day-to-day work, not including side projects and academic pursuits). On top of that I work with a small team of other developers who are all highly competent but only some of whom fit the description of proficient developers in the article. I think the article describes really well the differences between the two types, and I have tried to nail down what the proficient developers do and how I can acquire the same skills and instincts they have. The main things I have noticed are a) as the article discussed, always being able to debate the pros and cons of an approach beyond just best practices and without regurgitating things that renowned developers have espoused and b) being able to be able to drill into problems in the code-base or our process even if its due to technical debt that other competent developers are willing to work around, but more importantly knowing when it is appropriate to down a rabbit hole and when it isn't. I'm lucky to be able to see the distinction in action and overall I think the article helps to describe a distinction that I haven't been able to verbalize.
- dukerutledge 10y agoSome of these remind me of Ed Kmett's YOW talk: "Stop Treading Water: Learning to Learn" https://yow.eventer.com/yow-2014-1222/stop-treading-water-learning-to-learn-by-edward-kmett-1750 https://yow.eventer.com/yow-2014-1222/stop-treading-water-le...
- rainhacker 10y agoNice article, learned a new design pattern today. Wondering what are some practical use cases of memento design pattern ?
- rhizome 10y agoSoft-deletes, wikipedia article versioning
- rezashirazian 10y agoIf you like design patterns checkout my articles https://shirazian.wordpress.com/2016/04/11/design-patterns-in-swift/ https://shirazian.wordpress.com/2016/04/11/design-patterns-i... It's a compilation of design patterns implemented in Swift, solving a real world problem.
- Namrog84 10y agoI used a simpler analogy in a c++ class I used to teach. Some people might argue that setting a variable to 0 or something is pointless if you now your about to use it. But while technically it could add overhead. The chance of bugs forming from a future refactor is decreased. And those who track down sporadic uninitialized value bugs should know why it's almost always better to just initialize values. And not implicitly always trust the compiler will catch complain and or a future less knowledged developer won't accidentally do something silly. Many habits in programming are formed from habits and we're told to not do thibgs(1 entry and 1 exit. No goto. Etc..) but few can back it up with why and when it might be a worthy edge case
- monksy 10y agoIn C++ you're right. The value isn't predefined unless you calloc. In java there are default values. I.e. for an int it's 0 and a string it's an empty string. There is even a Checkstyle violation for this style choice.
- rezashirazian 10y agoOr in Swift, you either initialize a variable with a value or have to define it as an optional, in which case you are eventually forced to deal with its possible null state. But I digress
- ww520 10y agoWay back when I went for an interview. That was when Java started to get popular. The interview involved some coding, and I set a variable to 0 at declaration. The interviewer asked me why I did that. I said I know the language already initialized it to 0 but I like to clearly document the init state of the variable so others can have an easier time to understand. He said others should have known the language well enough to know the initial state of a variable. We went back and forth for a few minutes on the importance of code reading and code efficiency. At the end I realized I didn't want to work with people who were so pedantic on minute detail of a language. I later declined the offer, not that it was a good offer anyway.
- 10y ago
- ovrdrv3 10y agoIt isn't often that you click on a link to the book referred to and it is the pdf, sweet!
- dingdongding 10y agoAs a programmer I always write code considering if a new guy wants to take over my code, he should be able to understand it and use my code with as little complication as possible. Things should be simple enough that when a new guy takes over your code he can be onboarded soon and doesn't have to ask someone to explain him the magic pattern or secret sauce to under teams code.
- horizone 10y agoI am some what the opposite. The person that comes after me should be able to read and understand what I wrote without line by line documentation. If they can't, they are not fit for the position. Although, if there is a quirk within the code where something needs to be explained, it will have documentation.
- hasenj 10y agoWhat the article describes as "competence" sounds like total incompetence to me. If you learn a pattern from a book or a class or a blog post, and then you apply it in a project just because "the book said so" you are not a competent programmer. This might be an artifact of English not being my first language, but I would reverse the definitions. Proficiency means knowing how to use something. Competence is knowing how to do something properly, which implies having a deep _understanding_ about what is going on. That seems to be how people use these terms anyway (regardless of the dictionary definition). Proficient in jQuery: knows the ins and outs of most jQuery functions and plugins. Competent in jQuery: non-sensical statement. Proficient in git: knows most useful commands and arguments. Competent in git: almost a non-sensical statement. On the other hand: Competent front end developer: understands how to develop a web based application UI from scratch without being tied to a specific product domain. At least that's how I understand these terms.
- practicingdev 10y agoTo me the terms are roughly interchangeable if taken in their general meaning, or at least easy to confuse with one another. But when I wrote this article, I hinged it off of specific definitions assigned to the terms in the Dreyfus Model, which although not exactly commonplace, is an established bit of literature (for example, Pragmatic Press uses Dreyfus Model to indicate expected skill level for readers of their books) So I stuck with their definitions and attempted to restate those definitions (informally) in the article. But I'd be fine with you calling these Thing 1 and Thing 2, as long as they mapped to the definitions provided. What the article refers to as competence (Thing 1) is something programmers generally recognize as valuable, because it is valuable! Essential, in fact. What the article refers to as proficiency (Thing 2) is something programmers probably also recognize as valuable, however... many do fall into the trap of thinking this: Thing 2 is what you get from being really good at Thing 1 in many areas. In truth, Thing 2 is what you get from being halfway decent at Thing 1 in many areas, and then with a view of the bigger picture, getting really good at specific aspects of Thing 1... in the context of your actual work, goals, etc. In other words, Thing 2 = Thing 1 X TheBiggerPicture. Now if I were to use my own way of thinking about this... I actually thing of Thing 1 (competence) as tactics, and Thing 2 (proficiency) as strategy. But I think that could end up leading to an even more confusingly overloaded set of terms.
- tooljob 10y ago>> But a truly proficient programmer fits the tool to the job, not the other way around. A truly proficient programmer finds the right tool for the job, learns best practices on how to use that tool; makes mistakes, learns and improves.
- Vektorweg 10y agoIn short: if you have done it before, you are now an professional who can implement a very similar thing again. For everything else, you are not a professional. Thats how I understand the article.
- jwatte 10y ago"so many people struggle with high level programming ideas, like design patterns" That sounds more like the movement from "apprentice" to "journeyman." Is it really expected that professional, experienced programmers should struggle with the appropriate application of known techniques?
- facepalm 10y agoNobody knows everything, so I must admit I don't see the point of the article. Maybe sometimes you get lucky and have the relevant knowledge for seeing the big picture. At other times you won't have that knowledge. Are you proficient?
- squiguy7 10y ago> Patterns, principles, idioms, libraries, language features—these are all tools. But a truly proficient programmer fits the tool to the job, not the other way around. This isn't a unique statement but many people forget it. We all have our favorite tools and we criticize others that don't have complete parity. Picking a tool to use is often the hardest part considering there are so many nowadays. It's easy to rule out a hammer when you want to tighten a screw but in order to build a skyscraper you need to start with something.
- foxFive 10y agoAs a budding programmer I like the ideas here, but I want to take it with a grain of salt and figure it's best to have a wide breadth of knowledge before going deep. Or rather, gain competence before striving for mastery.
- avindroth 10y agoThis article is way too long and without a proper table of contents. I don't know what's important or not, so at a first glance I could not gauge opportunity costs. And also lists are meant for small items, not paragraphs. Readability is respect for the reader.