Reputation
204
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 6
Newest
 Commentator
Impact
~539 people reached

  • 0 posts edited
  • 0 helpful flags
  • 20 votes cast
Jan
20
awarded  Commentator
Jan
20
comment In REST is HATEOAS really about self-discovery or about navigation?
@Ewan: It seems like it, to an extent (based on my very limited understanding). But it's more than that because it also involves state. ie This is where I'm at now, what valid actions can I perform from here? So it includes links that represent those further actions. eg If I create a resource then the server may return a link to that resouce so I can update it or delete it if I wish.
Jan
20
comment Does discoverability in HATEOAS require the information must be machine readable, or can it just be human readable?
@AilurusFulgens: Both your links are very interesting, thanks. I've just spent a couple of hours reading the linked documents. Hydra seems very complete but also more complicated to parse (for both a human and a machine) compared to HAL or Siren. HAL is very simple, basically just links but also links to documentation, whereas Siren seems to sit in the middle between HAL and Hydra.
Jan
20
accepted Does discoverability in HATEOAS require the information must be machine readable, or can it just be human readable?
Jan
20
comment Does discoverability in HATEOAS require the information must be machine readable, or can it just be human readable?
@guillaume31: By "machine readable" I was thinking of data or meta-data that can be interpreted by a client application. Examples: (1) Including a well-known media type in the response header that would define the format of data the client should send; (2) Sending links via a Link header that include well-known relation names so the client can determine what its next action is (choose an option based on a relation name it recognizes, then use the link associated with that relation name for the next request).
Jan
17
awarded  Yearling
Jan
17
awarded  Editor
Jan
17
revised Does discoverability in HATEOAS require the information must be machine readable, or can it just be human readable?
added 37 characters in body
Jan
17
asked Does discoverability in HATEOAS require the information must be machine readable, or can it just be human readable?
Jan
17
answered In REST is HATEOAS really about self-discovery or about navigation?
Jan
16
comment In REST is HATEOAS really about self-discovery or about navigation?
@RobertHarvey: I found the spring article much the same as many of the examples I've seen, all about links and implying HATEOAS is just about navigation, without saying it explicitly. The Wikipedia article was confusing: The Details section was just about links, once again, but it also included the quote "A REST client needs no prior knowledge about how to interact with any particular application or server beyond a generic understanding of hypermedia", suggesting HATEOAS is about discovery in general, not just links. However, your link "What does HATEOAS offer..." was very illuminating. Thanks
Jan
16
comment In REST is HATEOAS really about self-discovery or about navigation?
I like your analogies of Wikipedia and a Choose Your Own Adventure book, they make the concept quite clear. Thanks.
Jan
15
asked In REST is HATEOAS really about self-discovery or about navigation?
Jul
4
comment How can a manager ensure developers are pushing up to the origin every day?
We already tend to use per developer or per issue branches before merging into a release branch. The issue we face is one developer stepping in to take over from another on holiday or away sick: Did the absent developer remember to push their latest code up to the origin or not? It's particularly a problem when someone has been working from home and we can't access their dev machine. I'm sure other teams have run into this same issue and I wonder what they do about it.
Jul
1
comment How can a manager ensure developers are pushing up to the origin every day?
@Daenyth: Nope, not a cop out. Folks want to do the right thing but no-one's perfect - that's human nature. Any process that relies on people to be perfect every single time will fail. That's why we put safety guards on machines and construction workers wear hard hats. I'm looking for a way of doing things that'll give my manager what he wants without relying on unachievable perfection from the people involved (I'm also aware that developers are professionals so should be treated with respect, not be like they're in the army or in primary school, however).
Jul
1
awarded  Scholar
Jul
1
accepted How can a manager ensure developers are pushing up to the origin every day?
Jul
1
comment How can a manager ensure developers are pushing up to the origin every day?
That sounds perfect. I think my manager is particularly worried about visibility, because with the centralised source control systems with SVN he had that visibility; he could see who had stuff checked out and who hadn't checked work back in in the evening. That web report sounds exactly what he needs.
Jul
1
comment How can a manager ensure developers are pushing up to the origin every day?
I totally agree with your I imagine most people simply don't do it because they forget when it comes to home time. I don't think people are doing it deliberately. Will check into Fossil, hadn't heard of it before. Can't help feeling that other teams seem to use git without problems and wonder how they do it.
Jun
29
comment How can a manager ensure developers are pushing up to the origin every day?
@delnan: The problem is human nature: folks tend to take shortcuts, even when told not to. If you tell people to not walk on the grass they still will, if it's quicker than going the long way round. So you need to maybe put a low wire round the grass, or similar, to make it just a little more difficult to cut across. The extra small difficulty is enough to persuade people to go around rather than cutting across. So I'm looking for a way to do that with Git, to make it easier for the developers to do the right thing than to be slack.