1,568 karma · joined March 29, 2010
"One of the three required pieces for each JSR is the Technology Compatibility Kit (TCK). A TCK is a suite of tests, tools and documentation that determines whether or not a product complies with a particular Java™ technology specification. A TCK must be included in a final Java technology release under the direction of its Expert Group."
Quoted from http://jcp.org/en/resources/tdk
Edit: A quick search turn up this interesting LtU discussion: http://lambda-the-ultimate.org/node/1544
I found this quite thought-provoking about different error handling techniques, so thought it worth submitting.
[1] http://blueprintforge.com/blog/2012/02/27/static-modificatio...
[2] http://blip.tv/pycon-us-videos-2009-2010-2011/pycon-2011-wha...
[3] http://docs.python.org/library/ast.html#abstract-grammar
Seems likely that an issue entry will provide better context to the problem than a simple TODO would. Issues may also be tagged with a rough indication of how much work they will require to tackle. Choosing issues that are a small amount of work seem to be a good way to get familiar with a codebase.
Anyway, good luck with statuscode!
http://www.hackernewsletter.com/
...so I decided to create one to gather together the best, most detailed programming articles I could find, regardless of language or platform. I don't see how this could be called "cloning", though the format of a weekly newsletter is obviously nothing new.
For instance, my recent post on optimising Django's SQL query generation was a collection of useful tools and approaches.
Seen in this light, a couple of the benefits are: the sharing of useful knowledge, and exploring things I encounter in daily development in more detail. As well as building things, it's nice to be able to work on my written communication.
http://duriansoftware.com/joe/An-intro-to-modern-OpenGL.-Tab...
Has anyone A/B tested this?
If there's a feature you'd like to see in a future release, you can suggest it here: https://groups.google.com/forum/?hl=en#!forum/scala-ide-dev
As somebody who is a few years out of university, being able to access the courses that MIT, Stanford, Berkeley and others produce is really fantastic.
I can't help but feel there are many opportunities for startups in this space as platform and service providers.
It's great to hear this is an active area of development, as it's probably the biggest remaining factor in me choosing host OS.
There are some good examples here: http://wiki.freebase.com/wiki/MQL_Cookbook
https://docs.djangoproject.com/en/dev/ref/request-response/#...
Agreed - 'depth' makes more sense as a GET parameter, since it's a resource in its own right.
The standard approach to expressing errors in a REST API
is to use HTTP status codes. As is often the case with
REST, this works fine for simple systems, but is simply
too limiting for more sophisticated systems, particularly
those which might submit a JSON or XML document to
describe a POST request.
That's what the response body is for. If a client PUTs (or POSTs) a malformed representation, it's reasonable for the response to be 400 with error detail in the body.The "depth" parameter is kind of interesting, since it gives the client a choice as to whether multiple resources are included in the response. I'd be interested to see how others implement this (or if the client is given no choice at all).
But essentially this is a straightforward choice between latency and response size.
http://groups.google.com/group/crunchbase-api/web/api-v1-doc...
Edit: to be clear, my definition of blogspam is "adds no value to the original content".