The idea probably has some other practical problems though.
3,572 karma · joined August 15, 2007
http://almostobsolete.net/ (Geeky website stuff) http://tomparslow.co.uk/ (Freelancer portfolio stuff)
I'm a freelance programmer in Brighton in the UK. I work in lots of languages but I seem to use Python and JavaScript the most. I spend most of my time working from a Brighton co-working space called The Skiff (http://theskiff.org/) which is very nice.
I was on Twitter @almostobsolete but who uses Twitter anymore?
Find me on Mastodon at @almostobsolete@mastodon.me.uk or on Bluesky at https://bsky.app/profile/almostobsolete.net
The idea probably has some other practical problems though.
I'm buying it right now.
Freelance developer based in the Brighton in the UK. I can travel to London but I usually prefer to work remotely.
I love working on MVPs and prototypes. I'd love to help you turn your idea into reality.
I work in a range of languages but I usually choose Python when I have a choice. I also do a lot of work in JavaScript. I have a range of skills from web development to computer vision. I can help with Rich JavaScript Applications and RESTful API design (see a talk I gave on the subjects here[1]). I've been enjoying AngularJS recently, it makes some things very easy and is a nice contrast with Backbone.JS (which I also still use for other things).
A very non-exhaustive list of technologies I have built real things with (and enjoyed): Python, JavaScript, Django, Node.JS, Backbone.JS, AngularJS, OpenCV.
Some samples of my code:
- An open source JavaScript library I wrote: https://github.com/dharmafly/jsonpatch.js
- The Amazon Glacier support I contributed to Boto (popular Python library): https://github.com/almost/boto/tree/glacier/boto/glacier
Please do get in touch!
Web: http://almostobsolete.net/
Github: https://github.com/almost
Email: tom@almostobsolete.net
Phone: +44 (0) 7951261227
That's exactly it! This looks like a sensible design for an API served from rails and consumed by Ember.JS. It's just over selling it a bit to imply that this should be how all JSON APIs should be.
The proper layer for caching is HTTP, do we really want to end up with duplicated overlapping functionality between the layers? I see you have an application specific need for a certain thing but I don't think it generalises enough.
A few other things I noticed:
- There's no name spaceing of your special properties, they're just mixed up with the domain-specific properties. So I can't have a property of my object named "rel" and worse still you can't ever add features to the spec without breaking backwards compatibility.
- No type information in items, which kind of breaks automatic caching.
- Multiple entities returned for a URL with no indication as to which is the main one represented by that URL and which are just extra associated ones.
What's the reason for the top level rel? It seems like it's just there to stop the urls from being repeated and to save space, but isn't that what gzip is for? Why complicate the data format and require all that extra logic and gzip would remove most of the redundancy before transmission anyway?
Also the name is a bit of an annoying land grab. It'll make it hard to talk about JSON APIs without getting them confused with JSON APIs that specifically use "JSON API".
Lastly, it really seems based on a rails active record style data store, it's assuming ids are the most important thing and that links are all relations that point to other objects within the system. Proper hyperlinks and point anywhere and can link together disperate systems which don't necessarily all use the exact same formats.
Just add the env directory to your .gitignore
Next one is happening next Thursday and there are still a couple of tickets:
Maybe just me?
Plus the Jabber trademark is owned by a company, so you'll probably have to change it anyway.
Just tell people about the stammer, you'll find plenty who will understand and be accommodating.
Check out the monthly "Who's hiring" threads on here as well, the latest was posted yesterday:
https://news.ycombinator.com/item?id=5472746
Go contact some likely looking positions on there right now! Seriously, you're a programmer, programmers are really in demand right now. You can and will find something better.
Also, fuck your current employer, how dare they take advantage of that to pay you so little.
Good luck! Why not let us know how it went when you've had try...
Freelance developer based in the Brighton in the UK. I can travel to London but I usually prefer to work remotely.
I love helping to produce MVPs and prototypes. I'd love to help you turn your idea into reality. I work in a range of languages but I usually choose Python when I have a choice, I also do a lot of work in JavaScript. I have a range of skills from web development to computer vision. I can also help with Rich JavaScript Applications and RESTful API design (see a talk I gave on the subjects here[1]). I've also been doing some Natural Language Processing things recently with NLTK in Python, so if you have needs in that area do get in touch.
A very non-exhaustive list of technologies I have built real things with (and enjoyed): Python, JavaScript, Django, Node.JS, Backbone.JS, AngularJS, OpenCV.
Please do get in touch!
Web: http://almostobsolete.net/
Github: https://github.com/almost
Email: tom@almostobsolete.net
One thing to keep in mind is that Cake is tiny, the complete source shouldn't take more than a minute or 2 to read and understand[1] and is a nice example of CoffeeScript style.
In the authors example if he got it wrong and it replaced a load of non-links with links then running it again on the output of the first run isn't going to do any good. So he's suggesting replacing "git reset" with "git stash", both reset the repo to the way it was pre-sledgehammer but "git stash" also keeps around the previous results for comparison.