After thesis and graduation, I took a break from to focus on getting a job.  I ended up getting hired at the wonderful The Barbarian Group as a developer (!!), about which I’m extremely happy, for that career change was exactly what I left DC and came to NYC to accomplish.

In the time since, I’ve been lurking in the nether regions of HTML5 canvas, HTTP headers, XSRF protections, and Drupal.  And now that I’m a little more comfortable with all the life changes around me, I have started coding for fun again.

I gravitate towards the MEAN stack for most any new fun project now: node.js/express.js being extremely easy to set up and expand, plus mongo which makes it super easy to drop in and manipulate with mongoose as an ORM, and then learning the intricacies of angular.js, which has made front-end state super easy.

And these projects I like to work on tend to relate to quant self and meta data about the self, which means they’re natural fits as an app on  So with that in mind, I fleshed out a new interface for collecting moments at


There are many categories of data on, like exercise, school, and work, but there are also more nebulous forms like moments.  What discrete events did you attend today?  What special interactions did you have with random strangers, or with your loved ones?  What was the quality of those experiences?  That’s all Momentous does — it’s an excuse for me to build a quick angular.js app that collects the random moments of my day.


You can give it a shot at (you’ll have to login/register) or just use the main moments page at if you like.

These sorts of mini-apps allow me to work on, experiment with new frameworks, and build nicer front-ends than the messy base template I’m currently using.  It’s still a work in progress.

The Future

I’m loving angular.js for building nice interactive apps that react quickly to the user and to the backend.  I’m thinking it’s a huge leap forward for writing HTML and JavaScript that expresses its meaning and functionality within the HTML source (by way of directives and filters) instead of having events bound to HTML states but stored in separate JS files.

From there, I’m thinking there’ll soon be code editors for JavaScript that build server-side API routes to receive and respond to the requests written by the user in client-facing scripts.  So you’d write some angular.js or jquery front-end stuff to hit an API route, and the IDE would automatically build the route to receive it and pull it from the database.  There’s still some disconnection between development for the client and for the server, but I think that’s what the next major leap forward will be for writing apps for the web.