Hacker News Reader

fwiw, I created a company with 100 shares of which I took only 1 at time of creation.

Apparently this makes things easier if/when you come to distribute shares to others as it will be a simple allocation of unallocated shares rather than a more convoluted 'transfer' process.

mikek85on Robot wars break out on poker sites

Ok, calm down.

I should've clarified no limit. This article is presumably talking about no limit - since that is by far the predominant game.

With all due respect, you have a poor understanding of poker if you really think there is a way to "memorize the correct action for every scenario". Poker is about interaction, spotaneity, 'feel', instinct. Mastering those things is where to get a real edge, not math - particularly in no limit. Hence my comment.

mikek85on Robot wars break out on poker sites

If you can't beat a bot then poker is not the right game for you.

mikek85on The one true REST explanation

http://gowalla.com/api/explorer

isn't bad

edit: Btw, any well designed website is at level 3.

mikek85on Ask HN: Good books?

The Wisdom Of Insecurity by Alan Watts

^ it's tiny, easily the best book I've ever read.

mikek85on Get Your API Right

these are important

1. use hyperlinks and link relations i.e. <link href="/people/bob" rel="friend" />

2. don't bother with multiple media types (unless /absolutely/ necessary) . If appropriate try to use/extend an established type such as Atom/AtomPub

3. make sure you set your cache control headers appropriately

mikek85on He Took a Polaroid Every Day, Until the Day He Died

DOLLY! WILL YOU GET A POLAROID OF THAT?

mikek85on Ask HN: Music while coding

any porno backing will work

.. plaaaayaaaaa

mikek85on Ask HN: Why do RSS Readers (mostly) suck?

get better at being ignorant

mikek85on Rethinking Rails 3 Controllers and Routes - PeepCode Blog

That 1:1 mapping is a good thing, but I don't think that's a reason to completely do-away with routing altogether. Sticking the route in the controller just makes the code harder to follow.

mikek85on Rethinking Rails 3 Controllers and Routes - PeepCode Blog

The main argument is flexibility and acknowledging what the role of the controller actually is in a resource-oriented application

Idea 2 is the way to go because it's resource oriented and you get useful stuff like 405's for free which you don't with the sinatra approach.

Please don't remove routing. Having routes is important - it makes the code more descriptive and easier to follow. All a route needs to do is map one URI pattern to one controller, i.e:

/blog -> BlogController

/blog/:post -> BlogPostController

/blog/:post/comments -> BlogPostCommentsController

I wrote a hack for Zend Framework last year to prove how this would work:

http://restafari.blogspot.com/2010/04/restful-php-applicatio...

mikek85on REST isn't what you think it is, and that's OK

Yes people have tended to miss out the hypermedia constraint and claim to be REST - partly because everyone's been too excited about using HTTP properly to think about anything else, but also just because there's been a lack of tooling and guidelines for designing media types properly. Most people in the REST community agree on that point and now there are useful approaches and technology emerging - restfulie is a great example of this.

mikek85on REST isn't what you think it is, and that's OK

Actually, I think the REST community is pretty clear on this now - there's no need need to accept incorrect definitions, omitting the hypertext constraint is not REST. "While the true definition is interesting for academic purposes and certainly lies behind the technologies upon which we build every day, it simply doesn’t have a whole lot of use to web application developers" - this is missing the point a bit.. If you're developing web apps for humans the reason REST 'doesn't have a use' is because it's already been 'used' to produce HTTP and HTML. "Doing REST" is essentially the process of designing hypermedia types, and defining/extending a uniform interface. Examples of that would be writing the AtomPub spec or reintroducing Link headers.