News for hackers. Stuff that matters.
Re:Technical Papers Every Programmer Should Read (At Least T... by 0x12 on Saturday September 10, 2011 @05:20AM (#2981231)
Most programmers I know never read papers, they read plenty of code but the code usually sucks. The reason why it sucks is because it was written by programmers that never read papers and so the cycle continues.

If you don't start somewhere then you'll miss out on papers being an excellent source of knowledge about algorithms, datastructures and the like. They also introduce you to a more mathematical approach to problem solving.

More papers, less code, and if you read code for its educational value make sure it is excellent code.

Then go back to your daily drudge of fixing bugs in crappy code, hopefully transforming it into something more elegant along the way with the knowledge you pick up.

Read papers, read good code to educate yourself.

Re:Technical Papers Every Programmer Should Read (At Least T... by swah on Saturday September 10, 2011 @10:17AM (#2981609)
What about books ? Aren't they condensations of papers? :)
Re:Technical Papers Every Programmer Should Read (At Least T... by 0x12 on Saturday September 10, 2011 @12:04PM (#2981777)
What about readers digest? Aren't they condensations of books? :)
Re:Technical Papers Every Programmer Should Read (At Least T... by Luyt on Saturday September 10, 2011 @12:54PM (#2981893)
What about blogs. Aren't they condensations of both?