20 Questions
Zero Vis...what?
Viscosity is, loosely speaking, the measure of a fluid's resistance to flow. Honey, for instance, has a (relatively) high viscosity. Flowing without resistance, or having zero viscosity, is a property observed in superfluids, a state of matter that is only found in liquid helium, ultracold atomic gases and (theoretically) in certain realms of high-energy and astrophysics. Superfluids exhibit some startling patterns of motion that defy both gravity and surface tension, such as climbing the walls of their containers. Like their better-known cousins, superconductors, they only occur at very low temperatures: the critical temperature (or λ-point) for helium-4 is 2.172K, which is -270.978°C or -455.7604°F.
Who thought that was a good name?
I did. I'm Kent English, the guy behind this site. Brief bio: I grew up on a farm outside Hamiota, a small town in southwestern Manitoba. I studied math and physics at Queen's University, where I also developed an interest in languages. That lead me to spend some time in Japan, although I've sadly lost a lot of my proficiency in 日本語. I've also had a long-standing interest in computers and programming, which is why these days I can found be at Uncharted Software.
OK, but why did you think Zero Viscosity was a good name?
Oh, that's what you meant. I first encountered superfluids and zero viscosity in high school, because—let's face it—I'm a bit of a nerd. I ultimately chose it as the name of my site (and my consultancy, Zero Viscosity Data Integration Solutions) because I work with data and I liked the idea of data flowing smoothly from one point to another without any resistance or—you guessed it—viscosity. In retrospect, perhaps I should have chosen a name that's easier to spell. To migitate that issue, the domain zevi.co also works.
You say you work with data... what does that mean?
Well, it depends on the day of the week. I work with data in a variety of capacities. On Mondays I'm often figuring out which kind of data store to use for a particular problem and how best to organize the data once I get it. I spend time on Tuesdays building back-end systems to retrieve or transform raw data. Wednesdays find me working on an API layer to deliver transformed data in JSON or some other format. Thursdays are usually reserved for buliding single-page web applications that allow you to interact with the data served up by the API. I like to spend Fridays doing analysis on some processed dataset and generating visualizations of it. On weekends I put the other days in a Yahtzee cup and scramble them up for the next iteration.
5 != 20. Where are the rest of the questions?
Apparently you're good at counting. It's true that I'm a few questions short, however they say patience is a virtue. I'll add more questions as they occur to me.