3 ms·
One of the best related comments I've seen on this topic was by coffeemug a few weeks ago: http://news.ycombinator.com/item?id=1747713 http://news.ycombinator.
by SkyMarshal 16y ago
One of the best related comments I've seen on this topic was by coffeemug a few weeks ago:
http://news.ycombinator.com/item?id=1747713 http://news.ycombinator.com/item?id=1747713
"1. Be good. Be very good. Don't be the "front-end guy" or the "back-end guy", or some other "guy". Once you know what you want to build, building software is about five things: algorithms that solve your problem, programming languages that express your algorithms, computer architecture that makes your algorithms run efficiently on real hardware, the practical toolchain, and the management of complexity of real software. So study algorithms, and then graduate algorithms, and then advanced graduate algorithms. Do every challenge problem online. Study programming languages to express those algorithms. You can get away with three: C, Lisp, Haskell. Everything else is crud.
..."
I interpreted that to mean that C, Lisp, and Haskell are best at expressing the most difficult algorithms and concepts in computer science and software engineering, while simultaneously giving one the conceptual understanding and ability to quickly use easier languages like Python or Ruby for glue, utility, etc.
- silentbicycle 16y agoI'd suggest ML rather than (or as a complement to) Haskell. The pervasive laziness in Haskell makes it rather unique - sometimes in a good way, but it means that algorithms often don't translate well to non-lazy languages. ML is just as good for algorithms & complex data structures (H-M+ inferred static typing, pattern matching, etc.), and has optional laziness (in OCaml, and IIRC as an extension to some SML implementations), but is usually easier to translate to more conventional languages as necessary.
- SkyMarshal 16y agoThanks, that's good to hear. I'm working through the Little MLer right now. Good intro, but I'd be interested recommendations for other good books on ML.
- silentbicycle 16y ago_The Little MLer_, first and foremost - it seems to be the best intro to the ML-style type system. My ML experience has mostly been OCaml-flavored. The best OCaml book I've seen is _Developing Applications with Objective Caml_ (In French, but a free English translation is online at http://caml.inria.fr/pub/docs/oreilly-book/html/index.html http://caml.inria.fr/pub/docs/oreilly-book/html/index.html). It covers a slightly older version of the language, but that mostly impacts libraries. Andrew Appel's _Modern Compiler Implementation in ML_ and _Compiling with Continuations_ are both great compiler books, which happen to use SML for the code. Joshua Smith's _Practical OCaml_ is bad. Really bad. I was shocked. Avoid. Chris Okasaki's _Purely Functional Data Structures_ is a great data structure / algorithm book, and uses SML (but has an appendix with Haskell versions). Also quite good. Finally, experience with Lisp, Prolog, and Haskell carry over to ML somewhat, if you've used those.
- SkyMarshal 16y agoGreat list, thank you. I've been eying Purely Functional Data Structures on Amazon, good to have a HN testimonial on that one. Will add that to my shopping cart for the next batch I buy. I've also been looking at Modern Compiler Implementation in ML, but have no experience in compilers (no courses, work, anything). Should I read Aho first, or is that one I could dive right into?
- silentbicycle 16y ago> Should I read Aho first, or is that one I could dive right into? I haven't read the newer edition of the dragon book, but MCIiML is a much better starting place than the old dragon. Relevant recent comments: http://news.ycombinator.com/item?id=1820858 http://news.ycombinator.com/item?id=1820858 (on parsing + how I feel about the dragon book) http://news.ycombinator.com/item?id=1822515 http://news.ycombinator.com/item?id=1822515 (more book, etc. suggestios)
- SkyMarshal 16y agoGreat, thank you!