3 ms·
> It's telling if their first instinct is to have a "createUser" endpoint versus a POST to /users/ It's telling of what exactly? RESTful is just one style of
by nandemo 13y ago
> It's telling if their first instinct is to have a "createUser" endpoint versus a POST to /users/
It's telling of what exactly?
RESTful is just one style of creating application interfaces over HTTP. And as far as I know, web apps with true RESTful interfaces are somewhat rare. [1] If you don't ask the candidate to do it RESTfully, it seems like you're doing the common interview anti-pattern of asking a question that is open-ended but expecting a particular answer.
[1] http://www.intridea.com/blog/2010/4/29/rest-isnt-what-you-think-it-is# http://www.intridea.com/blog/2010/4/29/rest-isnt-what-you-th...
- twerquie 13y ago> It's telling of what exactly? That the candidate favors transport-agnostic APIs or has limited familiarity with HTTP. One easy follow-up: "I notice you decided to call the method createUser..." and you've learned something concrete. They'll either stare blankly or discuss their preference for JSON-RPC or SOAP or whatever. > And as far as I know, web apps with true RESTful interfaces are somewhat rare. It's common to take advantage of HTTP's verb syntax.
- ericgoldberg 13y agoIt's telling that they don't know (or do know, but don't see the benefit in) RESTful interfaces. Which isn't a dead-end for the interview, it just leads to more questions to see what they understand about HTTP. I'm not expecting a particular answer, I'm using a question to understand where someone is at and then using the following discourse to understand how they arrived there.