Maker Faire 2015

More images in the Flickr Set.

This year was the 10th birthday of “The Greatest Show and Tell on Earth” – that Rainbow Gathering of robot makers, sculptors, hackers, welders, Burning Man attendees with kids, benders of light, food artisans, bicycle tweakers, DJs and artistic misfits.

Watches

I’m proud to be able to say I’ve taken my child to Maker Faire @ San Mateo every single year since 2006, meaning we haven’t missed a single event.

Iris

Light Sculpture

Despite the annoying aspect of the ever-growing crowds, it’s become a father-son tradition we look forward to every year, and we can’t imagine ever skipping it at this point. Every year is both “more of the same” and completely different.

Creature Quad

Certain exhibits seem almost perennial, but there are always tons of new surprises. It was especially nice to have cooler temperatures this year – low 60s meant we were able to do a full eight hours on the fairgrounds without missing a beat.

More fire-breathing giant beastie sculptures than ever before:

Robot sculpture fire

Riding Cyclecide’s collection of hacked bicycles is always our favorite part of the day. Bikes with hinges in the middle of the frame are almost impossible to ride, but you do kind of get the hang of it after a while.

Cyclecide

Same with the reverse-steering-gear bike that turns the opposite of the direction you turn the wheels. Our fave this time was the bike with off-center axles, making it feel like it’s navigating bumpy terrain even on flat ground.

Cyclecide

The “dark room” seemed better than ever, with more sophisticated interactives, plus a truly gorgeous wall-sized mixed-materials glowing sculpture reminiscent of a time tunnel receding into space.

Light Sculpture

We’ve admired the masking tape cities and gardens every year (now represening 10,000 hours of work and more than 27 miles of tape!), and for the first time this year we actually sat down for a 30-minute lesson on masking tape “origami.”

Masking Tape Art

And Miles had his first opportunity to sit at the helm of an original Apple IIe, just like the ones we used in high school in the early 80s:

Apple IIe

Totally loved the “junk” drumming of John F. King:

More images in the Flickr Set.

Notes on Organizing Digital Image Collections

I’ve spent the past few months going through and organizing my entire iPhoto -> Photos.app collection. It’s been a tedious but wonderful process. I’ve come to a few conclusions:

Snoopy mud flats

  • Everyone is sitting on tens of thousands of digital images.
  • No one can find a damn thing in that giant pile.
  • If you can’t find it five or ten years from now you may as well have not taken it in the first place.
  • The time to deal with your images is the day you shot them.
  • Delete the duds. Bad exposure. Out of focus. Not the best of the set. Delete delete delete. Delete heaps and you’ll still have more keepers than you’ll ever be able to enjoy. Don’t be a hoarder.
  • For the keepers, the key is findability.
    • Image titles. Album titles. Faces. Keywords. Doesn’t matter. Just make sure one or more keyword exists for search.
    • When adding titles, imagine a future version of yourself searching for this image.
  • Be disciplined. The longer you wait, the more daunting the task.
  • Chip away. Do it now.

Trix.py – Metadata/Converter for Hunter’s Trix

Hunter’s Trix is an incredible (and very large) collection of “matrix” recordings of some of the best Grateful Dead shows. The series is produced and mixed by Jubal Hunter Seamons and includes CD cover artwork for each volume/show.

trix1

A “matrix” involves taking a high-quality soundboard recording and merging (matrixing) it with one or more audience recordings (Auds) of the same show. The resulting matrix brings you the maximum fidelity of the soundboard source and the ambience/electricity of being in the audience at the same time.

There are more than 100 Hunter matrixes being traded as legal torrents on etree.org.

Unfortunately, there are two problems: 1) They’re all in FLAC format, instead of Apple Lossleess (ALAC). Since most people use iTunes, this means most people must go through a manual transcoding process; 2) The first 94 shows are missing embedded metadata and cover art (the cover art is beautiful). I’m obsessive about having perfect metadata and cover art in every single track in my collection, which meant manually copying and pasting metadata (including track and disc numbers, show dates and venues, track and album titles, etc.) from text files in the download directory into individual track files. It was taking 20+ minutes to process each album. So I decided to automate the process with this python script.

trix2

I had originally planned to share the completed ALAC versions of the collection back to the community, but Hunter talked me out of it. So I’m doing the next best thing here and sharing the conversion script. With everything installed and working, I was able to cut the processing time down from ~20 minutes per recording to 1 minute. The final results are added to your iTunes collection automagically.

trix3

Git it here: https://github.com/shacker/trix

Django Unit Tests Against Unmanaged Databases

A Django project I’m working on defines two databases in its config: The standard/default internal db as well as a remote legacy read-only database belonging to my organization. Models for the read-only db were generated by inspectdb, and naturally have managed = False in their Meta class, which prevents Django from attempting any form of migration on them.

Unfortunately, that also prevents the Django test runner from trying to create a schema mirror of it during test runs. But what if you want to stub out some sample data from the read-only database into a fixture that can be loaded and accessed during unit tests? You’ll need to do the following:

  • Tell Django to create the second test database locally rather than on the remote host
  • Disable any routers you have that route queries for certain models through the remote db
  • Tell Django to override the Managed = False attribute in the Meta class during the test run

Putting that all together turned out to be a bit tricky, but it’s not bad once you understand how and why you need to take these steps. Because you’ll need to override a few settings during test runs only, it makes sense to create a separate test_settings.py to keep everything together:

from project.local_settings import *
from django.test.runner import DiscoverRunner


class UnManagedModelTestRunner(DiscoverRunner):
    '''
    Test runner that automatically makes all unmanaged models in your Django
    project managed for the duration of the test run.
    Many thanks to the Caktus Group: http://bit.ly/1N8TcHW
    '''

    def setup_test_environment(self, *args, **kwargs):
        from django.db.models.loading import get_models
        self.unmanaged_models = [m for m in get_models() if not m._meta.managed]
        for m in self.unmanaged_models:
            m._meta.managed = True
        super(UnManagedModelTestRunner, self).setup_test_environment(*args, **kwargs)

    def teardown_test_environment(self, *args, **kwargs):
        super(UnManagedModelTestRunner, self).teardown_test_environment(*args, **kwargs)
        # reset unmanaged models
        for m in self.unmanaged_models:
            m._meta.managed = False

# Since we can't create a test db on the read-only host, and we
# want our test dbs created with postgres rather than the default, override
# some of the global db settings, only to be in effect when "test" is present
# in the command line arguments:

if 'test' in sys.argv or 'test_coverage' in sys.argv:  # Covers regular testing and django-coverage

    DATABASES['default']['ENGINE'] = 'django.db.backends.postgresql_psycopg2'
    DATABASES['default']['HOST'] = '127.0.0.1'
    DATABASES['default']['USER'] = 'username'
    DATABASES['default']['PASSWORD'] = 'secret'

    DATABASES['tmi']['ENGINE'] = 'django.db.backends.postgresql_psycopg2'
    DATABASES['tmi']['HOST'] = '127.0.0.1'
    DATABASES['tmi']['USER'] = 'username'
    DATABASES['tmi']['PASSWORD'] = 'secret'


# The custom routers we're using to route certain ORM queries
# to the remote host conflict with our overridden db settings.
# Set DATABASE_ROUTERS to an empty list to return to the defaults
# during the test run.

DATABASE_ROUTERS = []

# Set Django's test runner to the custom class defined above
TEST_RUNNER = 'project.test_settings.UnManagedModelTestRunner'

With that in place, you can now run your tests with:

./manage.py test --settings=project.test_settings

… leaving settings untouched during normal site operations. You can now serialize some data from your read-only host and load it as a fixture in your tests:

class DirappTests(TestCase):

    # Load test data into both dbs:
    fixtures = ['auth_group.json', 'sample_people.json']

    ...

    def test_stub_data(self):
        # Guarantees that our sample data is being loaded in the test suite
        person = Foo.objects.get(id=7000533)
        self.assertEqual(person.first_name, "Quillen")

Stranded Sea Lion, Angry Poison Oak, Ukulele Maiden

Huge day out with friends yesterday, along Coastal Trail to Alamere Falls (Pt. Reyes). Poison oak in full bloom. Recent stories about sea lion pups washing ashore, disconnected from their mothers who are out foraging for food made scarce by warming waters turned all too real when we encountered one, grumbling for a meal. Added another couple-three miles to route (for a total of 11?) as we walked up the beach looking for another access point to the trail above. Perfect weather, huge vistas, maltey barley wine enjoyed on a driftwood log after lunch. Great company, gorgeous day. Life is good.

Images in the Flickr set:

Alomere Falls - Steve & Andrew

Please Don’t Text Me

In the olden days, a typical worker’s desk had an “inbox” and an “outbox.” The “inbox” represented things that needed to be dealt with, and the “outbox” represented things that were done. When email came along, its designers wisely emulated this metaphor.

onedoesnotsimply

Your email inbox represents everything you haven’t dealt with yet, but that needs to be. While managing your email, you’re engaged in an ongoing process of deleting things you don’t need to ever see again, or archiving things that have been dealt with but need to be kept for reference. If it doesn’t need to be dealt with, it has no excuse to exist in your inbox. At the end of every day, what’s left in your inbox is the (hopefully very small) list of things you haven’t gotten around to. But you know they’ll still be there tomorrow – they won’t be lost. Your inbox is, in essence, the most important on-going to-do list you’ve got.

Text messaging apps have no such concept. When a text is new, you get an alert. But the moment you glance at it, there is no mechanism for separating it out from all of the thousands of other texts piled up in your app – it becomes part of the noise. There is no way to know what in your text app needs responding to and what does not.

Therefore, when you send me a text, I have two choices:

  1. Drop everything and respond right now so your message doesn’t get forgotten
  2. Add your message to the “mental stack” of things that need to be dealt with later.

Most of the time, when a new text rolls in, I’m not able to deal with it right now. Ipso facto, most of the time, when a new text rolls in, it’s bound to get forgotten – I’ll never see it again. Unless I add it to my mental stack, i.e. unless I incur a cognitive burden.

Case in point: A few days ago a text rolled in while I was on a long bike ride, asking for information I didn’t have access to at the time. When I arrived home six hours later, that text was the absolute last thing on my mind. It was gone, virtually forgotten. There was nothing to remind me that it ever existed. If it had been an email, the fact of it existing in my inbox would have ensured that it got the response it deserved. The sender had simply chosen the wrong tool for the job.

Because of this reality, when you send me a text, you are putting a burden on me. You are saying, “Drop what you’re doing and respond to me right now, regardless whether it’s convenient for you, lest this communication be forgotten.”

When you email me, you’re saying “Please respond to this when the timing is convenient for you.” With email, I have the luxury of being able to delay my response a day or two if needed. There is no cognitive burden – I don’t have to remember to respond. I’ll know to respond later, because your message is there in my inbox.

So in what occasions is a text more appropriate than email?

  • We’re arranging details about something that’s happening now or in a few hours
  • You just want say hello or share something simple that doesn’t demand an immediate response
  • Computer is on fire.

If you’re planning something that is not happening today, please don’t text. If you’re communicating important information, that needs real typing to work out, please don’t text. If you’re communicating information I might want to be able to refer to later, please don’t text.

I know there’s a lot of talk about how “email is dead” and “email belongs to the old,” and about how some young people actually prefer text over email. I say it’s not about youth – it’s about respecting people’s time, regardless of age (and everyone is busy!). Also: Claims about the death of email are grossly exaggerated – for me and millions of others, email is still the centerpiece of online communication.

I’m not asking you never to text me. I’m asking to ask yourself whether what you have to say rises to the level of deserving a time-stealing text.

Photo365 for 2014

At the start of 2014, I made it my New Year’s resolution to take at least one photo per day for the year. I had done the project once before, in 2011, after a suggestion by the amazing Richard Koci-Hernandez. The goal is to keep your photographic “eye” always open. That’s easy when you’re traveling or out having adventures, much more difficult through an ordinary workday, treading the same old offices and streets. But it’s amazing how things just seem to “turn up” when you have an eye out for possibilities.

It’s also a fantastic way to end up with your own “year in review” – really fun to walk back through some of the year’s best memories.

Watch the embedded slideshow here (full-screen please!) or check out the Flickr set

Taming a Mammoth Music Collection

Whether you’re talking about LPs or MP3s, people have really different ideas about what constitutes “the ultimate music collection.” For some, it means a process of endless refinement, boiling down a set of music to the purest essentials: All signal, no noise. For others, it’s an archival process (“Why have one Bix Biederbeck CD when you could have 23?”)

record-collection

It’s possible to have the best of both worlds: Maintain a large collection so you have access to everything, but create a playback system so you only end up hearing what you truly love.

I’ve been an eMusic subscriber for nearly a decade. I’ve spent a good deal of my spare time over the past four years digitizing my entire record collection, followed by my entire CD collection, followed by the large CD collections of six record-collecting friends (one of which alone was basically the Musical Library of Alexandria). All told, I’ve managed to amass a collection of ~120,000 tracks spanning ~9,100 albums, mostly in lossless format, and all with high-quality album art.

collection2

The accreted set now weighs around  2.25 terabytes  – large enough to have “special needs.” Over the past four years of building the collection, I’ve  picked up a few tips. Thought I’d share some of the most useful bits here,  in case anyone finds them helpful.

Love it or hate it, iTunes has enough traction to be considered the “default” music player for almost everyone, so I’m going on the assumption that it’s your player too. If you use something else, power to you! Everything below assumes you use iTunes 11 or 12.

This guide is split up into four major sections:

  • Remote Control (Playback techniques)
  • Miscellaneous iTunes Tips (Rare B-sides)
  • Digitization Notes
  • Building a Server

Continue reading