Technology and Compromise

Two recent conversations with the Non-Compromisers.

NC: "I can't use Yahoo! mail"

Me: "What?"

NC: "Yahoo! mail has a "Home" tab which isn't the inbox. It always lands there."

Me: "Yep. That's a javascript thing. The tab isn't bookmarkable."

NC: "The fact that I can't land directly on the "Inbox …

more ...

What's Central Here?

The requirements are a sequence diagram showing a complex back-and-forth with the vendor's web service. Each request and reply is detailed, but there's no overview or summary stated. It's implied, and all of the business folks can articulate it, but no one wrote any of it down.

This looks like …

more ...

Wrestling with REST

REST is cool because there's less protocol there -- little more than HTTP and some kind of representation for objects (XML, JSON or whatever.) It seems to me that REST with JSON is a very lightweight approach to implementing web services. Doing this in Python further trims down the technology stack …

more ...