Comments for Mike Pearce - blog

Comment on Why do I even care what version your API is? Versioning your API with HATEOAS by Philip Schweiger

Philip Schweiger — Sat, 21 Jan 2012 14:12:22 +0000

I think you can make an argument for versioning adhering to REST.

REST is all about resources, and an API is a contract promising that a given resource will exist at the specified URI. You could argue that the behavior of a resource is one of its intrinsic properties, hence if that changes, you really have a different resource. (Note that this is different from the format – the representation of a resource can change without the actual resource changing).

To back this up with an example from the actual source:

“For example, the “authors’ preferred version” of an academic paper is a mapping whose value changes over time, whereas a mapping to “the paper published in the proceedings of conference X” is static. These are two distinct resources, even if they both map to the same value at some point in time. The distinction is necessary so that both resources can be identified and referenced independently. A similar example from software engineering is the separate identification of a version-controlled source code file when referring to the “latest revision”, “revision number 1.2.7″, or “revision included with the Orange release.”
(http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_2_1_1)

In an API that honors contracts, you’re likely to have consumers that expect the resource to exhibit a certain behavior (dare we say, a resource in a given ‘state’?). That’s your versioned resource, the equivalent of “paper published in the proceedings of conference X”

Now, I don’t see why couldn’t ALSO have a non-versioned URI that links to a related resource. This would be akin to what you described above, and would work for API consumers that only care about the latest version (or if you prefer, most recent available ‘state’). From what I’ve read on REST, though, I can’t see any reason why using versioning to signal a static state of a resource violates any RESTful constraints.

Comment on A change of direction by Laurent F

Laurent F — Wed, 18 Jan 2012 11:38:15 +0000

Hey Mike!

Congratulations for your promotion! Well deserved and I am looking forward to reading your future posts

Comment on Agile core values: Individuals and interactions over processes and tools by Mike Pearce

Mike Pearce — Mon, 19 Dec 2011 07:34:30 +0000

Hi Lincoln, thanks for your comment. However, I’m not entirely sure what you mean? If you’re talking about the agile manifesto, you can only really talk abstractly, that’s what it’s for. The ‘values’ and ‘principles’ are there as guidelines for whatever method of software development you choose. Scrum isn’t a ‘principle’ as you say, it’s just a framework and while talking about individuals and interactions over processes and tools in the context of scrum would be an excellent topic for a blog post, it’s not irrelevant to discuss it like I have. The contents of this post serve as well in scrum as they do in kanban, dsdm, crystal and even waterfall. Thanks for the feedback though, it’s given my a good idea of what kind of thing to post next!

Comment on Agile core values: Individuals and interactions over processes and tools by Lincoln

Lincoln — Sun, 18 Dec 2011 06:11:32 +0000

talk about interactions and individuals in detail ….i hate this subject cause no one ever talk about this agile thing in deep why because you all speak general things choose a one agile principle like Scrum and talk about its interactions and individuals or else don’t polute the internet with poor information

Comment on git status on multiple repos by Chris Clements

Chris Clements — Mon, 05 Dec 2011 16:40:54 +0000

Thanks, this is awesome.

Comment on 10 Reasons why using a whiteboard is better than a digital tool by Print your spreadsheet based User Stories « Mike Pearce – blog

Print your spreadsheet based User Stories « Mike Pearce – blog — Sun, 06 Nov 2011 23:16:03 +0000

[...] I’ve mentioned in the past and spoken about at the London Scrum gathering, you should have a physical sprint backlog. The [...]

Comment on How do I estimate how long an agile project will take, before we start? by SCRUMCast #31 – White Elephant Estimating | Integrum

SCRUMCast #31 – White Elephant Estimating | Integrum — Thu, 27 Oct 2011 12:02:10 +0000

[...] Lengel-Zigich, Roy van de Water, Derek Neighors and Drew LeSueur talk about White Elephant estimating, a new way to generate estimates for stories to instead of the same-old planning [...]

Comment on You don’t really want a faster horse! by PM Hut

PM Hut — Thu, 27 Oct 2011 10:39:56 +0000

Hi Mike, I think the essence of getting proper requirements is: 1- Understand the business of the client 2- Interview the client about his needs - Ask as many questions as you can, based these questions on his understanding of the business I have published many (I mean many) articles on requirements management on PM Hut, you can find them here.

Comment on The difference between git pull, git fetch and git clone (and git rebase) by Davide Ganz

Davide Ganz — Sun, 16 Oct 2011 12:44:22 +0000

Nice e Clearly Written Info…
Thanks

Comment on Should I start with scrum, or kanban? by pmhut

pmhut — Fri, 23 Sep 2011 05:52:47 +0000

Hi Mike, I have published a few articles on Kanban and Scrum, lately this one. I think your article examines an issue that most companies think about right now, which framework should I follow to manage my projects? I would like to republish your post on PM Hut, please either email me or contact me through the "Contact Us" form on the PM Hut website in case you agree with this...