I'm a seasoned backend-centric developer - tools of choice these days are Scala, Java and Python, mainly in a *nix environment. Looking to work on interesting/novel problems with high quality and practice standards. Big on testing, and (pragmatic) functional programming.
Remote only for now
Location: Halifax, Nova Scotia, Canada
Remote: Only
Willing to relocate: Not currently
Technologies: Scala, Python, Java, JS, C, Akka, OSGi (probably not again), AWS, Mongo, Redis, SQL, Qt. Have also done a bunch of frontend stuff, though I'm no designer.
Resume: http://linkedin.com/in/agiledave
Email: david DOT leblanc AT gmail DOT com
Not sure what Wu-Tang has to do with this, but....
Seriously though, is Mongo an ODB, or a document oriented database? ODBs/OODBs imply a much different use-case and functionality, and I think we ought not conflate the two.
Mongo is not an ODB in the traditional ODB sense. Mongo is just a document (or blob) database. ODB supports relationship, link traversal, inheritance, etc. Basically the whole shebang of the OO notions in a database.
Along the same lines as Noam Chomsky's "Manufacturing Consent". The book is great, and there's a documentary from 92: https://www.youtube.com/watch?v=dzufDdQ6uKg