News for hackers. Stuff that matters.
Re:Organizational Skills Beat Algorithmic Wizardry by kyllo on Thursday June 20, 2013 @11:01AM (#5912467)
This Yegge article from 2007 is relevant:

http://steve-yegge.blogspot.com/2007/06/rich-programmer-food...

"If you don't know how compilers work, then you don't know how computers work."

Becoming better at the first class of programming that you describe, will also make you better at the second class.

And a lot of times, "modeling the world" is a pitfall of object-oriented programming, and something that you don't really want to do. But it's very tempting if you've only ever programmed in Java.

Re:Organizational Skills Beat Algorithmic Wizardry by acgourley on Thursday June 20, 2013 @12:40PM (#5913056)
Knowing how compilers work is very useful foundational knowledge, but that's different than knowing, off the top of your head, the underpinning algorithms needed to implement a compiler!
Re:Organizational Skills Beat Algorithmic Wizardry by kragen on Friday June 21, 2013 @01:49AM (#5916764)
Really? They sound exactly the same to me. What, in your mind, does "knowing how compilers work" consist of, other than "the underpinning algorithms needed to implement a compiler"?
Re:Organizational Skills Beat Algorithmic Wizardry by acgourley on Friday June 21, 2013 @11:02PM (#5922396)
The exhaustive list is longer than I have patience for, here's one example: understanding how the parse and lex steps work, and what is accomplished is useful without knowing how to pseudocode a recursive decent parser. It's worthwhile to write said parsing algorithm once in your life, it's not necessary to keep that knowledge warm in your head throughout your career.
Re:Organizational Skills Beat Algorithmic Wizardry by kragen on Saturday June 22, 2013 @08:50PM (#5925801)
Hmm, I guess I don't know what "understanding how the parse and lex steps work" would consist of that didn't involve being able to pseudocode at least some kind of parser, of which the recursive-descent type is the simplest. But maybe I'm blinded by having spent too much time writing parsers. Or maybe you mean "knowing how" in some kind of total back-of-the-hand mastery sense, as opposed to "you could eventually get it to work"?