1–10 of 41 posts
Stuff that usually sits in abtruse papers, out of mind for the average developer. Accessible to the average developer, and in a form more easily digestible (studying research papers is not practical for all).
When I picked up the Cormen book recently, I saw lots of new stuff I didnt learn in College.
The best thing to do is to first get more specific: what kind of algorithm? Is it database implementations? Virtualization techniques? Filesystem optimization? Graphics hardware? Programming languages?
Then, find the appropriate journals. Get an ACM membership so you can search and get full text of the library.
As for latest advances, there are many languages on the cutting edge, such as Haskell, OCaml and Erlang that would be worthy to study just to expand your horizons. These languages ARE many of the latest advances in CS. I'm currently diving into Lisp, and have found that some concepts are timeless (code as data, macros).
Computer Science, as a field is very mature, and as a result, very specialized in its research (though I disagree with the idea that core algorithm research is more relevant for the average developer than what you call fads). The best thing to do is to first get more specific: what kind of algorithm? Is it database implementations? Virtualization techniques? Filesystem optimization? Graphics hardware? Programming lan…
for developers with full time jobs?
But if you really want to learn more about algorithms, check out this book:
http://www.amazon.com/Algorithm-Design-Jon-Kleinberg/dp/0321...
As for programming languages, the java + eclipse combination is excellent.
For routine programming, the GoF Design Patterns book will be more helpful to you than algorithms books. But if you really want to learn more about algorithms, check out this book: http://www.amazon.com/Algorithm-Design-Jon-Kleinberg/dp/0321... As for programming languages, the java + eclipse combination is excellent.
http://www.amazon.com/Refactoring-Improving-Design-Existing-...
Computer Science, as a field is very mature, and as a result, very specialized in its research (though I disagree with the idea that core algorithm research is more relevant for the average developer than what you call fads). The best thing to do is to first get more specific: what kind of algorithm? Is it database implementations? Virtualization techniques? Filesystem optimization? Graphics hardware? Programming lan…
"find the appropriate journals. Get an ACM membership so you can search and get full text of the library" for developers with full time jobs?
Really, it's a matter of making time for reading and learning. Pick up a paper sometime at night when you don't feel like coding and would otherwise watch TV. Or print it out and read it on the subway or carpool.
You also mentioned Cormen being too hard for the "average developer" and covering stuff you didn't learn in college. Cormen is intended as a textbook for later undergrads or early grad student courses. If you didn't learn the material in college, Cormen is your chance to learn it. And you have to treat it just like you're in college again - really, you can't expect to just magically know things. The whole point is to learn from it - if it covered stuff you already knew, there'd be no reason to read it.
Earlier quoted context omitted.
"find the appropriate journals. Get an ACM membership so you can search and get full text of the library" for developers with full time jobs?
How else are you gonna pay for the ACM membership? ;-) Really, it's a matter of making time for reading and learning. Pick up a paper sometime at night when you don't feel like coding and would otherwise watch TV. Or print it out and read it on the subway or carpool. You also mentioned Cormen being too hard for the "average developer" and covering stuff you didn't learn in college. Cormen is intended as a textbook fo…
Earlier quoted context omitted.
"find the appropriate journals. Get an ACM membership so you can search and get full text of the library" for developers with full time jobs?
How else are you gonna pay for the ACM membership? ;-) Really, it's a matter of making time for reading and learning. Pick up a paper sometime at night when you don't feel like coding and would otherwise watch TV. Or print it out and read it on the subway or carpool. You also mentioned Cormen being too hard for the "average developer" and covering stuff you didn't learn in college. Cormen is intended as a textbook fo…