Course in Machine Learning

Another one.

Angular tutorial

Tutorial here.

Tutorial site for Foundation

Foundation is yet another HTML5/CSS framework. Here is a tutorial site with clever gamification and pretty design.

Regex crossword and constraint programming

So there's this neat little Regex learning site at Regex Crossword - it's fun. I worked straight through it and enjoyed the whole thing.  (HNN quote that made me laugh: "I tried to solve these with regular expressions. Now I have two crosswords.").

This led to the realization that constraint programming is actually a fun type of puzzle - and that automating it is something that was once considered AI, but is now no-true-Scotsmanned out of the domain. One example of a solution to this kind of problem using Haskell's Regex.Genex package is here. Cool stuff!

Lisp koans tutorial

Test-driven tutorial for Lisp.

Tutorial on AngularJS with Backlift persistence

Nice little tutorial. Backlift offers an API for data persistence (a straightforward service that makes sense to me!) and have provided a little tutorial on building a webapp in Angular that uses it.

Django HNN clone tutorial

Here's a cool thing - an "advanced Django tutorial" implementing an HNN-like site in Django.

Webapp design stuff

Ember is a JS Webapp framework.  Here is the tutorial list.

Then there are Pure CSS and Topcoat that have shown up on HNN this week.

ML tutorials

A couple of  useful Stanford tutorials in machine learning: Andrew Ng's open courseware ML class, and a second tutorial building on that for the new stuff in deep learning.

Lucy - C-language Lucene for embedding in dynamic languages

A tutorial.  Apache has also spun out its NLP tools into a separate project OpenNLP. And Lucene can query based on Levenshtein distance, which is pretty cool.

Git is really a lot more opaque than it needs to be

Here's a fantastic tutorial about Git branching that has finally made a lot of things make sense to me.  But seriously, the management commands provided, while they make perfect sense in terms of the actual things git is doing, make no sense whatsoever in terms of the semantics of managing branches and versions.

I conclude that git's actual UI is horrible.  Moreover, there's no real reason for there to be multiple DVCSs anyway, since they all essentially do the same thing - implement the same abstract architecture.  Again, the specifics of the UI obscure the actual things being done and why they're done.

A version history as represented in git (or any other DVCS) should be a part of the documentation in graphical form, like any other part of the documentation.  That report should then be available as a contextual orientation for performing actions on the official history of the project.  Specific branches and commits should be tracked explicitly and graphically - obviously while preserving the underlying command structure for those that think that way, but seriously.  Git is crazy.

Dojo tutorial

Dojo for jQuery developers.