being good at software design isn't about memorizing the specific details of a single language or subjects
languages are subject to change
hire people who are good at finding information
not someone who is good at blindly memorizing details of a specific instance of a language or system
someone who memorized every single detail of COBOL will be a worse coder than someone who spent time thinking about abstract thinking and problem solving
you'll want to double check everything anyway
this shows of a fundamental lack of insight into what it means to be a good developer
it's like someone who thinks they are smarter than everyone else because they spent thousands on hours on playing chess
this student who has memorized the full specification of HTML, CSS and Javascript will be useless if you ask them a question about lets say Erlang, and is easily replaced by a book
Comments
being good at software design isn't about memorizing the specific details of a single language or subjects
languages are subject to change
hire people who are good at finding information
not someone who is good at blindly memorizing details of a specific instance of a language or system
someone who memorized every single detail of COBOL will be a worse coder than someone who spent time thinking about abstract thinking and problem solving
you'll want to double check everything anyway
this shows of a fundamental lack of insight into what it means to be a good developer
it's like someone who thinks they are smarter than everyone else because they spent thousands on hours on playing chess
this student who has memorized the full specification of HTML, CSS and Javascript will be useless if you ask them a question about lets say Erlang, and is easily replaced by a book