jdd.io

Hi! I’m Duncan. I’m a photographer and web geek who loves to travel the world. This is my tumblog where I share quick thoughts, links, and photos. My portfolios, essays, reviews, and more can be found at duncandavidson.com

[duncandavidson]

Wow. The last few months have been a complete maelstrom but everything is working out well. Yesterday was the last day I owned my place in Portland. I’m sad to see it go, but I’m already enjoying the start of the next chapter. More to come. Soon.

[duncandavidson]

Quickly resetting dates in Wunderlist

I’ve long been a partial adherent to David Allen’s Getting Things Done. I’m not nearly process oriented enough to do the entire system, but I do try to offload my tasks out of my head into a list form and keep things up to date. Since I’m joining the team behind Wunderlist, I started using it as my personal task keeper. It doesn’t enforce a strict GTD approach, but it is lightweight, fast, and syncs between devices on different operating systems.

The only thing that vexed me about using it as a full-time task manager was that I found resetting the due dates during a review cycle to be a bit of a pain. Then, Benedikt Lehnert clued me in to the fact that on the desktop client, I could right click a task and quickly reset the due dates to something reasonable—Today, tomorrow, or even an outright removal if a task suddenly became fuzzy. Perfect!

[duncandavidson]

If you’ve been reading my newsletter—hint, these mailings will be a big part of my online writing from now on—you know that I’ve started a huge transition from Portland to Berlin to take a job working in software again. Today was Day 1 of working with an incredible team at 6Wunderkinder on Wunderlist as a cross-platform developer. That’s right. After over a decade of freelancing, I’m going back to salary work. I’m more than excited to be joining forces with longtime friend Chad Fowler and thrilled to get to work with new friends that are awesome at what they do, and do it with a serious emphasis not only on code, but on design as well.

More to come later this week in the newsletter.

(Image from the 6Wunderkinder jobs page)

[duncandavidson]

I sent the second issue of my newsletter out on Monday. If you didn’t see it, give it a read!

[duncandavidson]

After getting annoyed by people asking for likes at the end of Medium articles and whining about it on Twitter, I wrote a longer article—on Medium of course—about why I think the practice should be abandoned.

[duncandavidson]

Along the waterfront in Thessaloniki, Greece on a sunny cool day far far away from the polar vortex currently freezing out big chunks of the United States.

[duncandavidson]

This weekend, Katerina ditched me to go to an all night bachelorette party with her girlfriends. Saturday morning, however, I crashed the party for a little bit to make some photos of a very pregnant Andy. This is one of the results taken on a balcony with nothing but open sky as a light source.

[duncandavidson]

Resting for Health

In January, I’ll be participating in Lift’s Quantified Diet Project. I wrote a bit over on Medium about why. For science! And health! Oh, and it was pretty interesting giving Medium a workout. It’s a lovely environment to publish with. I’m still vaguely uneasy about that whole business model thing, however. 

[duncandavidson]

Late last year, I gave a small talk at TEDxBeaconStreet discussing what I see as the essential challenge of photography: reducing what’s happening in four dimensions into a two dimensional frame that you can then hand off to somebody else. I hope you enjoy it.

P.S. I dealt with watching my own talk today by adding “as one does” after various things I said including the various places I traveled to. Turns out, it’s a fun game to mock oneself like that, as one does.

[duncandavidson]

Umbrellas on the Thessaloníki waterfront

[duncandavidson]

Yesterday, I published first issue of my newsletter which I intend to send out on a weekly-ish basis through 2014. By weekly-ish, I mean every 5-10 days—shorter when there’s something worthy, longer when things are slower.  

[duncandavidson]

For 2014, I’m starting a weekly newsletter that will collect some of the thoughts, themes, photos, and more from my week. Sign up at MailChimp. The first one goes out Jan 1st.

[duncandavidson]

Cloudscapes over America on Christmas Eve as I made my way from Portland to Chicago to Newark

[duncandavidson]

[duncandavidson]

06:05 Christmas Eve at PDX pushing back for departure to Chicago. It’s not a subject that necessarily needs a super sharp lens.

[duncandavidson]

Which bigger is better?

Mike Clark and I were chatting on Twitter about noise and sensor resolution and I made the quip that “More pixels are almost always better”, at least when you’re north of 20 megapixels. Now, Twitter is a horrible place to say something like that—especially for someone like me who has long been in the bigger pixels are always better camp—so I quickly restated it as:

Or maybe a better way to think of it is that bigger pixels are better than smaller until you have ~1.5-2x the smaller ones.

Again, a quip forced into Twitter length and not really accurate, so let me unpack it a bit more here.

The truism that, all things being equal, bigger pixels in a camera sensor are less noisy than smaller pixels on a pixel-by-pixel basis is still absolutely in effect. But now that we’re moving into the realm of 24 and 36 megapixel sensors, there are other factors at play that are changing the game and reducing the effectiveness of that rule-of-thumb.

One of these factors is oversampling. When you take 24 megapixels and process them down to a finished image—whether that’s sized for your HDTV or a large print, the little bits of noise variation between pixels gets smoothed down more than when you start out with half the data—much in the same way that oversampling audio makes for better recordings. To be sure, there’s got to be an upper limit to where this benefit is, but evidently we’re not there yet.

Another factor is that the noise that is there is of a better subjective quality than ever before. Each generation of sensors seems produce noise that’s more and more like grain. This kind of noise is visually more appealing is the sort that helps acuity. It also seems to respond better to downsampling than the older, blocky noise of past sensors.

And finally, there are all the other factors that go into making a modern sensor that are continually improving all the time. Firmware, back-illumination, and a thousand other details that are part of the secret sauce of making amazing sensors. These are all exerting themselves in interesting ways that make relying on a single axis of judging a sensor—such as pixel size—problematic. And, they are most obvious on cameras that are twice the resolution as the ones that were state of the art not long ago.

So yes, big pixels are great. They always have been and always will be. But you know what’s better? Big sensors stuffed with pixels that are big enough to constrain noise, but are small enough and packed in tightly enough to bring the advantages of higher resolution, oversampling, and probably a few other factors that don’t reduce themselves down to a simple comparison statement to bear. Oh, and make ’em state of the art pixels. 

Also, you know what’s amazing? Simply being able to pick between so many great cameras and go out and make better photographs than ever. All that’s required is a good eye and some practice. From the the APS-C size Fuji X100s to the full-frame Sony A7 or Canon 5Dmk3 or Nikon D800, there’s never been a better crop of sensors.

[duncandavidson]