High Volume Photo Management

When my eldest child started swimming on a team at at 6, I brought my camera to the meet, like a good dad. Since I had invested in good lenses (Canon 100-400 f4.5-5.6L and 70-200 f2.8L) I was getting some pretty good shots. It took some time to develop my skills and figure out the timing to anticipate when the swimmer will be breathing, but I kept getting better by simply taking photos of more than just my kid.

Darien in 2006

Didn’t take long to be designated the team photographer and, since I was at the meets already with my gear, it wasn’t a big lift to start shooting all of the swimmers. Following a typical meet, I would have between 500 and 700 photos to sort through and this also required some new skills – metadata tagging and photo culling.

With video-game like reflexes, I can go through a set of photos and quickly identify whether there’s anything worth keeping – no face, no sale – and mark it for removal. Then the more difficult task – delete everything marked. Trash it. Delete from disk and don’t look back. That drops the total to 200-400 or so shots remaining. So, I’m done, right? Not quite.

Another Craig swimmer takes to the blocks

Shooting kids, ages 6-18 or so in bathing suits, both in and out of the water adds a higher bar for publishing. I have no intention of publishing or keeping anything that’s embarrassing or inappropriate. Teenagers have a hard enough time dealing with their body image and bullying and there are too many opportunities for these to mix in these situations. That, and I’m not a creep. Another pass through the remaining photos, slower this time, looking not just at the primary subject, but all around the photos. If it feels wrong, it’s gone. Delete from disk and don’t look back.

The rules of the process for dealing with a large volume of photos will change, but the process needs to be simple and definitive. The triggers to keep/delete will be different for a model shoot or other situations, but for a lot of photos, you’ll bury yourself in photos and never find the real keepers if you don’t make the effort to clean out the losers early.

My nemesis, however, is the GoPro. I used it heavily for one season, taking burst photos (10-30 at a time), which simply gave me more photos than I could handle. I never really developed a good way to differentiate and decide on “the best” of any given burst. Picking out the obvious duds or obviously inappropriate ones was pretty easy, but that still leaves many, many more that should be dealt with. Problem still unsolved.

I’ve been shooting swim and some dive meets for twelve years now and have about 17,000 photos in the collection. You can visit the galleries and decide how well my skills have developed over the years. Most are taken with the 100-400 lens because it allows me to shoot reliably from basically anywhere around the pool. A monopod is an absolute must have option too. And I always shoot with a flash to pick up facial features as well as get some good reflections off the water.

Unexpected college challenge

My son’s headed to college in about a month, and I’m realizing just how much I’m going to miss being able to discuss purely geeky things with him. My wife’s eyes will glaze over instantly when I tell her about the cool process I got working on AWS with Vagrant, Ansible, and…whatever, she stopped listening at “process” anyhow.

Darien didn’t necessarily get it, but he listened, sometimes just politely, but generally with interest, and he asks questions. And he poked around with enough things out there that he has been finding new and interesting topics too. He also asked enough questions to drive new approaches and ideas into the topic. He’s always been my geek buddy, but it’s only been the past couple of years where he’s been at a high enough level of knowledge that any topic was fair game, and spending so much time at home this past year, I expect to be able to talk with him almost any time.

My daughter doesn’t realize what she’s in for as I seek out a new outlet. I presume that I’ll be spending more time in the robotics team’s “chatter” channel on Slack too.

Steep learning curve

Switching gears from managing teams and doing fairly high level business and technology system design form many years, I’m finding myself having to get deep into many different technologies that I knew about, but didn’t actually know. This isn’t bad, per se, but it is daunting. The technology landscape for building a complex data driven system, with multi device front ends, analytics, security, and a supportable, distributable (i.e. cloud based) environment from scratch narrows my technology search down to a few million items. Different languages don’t really scare me (despite not really being up on any of them), but every language comes with a plethora of frameworks and development tools that also need to be learned. Development patterns change with each selection and the ability to make an informed decision (without a well versed team around who can call BS when appropriate) is a major challenge. Hello World! applications aren’t going to tell me whether the application will be able to distribute amongst multiple back end providers and maintain an acceptable database throughput and remain stable.

So I’m in the midst of not so much evaluating technology based on their actual capabilities, but based on the risk level each brings, assessed by the capabilities I can infer from very limited use. Some decisions are pretty easy, despite minimal experience with them. We’ll be using node.js for many of our back end elements. Why? It meets the design needs, has a reasonably comprehensive ecosystem, and I’m convinced it’s moving forward, not stagnating. I’m a believer in lightweight frameworks and that tends to be the mindset of the developer base.

What about Ruby/Rails? Not out of the question, and will probably be part of the mix, but it’s not going to be primary unless somebody shows up on the team and can knock some things out of the park quickly with it, and we can develop appropriate strategies for scaling.

Yes, there are a ton of options, but so far, it’s just little old me making these decisions, so aside from calling friends and asking them dumb questions about the tools, I’m going on gut feeling of what can produce a viable product without a short street with a dead-end.

3d Printer

Despite our desire to build one, I finally accepted the fact that Darien and I were never going to find the time, so I took a chance on the Monoprice Maker Select i3 (which is actually a Wanhao Duplicator i3 printer). It’s my first real hands-on experience with a 3d printer, so I can’t compare to other models, but it seems to work reliably and I’m learning about the printing process, which was the primary goal anyhow.

This is an entry level printer. Period. I’m not sure where the real limitations will occur, but I’m confident that they’ll be there once I know what I’m doing. It’ll probably be accuracy of higher resolution prints. So far, printing high resolution hasn’t resulted in significantly better prints, just slower ones, and in some cases much worse quality. I’ve found 3dPrinterBrain to be an invaluable source of information.

What am I going to do with a 3d printer? Robotics is one area where I’ve already started to make use of it. I’m now coaching FIRST Robotics Competition (FRC) Team 4026 and we’ve had a number of problems that were fairly easily solved with a quick design and print (OK, prints are never quick).

Some of my more interesting and useful prints so far.

The killer in this bunch as been the marking guides for the aluminum tubing. They’ve been a godsend. Saves a ton of time when trying to make accurate holes (need 4 1/4″ holes, spaced 1″ apart, set 1/2″ from the edge of the tube, starting at 1/2″ from the end). Previously doing that with clumsy tools, tape measures, calipers, a compass, and lots of cursing could take an hour for a single part. Then, any inaccuracies were multiplied by drill press sloppiness.

With these guides, you drop it on the edge, flush to the end, mark the long axis and the 1/2″ starting point, slide the guide up to that mark, continue the long axis and mark every 1″ tic mark, punch the tic marks and go drill. The whole thing can be accurately marked in 2 minutes.

So far, well worth the $350 for the printer, plus about $30/kg of material (ABS and PLA so far, PETG next). Lots of fun. Amazing to watch. And unbeatable to solve an odd problem here or there.