happyshadows

This is my approach as well. Works very well with an event-sourcing model.

It is much easier to capture user intent with POST /api/customer/1/change-address-due-to-move { "address_1": "...", "address_2": "...", ... }

than with: PUT /api/customer/1 { "address_1": "...", "address_2": "...", ... }

Also, GET /api/resource/action is nice place for a payload describing the expected inputs to the action. Link it all together with hypermedia and you really have something ;)

Believe others are coming around to this line of thought: ThoughtWorks included "REST without PUT" onto their technology radar earlier this year.

Same issue here. Now so off-track that I'll probably just change the content-type and call it a day.

When Lord? When the hell do I get to see the goddamn sailboat?

Seems like a throwback to the days of the web portal (ala Yahoo.)

Mutations is a great gem. I've used in my latest project and it has been an exceptionally useful tool for managing complexity.

I wish Google would change their meta-tag from "origin" to "always". It's getting harder and harder to see which keywords bring traffic to your site these days.

I would stick with GA and just trigger an event via javascript once the body of text is scrolled through.

If I didn't know how to do that, I would probably use a scrollmap tool like CrazyEgg.

Analytics calculates the time on page by the time difference _between_ page hits. One hit: 0 seconds on site. Because of this, it isn't an accurate metric to measure engagement for a single blog post.

One of the tangental points you raised was wrong so you are wrong!