What I Did at RC
Pixie Report - want big progress, hits a number of learning at my edge challenges, Absolutely hitting a number of learning edges, including: analysis paralysis (too many options), working at low gear outside the circle of life, staying open to alternatives without letting those alternatives cause flapping. Some progress, but slow. Mostly encouraging that I never hit a dead end, just a lot of "where do I best go from here?"
Pieces finally falling into place for the in-browser composer. Mostly I've been struggling with the mental model of what's going on and how do I handle the cross-cutting aspects of browser runtime resource management; things are finally clicking in the last week.
Memory Card Creator - small enough to just jump on it? +2nd wk. Not quite small enough. Again, operating in the browser as an application platform was unfamiliar enough that I was often stuck not knowing my next move.
Pairing - opportunities to let others' interest drive my learning and gain satisfaction with mutual progress. Pairing ended up being more on my stuff, and just the energy of working alongside and explaining what I did was helpful. Let's do more of that.
GT/Lepiter - seize the pairing availability. Yes. We got far enough to see Moldable Development working for the DocAssemble project.
Career Crud / Job Prep. I got help from the RC job staff in updating my resume; however, RC's companies are startup-heavy, and may not be as good for me. I got more engaged with LinkedIn, posting my "Crash Faster!" zine about Crash-Only Software.
Blogging - learn generously. I love taking notes and figuring things out, and I even have a sort-of workflow; what I find is that when I engage with And Another Player Yet to be Named blog 
, I rediscover motivation. I did a little bit of that. At the RC and Who Could Hate Jira? I also joined the RC Webring.