As a big user of Day One (and a tinkerer of some plugins for it), I really enjoyed this conversation.
One thing I like about Gabe’s list is that it’s not entirely tech stuff. Nice wheelbarrow!
I haven’t really remarked here, or anywhere for that matter, on my transition from academia. Maybe one of these days, but for now Peter Levin pretty aptly describes the why:
Some years ago, for the Columbia pro-seminar, I produced a year-by-year ‘getting through graduate school’ handout. In my little pitch to 1st years, I told them that each year, including your terminal, job-hunting year, you should take stock of your sunk costs, and ask yourself if you still want to be an academic. For me, the answer became no. And for me, like many of graduate students, as well as tenured and untenured faculty, the biggest question was, if not academia, then what else?
Peter has landed what sounds like a fantastic gig with Intel, as a “sociologist in the wild,” and I’m looking forward to hearing about his acclimatization to Portland’s environs. Happy trails!
This week’s episode of Accidental Tech Podcast continues discussion that I have really appreciated, motivated in part by Bradley Chambers’ post on the state of photo management in iOS. The followup conversation this week begins with John Siracuasa’s good-so-far experience with Everpix, and focuses mostly on the dilemma of reliable and accessible backups of one’s photo collection.
Over the years I have accumulated a series of increasingly-large external hard drives that perform both backup of my active data as well as offline storage and its backup (offline storage being for the stuff, almost exclusively photos, that I moved from primary storage to free up more space). I have had an array of backup regimes including wirelessly mounting these external drives for incremental backup using a terribly fiddly launchd+ unison and later rsync script, which turned out to be fiddly enough and require enough babysitting that I stopped doing it altogether and now rely on somewhat randomly scheduled cabled backups. In addition to these, I have backups from various points in time to cloud destinations like Strongspace and Box.net and utterly gobs of pictures at Flickr and Facebook. (Also Trovebox where I spent some time last year. You get the point.)
I have and will continue to pay good money for the desk- and cloud-based boxes that hold my stuff. Problem is, perhaps in contrast to the ATP conversation, the boxes might be too easy. I’m not suggesting that making Time Machine/Capsule work flawlessly is easy, or that most upload bandwidth allows for efficient creation of comprehensive cloud backups; but what’s easy is filling up platter after platter with data. To be sure, as a general area of computing, not having backups, or not having backups that work are substantial problems (how many of us have tested our backups or could actually perform a restore from them to rebuild a working boot disk?).
But as space gets cheaper and services proliferate, the boxes of disks become for me a minority concern and even exacerbates the problem of retrievability. More important is knowing what I have, and perhaps this is the difference between backup and archiving. I think the real problem in twenty years probably won’t be having my stuff around but using it well, by which I mean:
- that serendipitous rediscovery of a memory
- my son could use pictures of mom and dad for a surprise anniversary party
- not sorting through dozens or hundreds of photos from the same event to find a good one
- the video I shoot is discoverable
- it’s possible to find a photo of a person from a location even though I don’t exactly remember when I took it
- browsing photos is pleasant despite there being gigabytes and gigabytes and gigabytes of them, from different catalogs and sources
Some of this is a problem of discipline: and if I were just more diligent about keywording and filing taxonomy then perhaps this would be easier. But it’s also a problem of scale: Files not only keep getting bigger but we are making massively more of them every year. And unlike the storage element, the problem of scale isn’t getting easier, and won’t get easier without next-gen advances in tools that help with navigating and understanding the content of our photos.
In short, finding what I’ve stored is hard, and it’s made harder by the passage of time, the shifting of things offline as new content gets bigger than always-on capacity, and the arrival of new platforms and devices.
Going back to the beginning, I’m considering Everpix myself not for backup purposes but because they seem to take this quite seriously
It has become easier and easier to take pictures of everything, but technology to manage them has not progressed much. Photographs capture precious memories and emotions, yet a computer stores them as files and bits. Effectively, we, the users, are the only ones for whom these images still have a meaning. Maybe not for long: as photos accumulate by the hundreds, or thousands, on our phones, memory cards, hard drives or social networks, the cost of collecting, organizing, and managing them becomes so high that we also lose touch with these captured memories. Our memories could, ultimately, end up forgotten on some computer memory.
So why am I holding back? My primary reservation is about having Yet Another Service holding my stuff. Everpix would be an easy, no-brainer buy for me if it could do what they offer on my desktop — or my own storage, wherever it is — without requiring me to send them all my stuff. But at the moment maybe that’s the price for (part of) what I ultimately really want.
Okay, it’s my second workflow, but the first (which rebuilds this site) is not really publish-ready.
Grab the current URL from the Editorial browser and insert as a markdown link in the current document. Opens a prompt for the link text with the default set to the current editor selection.
I sprung for the VSCO slide film pack while it was on sale for its recent launch, and I’m enjoying experimenting with it. Having not grown up shooting film I don’t have expectations for certain looks from the presets, and the sheer number of options is somewhat overwhelming. There’s a huge amount of variety in the array of film styles. Below are a few I’ve liked so far, compared to an out of camera JPG from the X100S:
clockwise from top left: Fuji Velvia 100F Landscape; Fuji Provia 100F +; Pro Neg. Hi SOOC; Agfa Scala 200 ++
Patrick La Roque has a bunch of inspiring examples of VSCO Film 04 in use.
On the sofa with the iPad, checking out Editorial. It really is all that and a bag of chips, so far: a really nice markdown writing environment with a crazy crazy powerful scripting platform built in.
I wrote this post in Editorial and then used a short python script to publish and rebuild the blog, all right here within the Editorial interface. (Thanks to Gabe for his FTP upload script from which I cribbed the keychain module usage.)
I’ve become a big fan of NPR’s Pop Culture Happy Hour. It’s casual but also focused, so the discussion never gets lost in a lot of banter or insider-ness. Recent episodes have featured San Diego Comic Con, Orange is the new Black, fall TV, and Doctor Who. The show often features familiar voices from other NPR programming, and it’s fun to hear them outside of their normal context.
Patrick La Roque had exactly what I was looking for this morning: A quick discussion of using exiftool to get detailed EXIF data from Fuji X100/X100S JPGs. I’d love to figure out a good way to automatically pipe the film mode detail back into a Lightroom keyword for those out-of-camera JPGs that I keep; maybe I’ll make that a project for next weekend or so.
Another influence was a forum discussion about telling stories through photos; that thread (dpreview?) is lost to me now — should have saved to pinboard — but a google search led me to another of Boyer’s recent posts, Fuji X100S - Story Telling Device:
If we bottom-line this whole photography endeavor the entire exercise boils down to telling a story. With all the pigeon-holed genres the one thing in common is that inside each an images success or failure is ultimately based on how effectively it tells a story or maybe part of a story.
This is so key. Debates over bokeh and pixel-peeping, smeared foliage and focus speed (all weighed against price and/or status as a “real” camera/photographer) fill the internet with noise but so often the technical details leave out the quality of an image to tell a story.
I won’t claim to be any good at this, but I’m trying to keep this all in mind.
So. We went on vacation the past week or so, road-tripping through southern Utah and on up to the Salt Lake City area, and man I shot a ton of photos. At one point in Bryce Canyon, stopping to shoot every hundred feet or so along a trail winding up the rim of an amphitheater, I self-consciously noted that I really didn’t have any idea what would make one of these photos better than the others. Deepening sunset was changing the light, and as we walked our angle changed, too. I made some in black and white, did some panos, experimented with depth of field and persuaded my exasperated wife to stand for just a few more portraits against the canyon background.
(A note on black and white: There’s a lot to love about the out-of-camera JPGs from the X100s. The great flexibility I get from shooting in JPG+raw is that I can work up a raw image if I don’t like the JPG so much; and if I shoot a black and white JPG and start to wonder what it looks like in color, well there’s the raw.)
(But, and this aside is becoming less of one, using film modes such as the BW setting gives me a valuable intent. This one’s black and white I tell myself and the X100S chimps at me to prove it after I click the shutter. The same goes for the other film mode settings: Great sunset, let’s try it in Velvia, etc. I’m eager to get those full-size JPGs off the card to see how they match my vision at the time and my intent with the film mode. Thinking about those film modes becomes part of the telling of the story — If I have the presence of mind to compose it, of course.)
In his post, Robert Boyer lists a handful of storytelling questions to ask of his photos, and I love how detailed he gets in this inventory:
- What’s going on here at the image at the top?
- Girl or boy?
- How old?
- What’s the time of day?
- Time of year?
- Hot or cold?
- Modern or antique?
- Sunny or cloudy?
- Indoors or out?
So anyway I’m thinking as I take photo after photo of this spectacular landscape something to the effect of “I don’t know what will make this one of the tree more interesting than this one with just the hoodoos, so I’ll keep shooting lots.” Later, in Lightroom, comes trying to filter the photos and look for some keepers with questions like:
How did we get way up here? What’s it feel like to stand in that spot? Can a photo hint at the smell of rain way out there? (Also: Am I focused where I want to be? Should I adjust exposure? DOF?? Was that lightning? The signs at the trailhead said to get the hell off the ridge if there’s lightning.)
I think the point as I do this more is to try to front-load the picture-taking itself with those questions (the same way that using a film mode begins to hint at the intended effect of a photo), and then compose the photos accordingly. But one step at a time, right?
After all that, did I get a story? Well hell, hard to say. I do know that I really love trying. Right now, figuring out the balance of right technical elements and narrative components of the photo is just a great ball of fun.
Did you notice you can click the images in this post to bring up a lightbox view of all the images from the post? It’s something I’m trying out, using the lightview toolkit.
And life’s pretty good. Today we begin our drive back home, for a short southern Utah stay and then a few more days of down-time before work and school begin again.
The excellent quality of the X100S’s in-camera JPEG processing means that for many purposes it makes perfect sense to shoot JPEG+RAW with the intent of using the JPEG by default, and only resorting to the Raws when you want to pay an image special attention, as in the examples above. The most obvious case when you’d need the extra latitude of a Raw file is when you want to adjust white balance post-capture.
This is exactly how I shoot with it, and I’ve found it to work really well. If an image doesn’t have some quality I’m looking for and some minor adjustements to the jpg don’t give it to me (Lightroom can do a lot with a jpg!), I work up the raw file and see how it goes.
On dynamic range:
An alternative way of thinking about this is that DR200 is like underexposing a stop to retain highlights then adjusting the brightness afterwards, and DR400 is like underexposing by two stops and adjusting further. Because of this, the minimum ISO available in each mode is limited: ISO 400 at DR200, and ISO 800 at DR400. The flipside to this approach is shown by ISO 100, which is effectively the opposite; i.e. ISO200 overexposed by a stop then pulled-down in processing. This results in the loss of stop of highlight range - to all intents and purposes it counts as DR50, and should therefore normally be avoided. (Note ISO 100 is only available in JPEG anyway).
As usual for DPR, this is a detailed review that can teach someone already using the camera a lot about how it’s put together, what its capabilities are, and how to get the most from it.
Between ISO 200 and 800 the X100S delivers images which contain effectively no visible noise. This, coupled with the inclusion of a 3-stop ND filter means that it is entirely possible to shoot at ISO 800 outdoors in bright daylight for the sake of better dynamic range (see DR expansion modes section on the next page). In our everyday shooting we alternate between DR200% and 400% in especially tricky conditions, and we’ve learned not to worry about the consequent increase in ‘base’ ISO.
I had a great evening at the best pizza place around this weekend — got a few photos I enjoy, too.
I am so far behind on a certain category of my reading that I’m intimidated enough to mostly avoid opening up Instapaper altogether. But I keep saving things to “read later” all the same. Aspirational bookmarking at its best, I suppose. At least neither the Instapaper or Pinboard queue show up with red badges on any of my various screens.
It’s not that I’m not reading, though. I’m reading a ton, probably more this year than in quite a while. On the treadmill at the gym I’m slowly making my way through Passage of Power by Robert Caro, a genuinely fascinating — and challengingly lengthy — telling of LBJ’s journey to the presidency. It’s enthralling, and also 736 pages long, which, when rendered in Kindle format sufficiently large to read while bouncing along at the five to six miles an hour I can manage on the treadmill, results in something like 20,000 “locations” in Kindle-speak. I’ve borrowed it three times from the local library, which I suppose is a sign that a) I enjoy it and b) I don’t read it particularly quickly, and c) nobody else is borrowing it.
The treadmill or bike at the gym seems to be the primary place where I do most of my reading, these days, being as they are among the few places where a 35-inch-high pre-schooler isn’t eagerly seeking my attention. This beautiful summer season, I feel somewhat guilty for not being out on the trails, but time and attention are the resource now most in demand and shortage, so fresh and piney air often fall third in the priority list to a good workout and enjoying some reading.
I’m still getting out and about quite a bit, too. It’s a beautiful monsoon season here, so far.
I’m having a blast with this new camera, the Fuji X100S.
I had a conversation with my wife today that seemed to bear on why this camera is so much fun. She’s looking for a new bike and has been demoing some from local shops to find just what she wants. (This, by the way, is where our little outdoorsy town excels; want a new mountain bike? Half a dozen excellent shops have gear for you. But if you want a camera, you can try your luck at the Best Buy, or drive 140 miles to the big city.) This morning she rode a bike that is on paper superior to the one she tried earlier in the week, with higher-specced components, insane suspension and a frame design that should be precisely in her wanna bike sweet spot.
But it wasn’t a much fun as the one the tried earlier. The experience of the first bike was just better, but not in a way she could quite explain or quantify. The ineffable sum of its parts just add up to more, and I guess that’s about the same with this fixed-lens, slightly slow to focus, battery-eating and sometimes just obtuse little Fuji. I still have the fancy glass if I ever want to upgrade to a new shiny DSLR body, but it simply feels good to sling the X100S over my shoulder and go for a walk, and I love the photos it makes.
I got an Eye-Fi card to use with it, to pull jpgs right off the card through the vapor while I’m away from my computer. It seems to work well, is not automatic (in the sense that I can turn it on and off and it requires the iPhone or receiving device to be set to its own wifi network to receive) but that’s probably better than something that’s unpredictable. The eye-fi adds imported photos to three locations: one, the in-app gallery; two, the iPhone camera album; three, an “eye-fi” gallery in photos app. This means that it’s a piece of cake to select jpgs in the camera roll and share to an icloud photo stream – meaning that those images are quickly available on my iPad, too (or, via shared photostream, anybody else’s I share with).
My flow is shooting with the X100S, doing in-camera development as desired to produce some jpgs, then turning on the eye-fi when ready to sync to the phone for sharing or (via Dropbox) taking a closer look on the iPad.
This is an out-and-about type of workflow, because I will still download and work with raw if/when I want more control or am not satisfied with jpgs. But it will be fun when traveling or enjoying busy days that keep me away from the laptop. And, because the photos get put in the camera roll, they also get uploaded to dropbox if its app is configured to upload from the camera roll. This latter effect may create some redundancy, but it’s also a nice and complete circle – out-of-camera images can easily be pushed everywhere I want to use jpgs.
A couple recent photos that I enjoyed:
X100S and a nice Kolsch at Mother Road Brewing
So I went and got that camera
After a long couple of months of thinking on it, I was ready for a new camera, but surfing dpreview only made it harder to decide. The mirrorless options were looking good — like the upcoming release in the Olympus line, the E-P5. On a whim, I emailed a Phoenix camera shop one Saturday morning to see if they had the hard-to-find camera I thought I might enjoy.
“One in stock” they told me. Oh. “We can hold it for you until the end of the day.” Oh.
It was the perfect combination of coincidence, opportunity and well-informed impulse buy. So I took a quick road trip down the hill to the 106° F heat and picked up a shiny new Fuji X100S for myself. (Related: How nice it was to go into an actual camera shop and have a chat with guys who love what they do instead of trying to ask a bro at Best Buy whose last sale was a dryer. It was great. I miss having a local shop.)
And a week later, man am I having a good time. I’m learning the ropes of a very different kind of camera for me, and enjoying all of it.
The X100S is lots less unobtrusive than the big DSLR, making it easier to shoot candid street-style photos. The smoker at the brewpup is a shot I wouldn’t have made with the big old Pentax (manual focus, too, thanks to the focal distance indicator in the EVF). And the focal length of the Fuji is just a little wider than my favorite FA 35mm Pentax lens, so it’s a familiar field of vision – which is making the rangefinder-style optical viewfinder a little easier to get accustomed to. The hybrid/electronic viewfinder is great: Fast, with display of a lot of information in the overlay.
Out-of camera JPGs are good, and the camera includes several film simulation filters to “develop” raw images in-camera. Since the raw files are a big 32mb, which pushes my old lappy 386 quite a bit, I have been trying to practice developing raw in camera or simply shooting in JPG. This is a change for me because I have shot raw a rule on the old camera; but exposure, noise and detail are so good on the X100S that it’s much more feasible to fiddle with a few JPG settings and leave it at that. There’s a simplicity to that, too, though I’m a long way from giving up on using LR to post-process altogether.
There are a bunch of useful X100S resources I have learned from as I experiment and play:
- Fujifilm Finepix X100S — compared to the X100: Although a comparison to the original X100, Fredrik Averpil’s review is a good review of capabilities and use.
- Fujifilm X100S DNG camera profiles and some presets: More from Fredrik Averpil, beautiful film presets
- Is there a setting you leave on X100S the most?: Zach Arias on how he shoots with it.
- Fuji X100S custom settings: Settings recommendations and a walkthrough of the custom settings configuration
- How to set up your Fujifilm X100s for street photography « Mike Kobal: More on settings
- Fuji X100s - Links Testberichte - Reviews - WOSIMs Photography: A big, big index of reviews
- Fuji X Series and Post: Settings, postprocessing discussion
- Photography Stack Exchange: I didn’t know stack exchange had a photography site — this is pretty cool.
- The First 100 Days with the X100S: Brian Kraft has a bunch of lovely photos from the Denver area that make me miss the Rockies, and he shows off a lot of the camera’s capabilities.
(By the way)
The photos in this post are served up via a really slick gallery and portfolio application called Koken. It’s self-hosted and has a beautiful interface that supports embedding as well as its very own writing engine for blogs or portfolios. I uploaded the photos through its Lightroom publish service plugin. Good stuff, worth checking out.
Koken is a free system designed for photographers, designers, and creative DIYs to publish independent websites of their work.
I installed Koken last night to give it a try, thinking I might use it to replace other photo sharing platforms. It has an elegant installation process and the application is really sophisticated. Plus, it has a Lightroom publishing service plugin so you can upload images to a Koken installation by pushing directly from LR. Very cool.
Busy days here, which is not really anything new. I have found in my spare time that I have been quite happy to work on my growing catalog of toddler photos and spend lots of time biking and jogging — summer has come to 7,000 feet and it’s time to soak up the outdoors.
But there have been a bunch of bits and pieces bubbling along that I have wanted to share. Here are a few of them.
Here’s a Drafts action that sends entries to Day One along with a tag for my son’s name. This one is for capturing and saving bits and pieces of things he says and moments that catch me off-guard — which, as he gets more remarkable, are most days. Replace TAG twice in this to use it with a different tag; nothing complicated here, but I had to tweak it a bit to get what I wanted (specifically, to get the right urlencoded newline strings so that Day One would handle the tag correctly.
My friend Alice has started up a podcast called Educating [Geeks], with the premise that, “At some point in our lives, we’ve all been on the receiving of the incredulous shock and horror when a superfan realizes that you’re not a member of the club.” They find inspiration in this great XKCD strip that celebrates bringing people into the things we love and excited or fascinated by. I’ve been stewing on a longer post about this and some perhaps interesting thinking, but just can’t seem to get it out the door, so check out the podcast in the meantime. I think you might enjoy it. It’s fun.
Here’s a guy who has really thought about notebooks (among other things; Sean has a great set of outliner based pages about all kinds of things that are interesting).
The National Day of Civic Hacking looks cool, much more practical than a lot of change-the-world-with-technology enthusiasm. I missed the actual event this year but will watch to see what comes of it.
I dusted off and started to update my data from The Setup this weekend. Here’s a plot of some selected text editors that people discuss over the past few years. I’ve cut the 2013 data because there’s not much information there, yet, and it makes it appear as if the frequencies of all the editor mentions go way down.
For all the noise about fancy new-generation editors, respondents at The Setup seem to hew old school, or at least talk old school, as the data reflects mentions rather than actual use. (Seriously, this is just about as unscientific as it gets. But it’s fun.) Will TextMate return to prominence in 2013, or will Emacs continue its ascent? Can Sublime Text outpace vim? Time will tell.
Bonus update, mobile devices. I was having fun, so I updated to include a swing at mobile devices. This may be an incomplete count of the various Android devices. Rather than filter out the devices with just a single count, I included them to show some of the variety (which also tends to highlight just how dominant the iOS devices are).
You may be saying, “hey, what about Windows Phone?” Well, here are the current counts:
Mobile Devices: --------------- iPhones: 190 iPads: 132 Androids: 72 Windows Phone: 1
Now you know.
The fitbit folks have improved their dashboard quite a bit. The new display has moveable tiles and is pretty nice, but the most substantial improvement is that the data displays don’t require Flash any longer. Finally, that information is usable on iOS.
And they revamped their sleep record to be much more useful:
This was a labor of love:
(Updated March 23, 2014)
An annual exercise challenge rolled around again at my workplace, so naturally I found a project in it: Wondering if I could hook Runkeeper up to my Day One journal. The result: The Runkeeper plugin for Slogger
Getting up and running with the Runkeeper API was tricky; I never quite got the hang of passing parameters to it, which still puzzles me. When I figured it out, I put together a quick walkthrough for the API startup and posted it as a gist (Also embedded at the bottom of the post). The gist provides some instructions, but users new to Slogger plugins and working with API authentication may also want to check out Sven’s writeup that uses this method and includes a couple of additional screenshots.1
One note about configuring your Runkeeper application: The Runkeeper folks don’t want to appear to endorse any applications or have them potentially be confused for official Runkeeper services, so avoid identifying your app with anything that uses “Runkeeper” or “Health Graph” in its name or description to save yourself from receiving a polite email requesting you to make a change.
I built the Runkeeper plugin for Slogger with a fun option to save its data additionally to a text file. I plan to do some stats or plots or something with that data, perhaps akin to my fitbit visualization, one of these days.
The future is extremely hard to see through the lens of the present. It’s very easy to unconsciously dismiss the first versions of something as frivolous or useless. Or as stupid ideas.
Eighties bombast soundtrack reclaimed as moody southwest indie rock. I love Calexico, and this is fun.
Fun and interesting conversation on Generational about blog platforms and static blog systems. Discusses hosts, editing and practically solving some of the “how-do-I” problems writers may face.
I know I’m going on and on, but I’m enthused. I use Slogger to save entries from twitter, last.fm, app.net and fitbit activity to Day One. Just as with the build tool for my blog here, mover.io helps remove the laptop from the workflow. See, I don’t have have a dedicated old machine to run as a server for my Mac stuff, so the standard method of running slogger via a daily scheduled task doesn’t work so well for me. I set a reminder.