440 karma · joined November 1, 2012
Do capital markets have a natural or a constructed social utility?
If their social utility is natural, then finding out what benefit they might have to society is a sort of empirical question. But if their utility is a purely political construction, then their perceived benefit can be moulded to fit a desired outcome.
Seeking short term contracts to supplement existing employment.
I am a human/machine interface designer && developer. My work consists of "from scratch" UX and interface design, from the napkin to nginx. I have considerable experience with Ruby and Javascript, years of experience with Rails, and extensive knowledge of client-side MVC.
I've made contributions to Ember.js, and have written multiple 10k+ LOC apps - starting with 0.9 up to the latest 1.0 (one was recently featured on Venture Beat: http://venturebeat.com/2013/07/22/uniiverse-releases-direct-...). I am acutely aware of the challenges/strategies associated with migrating server side architecture into the browser, leaning down views, and fattening up controllers.
I am the author of an open source project called Quant (https://github.com/jdjkelly/quant) - a Rails API + Angular.js app to track "quantified self" data from every manufacturer willing to give it up. My work here was featured on The Verge alongside a similar project by the founder of Foursquare (http://www.theverge.com/2013/6/4/4392996/fitness-tracker-dat...)
Recently, I also contributed to the development of an iOS app, which is now in the app store: https://itunes.apple.com/ca/app/ticket-manager-by-uniiverse/.... I was responsible for integrating a credit card device reader with an existing checkout API, testing, and delivering a final build to the app store.
Skills: Ruby, Rails, Mongo, Postgres, Sinatra, Node.js, Objective-C, Javascript, Coffeescript, Sass, Ember.js, Backbone.js, Angular.js, jQuery, HTML5, CSS3
Other tools in the box: Git, Zsh, pencils, pens, paper, Photoshop
Contact is in my profile.
I have been working on an open source API to accomplish similar things (specifically just re: aggregation of data from disparate sources): https://github.com/jdjkelly/quantify
It's Rails + Postgres, and so far aggregates meal, weight, and sleep data from Withings and Fitbit - but I've been focussed on building out a framework to easily aggregate many, many more sources.
Maybe we could find a project to work on together - contact is in my profile.
The original headline is preserved, and clarified by the editorial clarification in square brackets. It would be great for HN to adopt this as a solution to the modified headline problem, with the provisio that editorial comment must only be used for the purposes of clarification.
I am a human/machine interface designer && developer. My work consists of "from scratch" UX and interface design, from the napkin to nginx.
I have considerable experience with Ruby and Javascript, years of experience with Rails, and extensive knowledge of client-side MVC. I've made contributions to Ember.js, and have written multiple 10k+ LOC apps - starting with 0.9 up to the latest 1.0 (one was recently featured on Venture Beat: http://venturebeat.com/2013/07/22/uniiverse-releases-direct-...). I am acutely aware of the challenges/strategies associated with migrating server side architecture into the browser, leaning down views, and fattening up controllers.
I am the author of an open source project called Quantify (https://github.com/jdjkelly/quantify) - a Rails API to track "quantified self" data from every manufacturer willing to give it up. My work here was featured on The Verge alongside a similar project by the founder of Foursquare (http://www.theverge.com/2013/6/4/4392996/fitness-tracker-dat...)
Backend: Ruby, Rails, Mongo, Postgres, Sinatra, Node.js
Frontend: Javascript, Coffeescript, Sass, Ember.js, Backbone.js, Angular.js, jQuery, HTML5, CSS3
Other tools in the box: Git, Zsh
Design: Pencils, pens, paper, Photoshop
Contact is in my profile.
The most important thing I've accomplished, other than building the compiler, is
training young people. They come to me, you know, and say, "Do you think we can do
this?" I say, "Try it." And I back 'em up. They need that. I keep track of them as
they get older and I stir 'em up at intervals so they don't forget to take chances."We need a Rapgenius for online discount codes. Right now, it's full of scummy, crappy sites (just like lyric sites), but could be easily improved with a simple interface, minimal advertising, and collaboratively sourced content.
I am a human/machine interface designer && developer. My work consists of "from scratch" UX and interface design, from the napkin to nginx.
I have considerable experience with Ruby and Javascript, years of experience with Rails, and extensive knowledge of client-side MVC. I've made contributions to Ember.js, and have written multiple 10k+ LOC apps - starting with 0.9 up to the latest 1.0 RC 6.1 (one was recently featured on Venture Beat: http://venturebeat.com/2013/07/22/uniiverse-releases-direct-...). I am acutely aware of the challenges/strategies associated with migrating server side architecture into the browser, leaning down views, and fattening up controllers.
I am the author of an open source project called Quantify (https://github.com/jdjkelly/quantify) - a Rails API to track "quantified self" data from every manufacturer willing to give it up. My work here was featured on The Verge alongside a similar project by the founder of Foursquare (http://www.theverge.com/2013/6/4/4392996/fitness-tracker-dat...)
Backend: Ruby, Rails, Mongo, Postgres, Sinatra, Node.js
Frontend: Javascript, Coffeescript, Sass, Ember.js, Backbone.js, Angular.js, jQuery, HTML5, CSS3
Other tools in the box: Git, Zsh
Design: Pencils, pens, paper, Photoshop
Contact is in my profile.
I'm nearly positive the answer is just "to learn Ember" - in which case, great!
To everyone else: don't start using a JS MVC framework for your real projects without seriously justifying their use in the first place. They should absolutely not be considered part of a default app stack. You will go through so much pain in doing so, and that pain needs to explain itself, in the concrete terms of the project requirements.
Events need not be the same for us to try to use them to understand and vocalize our experiences.
Great writeup! Some days I feel similarly about Ember.
Human/machine interface designer/developer. From scratch experience and interface design, from the napkin to nginx.
Frontend: HTML5 (Haml, Slim), CSS3 (Sass, Less), JavaScript (Vanilla, jQuery, Ember.js, Backbone.js, Handlebars). I've made contributions to Ember.js, and have written multiple 10k+ LOC apps - starting with 0.9 up to the lastest RC6. I have extensive knowledge of the challenges/strategies associated with moving an existing app to be client-side MVC.
Backend: Ruby, Rails, Mongo, Postgres
Design: Pencils, pens, paper, Photoshop
SPECIAL OFFER: I'm offering a free hour long Skype call to anyone who needs high level advice about any of the above. Contact is in my profile.