one part of my brain understands this is just a network graph of semantic web things. the other part really wants it to be an rpg. a weather-related rpg that we can use for dice-shaming - “just kept rolling twos so it never rained and now the world is on fire. thanks.”
“Spend an hour watching the clouds roll overhead and no two of them will be the same. The complexity and dynamic motion of turbulence make these flows fascinating, even mesmerizing, to watch. Humans are a pattern-seeking species. We like to seek order in apparent chaos, and this, perhaps, is what makes turbulence such a captivating subject for scientists and artists alike.”—
trying to come up with a presentation for an interview where the presentation is meant to be about some gis analysis problem that i’ve solved for a job that wants to start out as an ember dev by asking for a python dev.
“There’s a meaty region south of syntax and north of mathematics that we don’t have a good name for, and that’s what we learn when we learn to program.”—Peter Jaros (Sarah Mei » Programming Is Not Math) (via femmebot)
the other dev quit a few weeks ago. i keep thinking “i miss the little guy.” he is a foot taller than me. when we spoke, one of us was almost always sitting down and so he is, clearly, shorter.
at a meeting full of people really super into metadata, we still managed to put one to sleep. i blame the altitude. because using the iso 19115 lineage and data series schemas to generate prov-o as rdf xml could not possibly be boring.
do not trust mountains.
it is very difficult to try to arrange collaborative research projects based on height preferences, your potential collaborators’ memory ranges or blood oxygen levels. as in, i am tired of neck strain from working only with people a foot taller than me. if you are going to work with people who do not track decisions from week to week and it’s a long-running technically complex project, run away. just run away.
i avoid tumblr when drinking to avoid embarrassment, usually metadata related (i am very boring, tumblr), but spell better when texting while drunk. there were a lot of late nights involving international travel tips, football recaps, homebrewing and persistent identifier conversations. also community building, why relying on vm images for software sustainability is itself not sustainable (just think about it for a minute) and why people who normally manage to avoid television in real life tend to get sucked into reality shows when in conference hotels (this year’s favorite: naked and afraid).
do not trust mountains. there is hail. and marmots.
but mountains have a variety of louseworts. it’s a toss-up sometimes. bistort.
“A mind that moves associatively (as my mind does and probably your mind too) like a firefly in a grassy yard on a late June evening, has more fun (and other things too, of course, like static, like trouble) than a mind that moves logically or even chronologically.”—Pam Houston, “Corn Maze" (via Nicole)
When you bring a UUID into this world you have a responsibility to see that his existence is not wasted. You are his only hope to have a meaningful life; no other programmer will ever see that UUID. He is a special snowflake that has waited for an eternity to be born and serve as an ID. To minimize the needless abuse, only create a UUID when you are sure that he will be needed. If you accidentally create a UUID which you do not need, euthanize it by deleting all copies as soon as possible.
The first pass should be ugly, the ugliest. Any brain cycle spent on pretty is self deception. If pretty is the point then please stop. Do not, I repeat, do not spent three months on the radial menu, impressive as it may be. It will not save your company. There is a time for that. That time is not now. Instead, make grand gestures. General gestures. Most importantly, enumerate the unknowns. Make a list. Making known the unknowns you now know will surface the other unknowns, the important unknowns, the truly devastating unknowns — you can’t scrape our content! you can’t monkey park here! a tiny antennae is not for rent! You want to unearth answers as quickly as possible. Nothing else matters if your question marks irrecoverably break you. Do not procrastinate in their excavation.
Craig’s words ring loudly in my ears. You want to unearth answers as quickly as possible. Do not procrastinate in their excavation.
Superb advice for the exploration phase of just about any project, not just app development.
i have been trying to come up with an appropriately technical justification for a provenance implementation to present next week at a workshop and can’t get past “it seemed like a really great plan right after i walked into that tree and thought it was a bear” or “i used the thing in the way the thing was intended to be used but no one really bothers to do that so we look really clever.”
Q: what advice do you have for other data providers be able to use your implementation to join the earth science semantic web community, roomthily?
A: well, i’ve found it helps to be mildly concussed.
a research project which aims to understand how people make sense of big data visualisations. We aim to share what we learn about the ways in which people engage with data visualisations with the general public, to help them develop the skills they need to interact with visualisations, and with visualisation producers, to help them understand what matters to the people who view and engage with their visualisations.
keep dozing off with my thumb on the space bar and then scrolling back up half-awake and really not sure what’s going on because bees and tumblr groundhog day and it’s like a sacred trust following tumblrs, i mean the lonely chairs of cern is just heartbreaking on four hours of sleep. the chairs are so lonely and stuck in the seventies.