A session of Martin Odersky's Functional Programming in Scala is just wrapping up. I'd reccommend it as a good way to bring a more functional style to the JVM. The Edx course, being in Haskell probably is a better choice for a different audience.
This Clojure course is a clear third alternative because of Clojure's pseudo.dynamic typing versus the Scala and Haskell's strong static typing.
It resembles programming koans — you fork a repository and run tests to see if you succeeded:
>At the start of every chapter, you should go to Github and fork the chapters repository. There will be a link to the appropriate repository at the beginning of every chapter. You then clone your own fork of the repository and start working with the exercises when you encounter them among the material. You create commits and maybe push them in to your own fork while working. You also run the tests with lein midje to see if they pass.
Note that they mean the "chapter's" repository, not a "chapters repository" that contains everything.
Grading is done separately: a continuous integration tool runs your assignment and replies with your grade.
>When you want your answers graded, you push all of your work with git push. You then go to Github and send a pull request. At this point, Travis kicks in. It runs the tests for your code and then comments on the pull request whether the tests passed or failed. A link is also provided to see the nitty-gritty details.
That's actually a rather common error for Finns. G and Q are almost exclusively used in loanwords and foreign proper names. What's more, some Finns pronounce the name for the letter Q as "guu". I've never figured out why.
[+] [-] reedlaw|11 years ago|reply
[+] [-] brudgers|11 years ago|reply
This Clojure course is a clear third alternative because of Clojure's pseudo.dynamic typing versus the Scala and Haskell's strong static typing.
[+] [-] macco|11 years ago|reply
[+] [-] freeduck|11 years ago|reply
[+] [-] estebanrules|11 years ago|reply
[+] [-] alecdbrooks|11 years ago|reply
>At the start of every chapter, you should go to Github and fork the chapters repository. There will be a link to the appropriate repository at the beginning of every chapter. You then clone your own fork of the repository and start working with the exercises when you encounter them among the material. You create commits and maybe push them in to your own fork while working. You also run the tests with lein midje to see if they pass.
Note that they mean the "chapter's" repository, not a "chapters repository" that contains everything.
Grading is done separately: a continuous integration tool runs your assignment and replies with your grade.
>When you want your answers graded, you push all of your work with git push. You then go to Github and send a pull request. At this point, Travis kicks in. It runs the tests for your code and then comments on the pull request whether the tests passed or failed. A link is also provided to see the nitty-gritty details.
Source: https://iloveponies.github.io/120-hour-epic-sax-marathon/bas....
[+] [-] sharms|11 years ago|reply
[+] [-] cnp|11 years ago|reply
[+] [-] cnp|11 years ago|reply
[+] [-] kremlin|11 years ago|reply
[+] [-] tricolon|11 years ago|reply
[+] [-] melipone|11 years ago|reply
[+] [-] fingerzam|11 years ago|reply