That 80-20 rule turns up everywhere. I find it most interesting that in many languages you can do 80% of the job with 20% of the features - and it strikes me that we thus have to think real hard about which features we want to fit within those initial 20%. If it takes a CS graduate 10 years to be proficient, you've got to wonder whether we can't do better here - it needs to be harder writing "bad code". Java is probably among the most complex languages to truly master* due to a long lifespan, religious approach to backwards compatibility and shoehorning of features.
/Casper *Even a Sun distinguished engineer can get in trouble: http://www.javaspecialists.eu/archive/Issue185.html On Jul 12, 1:42 pm, Wildam Martin <[email protected]> wrote: > Within my newsfeeds today I found an article that in point 2. talks > about the 10 000 hour rule (I heard this before but did not think > further about it):http://thinksimplenow.com/happiness/how-to-have-good-luck/ > > This means that with an approx of 150 working hours per year it takes > more than 8 years to master a topic (or in our case - programming > language for example). If you consider that you are using the same > programming language for about 10 years, we have a 80-20 rule of 80 % > bad code and 20 % good code. ;-) > > -- > Martin Wildam -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
