New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL all the things #308

Merged
merged 15 commits into from Nov 12, 2015

Conversation

Projects
None yet
2 participants
@benbalter
Copy link
Owner

benbalter commented Oct 22, 2015

Fixes #301.

@benbalter benbalter self-assigned this Oct 22, 2015

benbalter added some commits Oct 30, 2015

@benbalter benbalter changed the title WIP: URL all the things URL all the things Nov 6, 2015

@benbalter

This comment has been minimized.

Copy link
Owner Author

benbalter commented Nov 6, 2015

@bkeepers, @spraints absolutely no obligation, but if you have a free cycle to skim the post in this PR, based on our conversation in Chicago, it's still a bit rough in terms of writing, but I'd <3 your thoughts if you can spare them.

@spraints

This comment has been minimized.

Copy link

spraints commented Nov 9, 2015

I like it. The first time I read through it, I got the impression that URLs would be a way to set decisions in stone. On the second read, I spent more time in the sections about what's good and what's bad, and I think those are good.

For me, one of the key values of URLs is that it helps my team to work async and distributed. There's an aesthetic angle, too: good URLs tell you what they are. And good URLs make it so that I can link right to what I'm referring to (e.g. "chat with my by going to this link" not "chat with me by downloading this app, signing in, clicking on the category 'welcome' then the topic 'new people' then finding my name in the list").

benbalter added some commits Nov 12, 2015

@benbalter

This comment has been minimized.

Copy link
Owner Author

benbalter commented Nov 12, 2015

. There's an aesthetic angle, too: good URLs tell you what they are.

I wrote about that a bit in http://ben.balter.com/2014/10/07/expose-process-through-urls/ (and went a step further, to sadly have to say that URLs link to content, which in government, isn't always true).

@benbalter

This comment has been minimized.

Copy link
Owner Author

benbalter commented Nov 12, 2015

For me, one of the key values of URLs is that it helps my team to work async and distributed.

You're 100% right. I tried to capture that with the idea of "preferring systems that can render organizational context time and location agnostic", breaking async into what it actually means to be async, as async can be an unintuitive concept for those not previously exposed.

benbalter added some commits Nov 12, 2015

benbalter added a commit that referenced this pull request Nov 12, 2015

@benbalter benbalter merged commit 67f5431 into master Nov 12, 2015

0 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build failed
Details
continuous-integration/travis-ci/push The Travis CI build failed
Details

@benbalter benbalter deleted the url-all-the-things branch Nov 12, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment