Re:Organizational Skills Beat Algorithmic Wizardry
by kaoD on Thursday June 20, 2013 @08:46AM
(#5911692)
That you're "quite a good programmer" might be a myth too :P
[ Parent
| on HN ]
Re:Organizational Skills Beat Algorithmic Wizardry
by RivieraKid on Thursday June 20, 2013 @08:54AM
(#5911726)
I don't think so, because I've developed some quite popular software and done well in programming contests.
Re:Organizational Skills Beat Algorithmic Wizardry
by kaoD on Thursday June 20, 2013 @09:04AM
(#5911785)
Programming contests show nothing about your organizational skills, which is what companies should be looking for.
See https://news.ycombinator.com/item?id=5911235
Mathematicians perform very well on programming contests, but they are usually terrible software engineers.
Anyways, I was just kidding :)
Re:Organizational Skills Beat Algorithmic Wizardry
by RivieraKid on Thursday June 20, 2013 @10:49AM
(#5912381)
I think that mathematicians don't do well in software development because they simply have much less experience than other devs :) I think that what's most important in software engneering is experience, motivation, intelligence, common sense and good taste (aesthetics).
Re:Organizational Skills Beat Algorithmic Wizardry
by victorhn on Thursday June 20, 2013 @09:17AM
(#5911837)
Google is full of engineers that did well on programming contests, they even have their own contest, and i don't think they are all terrible software engineers.
Re:Organizational Skills Beat Algorithmic Wizardry
by victorhn on Thursday June 20, 2013 @09:26AM
(#5911895)
I don't think the problems in algorithmics contests are in the category of brainteasers. As far as i know Google still relies heavily on knowledge of algorithms and problem solving capability to hire their engineers.
Re:Organizational Skills Beat Algorithmic Wizardry
by kaoD on Thursday June 20, 2013 @10:29AM
(#5912252)
Fair point. I still think there are two types of programmers: problem solvers and system architects.
The former (e.g. a data scientist) will be good solving a problem but bad building a big architecture. The latter, the other way around.
I guess the question is which kind of programmer you are and which skills to look for.