On the left, an aspirational watch, the Sinn265 mechanical with special materials, special mechanical movement and special, ridiculous price. On the right, the Seiko sna139 for the less that 8% of the price…if I could put one together from parts!
If you program and do interfaces, you might like watches. It is a distillation of function and interface and taste. It’s technology as your personal signature and of course, the Very First Wearable.
It might just be a reminder that not everything has to be ‘smart’ but no so smart looking.
You don’t need one any more, but you may want one because of it represents – a self contained universe of design thinking and craftsmanship that solves a problem that has been solved many times before, but in its own unique way.
Since it is a personal signature, when you find one you want, you want it. And when it is no longer available, you have to start thinking, ‘how badly do I want to make this happen?’ The answer may depend on whether you want to pick up a pair of Tweezers.
Expect all network communication to be asynchronous. You don’t know when requests will come back to you, and you likely have no idea what order they will arrive back. So you write your code asynchronously, same as you do in real life:
“Look, just get back to me when it’s done, ok?”
“Sure thing, I’ll call when it’s ready”
That’s all a Promise is – that conversation and that commitment. And they are a great design pattern to restore some sanity to asynchronous code.
If you are moving to OpenLayers3, the documentation is autogenerated, but the constructors aren’t really described all that well. The changes were enough to warrant a demo site and a workshop site that cover a lot of cookbook tasks. Find out more about Quakes in Canada at the NRCan quake center. If you want to do something with the datasets at Open Data, you can submit them to their App catalogue here
Rosetta and Philae are working hard at comet 67P and how they got there makes for some good interactive content.
Elegant simple clean interfaces work best when exploring new content that stands on its own. The dash and interface are a DOM overlay on the webgl allowing for simpler responsive layout changes for window size. The milestones really pull the interactive together and it would be interesting to have them denoted as points on the scrubber timeline or allow sequential navigation between them (i.e. [next milestone: encounter with asteroid Stein 3D] )
With exportable and maintainable csv files, data compression is not optimized but export from content creators is kept simple. The app is kept up to date on a daily basis and no web backend is really needed for DB entry. It will be interesting to see if how it is kept up to date while the imagery from Philae on the surface starts coming in. It is likely there is a custom CSV editor to ensure that no errors are made and that orbital data can be imported from other engineering tools.
Reuse: Any mission can use an interface like this. The spacecraft and target models could be changed up and of the CSV data on paths and milestones.
Social Media: The big social media aspects for ESA are webcast links, first images, and animated GIFs and simulations of approach and landing. Interactive content showing a timeline has to justify itself in comparison social media and outreach tools which are dense and event-based. They attract a different set of users who want to share in exploration actions not simply the results of the exploration. To bridge the two, embedding of Twtter feed tool, YouTube videos in the milestones section would make this a gateway interface to social media. In the other direction, a ‘goto’ function and embedding capability would make this a tool that could be quickly reference on social media channels (i.e. share this viewpoint and 3 days of orbit time)
“People aren’t puzzle pieces, turn-key products, or canned beans. They are investments, copilots, and will form connections within and outside your organization you never would have guessed”
Fuelling People is probably one of the tougher things to do in an organization – training programs, interesting work, mentorship, matched teams, surveys, open door policies, carefully tailored workloads are all a nice set of sliders and controls an organization can play with and optimize, But the most difficult thing is still creating training around an institutional knowledge set that includes some really hard-to-capture aspects – gut feel, interpersonal relations, estimating workloads and performance, turning measurements into decisions, and understanding people’s true capacities and capabilities.
Have some awesome homework. Learning is, in the end, doing, and watching someone else cook doesn’t make you a chef. Make the homework rewarding, possibly collaborative, and flexible to meet the motivations and interests of the learner. It’s also a breeding ground for real questions and feedback, not the polite stuff or pile-ons you might get immediately after a presentation
Learn how the training went – get feedback and get it immediately as well as later on. You have to learn how to teach people, after all, and accurate feedback is more than one datapoint in time – The term, “Let it sink in”, and “experience is the best teacher” have a very good reason to exist!