3 ms·
This essay seems to beg the question. A "good" developer, by its definition, is the who picks the most reasonable, easy to maintain technology, because she know
by danso 15y ago
This essay seems to beg the question. A "good" developer, by its definition, is the who picks the most reasonable, easy to maintain technology, because she knows anything "much more complex would be beyond her current skill." Yet, if she is lacking in skill, how can we be sure her judgment is sound on what a "reasonable" and "easy" technology is? Doesn't the basis for that judgment require superstar-like experience and curiosity?
- deleted 15y ago[deleted]
- ryanto 15y agoDevelopers who lack skill are awful at picking technologies. I like to think of it like this: when the guys that don't know anything start picking the tools they are basically throwing darts at a board. Everything is going to seem random. Sure, some of their picks will be correct, but most are going to be awful selections that make maintaining the project a very unpleasant experience.
- arctangent 15y agoThese kinds of people tend to choose whatever seems popular right now. If they happen to be managers then they will read Gartner reports and report on their contents as if Moses himself had presented them with edicts carved into stone tablets.
- grannyg00se 15y agoI would say that once you reach a certain level you are able to determine which technology is reasonable based on things like language familiarity, community support, and documentation.
- danso 15y agoSure, but I wonder if two years in Ruby, or any language, is enough? A superstar dev might go out and try a lot of the new, cool stuff, even when it is needed. But it seems that that developer would also have a grasp of the common characteristics of bad technology. So I think there are at a minimum two good traits of a great developer. The rockstar-like quality of having the skill, curiosity, and breadth of knowledge to handle being on the edge. And the maturity and thoughtfulness to know whey he/she has failed in the past.
- tjsnyder 15y agoTwo years? I think you can learn everything you ever needed to know about a language in a much shorter time period than that.
- ysilver 15y agoTotally agree. For example, if a web dev wants to try a new language/framework, he or she can be competent in a few weeks and well-versed in 3-6 months. No?
- deleted 15y ago[deleted]
- dkersten 15y agoIf you are already an expert programmer who knows a few similar languages, then sure. If you are already an expert programmer who knows different languages, then two years may be enough, or it may not. If you are not already an expert programmer, then two years is unlikely to be enough. Peter Norvig suggests it may take ten years to become an expert: http://norvig.com/21-days.html http://norvig.com/21-days.html Example: I have been programming for a little over ten years (though not all of that time was professional programming); have a degree in software engineering; have worked in telecoms, web development and recently in embedded systems; have used C, C++, Java and Python professionally; I am a self-described language enthusiast who likes to tinker with, try out and apply a variety of languages (factor, scheme, clojure, prolog, ocaml, haskell and a few more to a lesser extent). BUT I still learn new things about the languages I use. I still feel I have a lot more to learn. I first started using Python in 2001 or 2002 and I still find myself learning useful new things. So, sure, you can learn enough to effectively use a language in a lot less than two years, but I think it will take a lot lot longer to learn "everything you ever needed to know about a language".
- angelbob 15y agoRuby is also a bit of a contrived example. Ruby looks a lot like you could come to it from Java and know most of it, but metaprogramming actually takes a long time and a lot of work to really figure out. Similarly, Ruby has many different little variants -- Rails, Rake, various sorts of DSLs -- and that adds significantly to the time to learn it. Really learning Ruby is learning several similar languages, which makes two years a much harder number to achieve. C++ could easily have been like that if it had different constellations of features that were routinely used in different ways by the same programmers. Imagine if there were a whole "C++ tools" subculture that used templates extensively but differently, along with one or two other nontrivial features (say, multiple inheritance and exceptions) used in specific ways with specific non-compiler-mandated rules. You'd have to learn, in effect, about another programming language's worth of material to program fluently within that subculture. Ruby has several of those.
- einhverfr 15y agoAgreed and of course a clear understanding of what the tradeoffs of approaches are. In the end, I think that more than years of experience is the best marker. I have come into codebases written by a few developers for 20 years that made me think "why don't these people ever get any better?" And when the codebase could function as a textbook of how not to program........