Differences between revisions 15 and 17 (spanning 2 versions)
Revision 15 as of 2016-08-12 13:58:24
Size: 3474
Editor: shoobe01
Comment:
Revision 17 as of 2016-08-16 19:47:38
Size: 4800
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * [[|]]  * [[https://www.minnpost.com/business/2016/08/rise-and-fall-gopher-protocol|]] ... last month had the history of something. This is super, super cool on how the WWW was not a foregone conclusion. predicting the future is hard.
 * [[http://www.independent.co.uk/news/world/europe/british-airways-stops-musician-from-flying-with-cello-as-it-didnt-have-a-visa-a7187516.html|British Airways stops musician from flying with cello as 'it didn't have a visa']] Let's have a funny one. Read the article. Giggle. Okay, what went wrong? Not sociologically or politically, but what went wrong with systems? We don't know for sure, but we can guess. The website she booked through required her to give a name to each ticketed "passenger." So she did. The BA system requires each passenger to have a visa. Impasse! Solving this is not just on one system, but both, and all. Edge cases need to be dealt with, and we're in a bad trend of simplifying by removing features instead of designing well. Since it's possible to buy a ticket for a seat to put a not-person there, that should be an option. An obscure, hard-to-find option, but one anyway. And people who mis-allocate in one part of the process, should not be disallowed from fixing it later on. Now, go back and think what you are doing to the systems you design. Can this happen to you?

For a complete index of the monthly newsletters, see http://4ourth.com/wiki/Newsletter

To sign up for 4ourth Mobile Online Training, visit http://4ourth.com/Training/

September 2016 (last edited 2016-09-11 17:23:25 by shoobe01)