Category Archives: kaizen

Understanding my procrastination

This week’s Less Wrong Toronto rationality challenge was about procrastination: observing how, why, and when you procrastinate, and what you can do about it.

The word “procrastination” comes from the Latin roots pro (“for”) and cras (“tomorrow”). The more I think about that, the more it seems that putting things off is actually a very useful skill, despite its negative connotations. There is only so much time in the day and so many years in a life. Figuring out what makes sense to do right now, what might make sense to do later, and what doesn’t make sense to do at all–that can be really helpful. To describe how we decide what to do later, we use the word “planning.” We reserve “procrastination” for when we put things off to our detriment, when we do low-value tasks instead of high-value tasks.

The Wikipedia article on procrastination describes procrastination as “replacing high-priority actions with tasks of lower priority” (emphasis mine), but I’ve been working on not letting perceived urgency mess up my true priorities. Thinking of it in terms of value instead of priority helps me not get caught up in false urgency.

Because the procrastinating mind can be good at rationalization (“I know I should write that blog post, but dinner needs to be cooked and the blog post isn’t that important anyway”), it can be difficult to recognize procrastination unless you’re obviously avoiding something. It’s easier to look at various decisions to put off actions, figure out the reasoning behind them, and look for patterns.

I put off many ideas by adding them to my Someday/Maybe list or scheduling them for the future. I’m working on getting better at finishing projects, so I try not to get too distracted from today’s to-do list unless it’s really important. Stashing other ideas in my Someday/Maybe list means that if I get blocked on all my current tasks, I can easily find something else that I might want to work on. Structured procrastination for the win! (Procrastination explanation: Low value compared to current tasks.)

I put off various types of tasks to certain days. For example, I balance my business books and handle other paperwork every Friday. If I need to get an invoice out quickly, I’ll do that any day of the week, but having one day set aside for paperwork and all those other little things makes it easy to keep the rest of my week clear. I put off worrying, too. I allow myself a chunk of time for planning and questioning, then focus in moving in roughly that direction the rest of the week. Mornings are great for code, afternoons for calls, and evenings for writing. On either Saturday or Sunday, we do our household chores and lots of cooking. Roughly sketching out our days like this helps me batch process tasks. (Procrastination explanation: Reducing impulsiveness / interruptions.)

I put off actions depending on my energy level. When focused and excited, I code or write. When I’m more contemplative, I like drawing or reading books. When I feel uncreative, that’s the perfect time to handle paperwork or do chores. When I’m optimistic, I flesh out my vision. When I’m pessimistic, I dig into my backup plans. (Procrastination explanation: Low value or expectancy; I expect to not code well if I’m preoccupied with something else.)

I absentmindedly put off putting things away. Not all the time, but enough times that this gets in my way. I have some workarounds. For example, I switched to using a belt bag because that was an excellent if unfashionable way to not lose track of my phone and my keys. I’m still working on slowing down, having one place to put things, and minimizing stress. W- has this saying, “One hand, put away” – put things away while you’re holding them instead of going back and forth. Working on it. =) (Procrastination explanation: impulsiveness.)

I put off going to the gym with W-, reasoning that I’m pretty tired from biking upwind and uphill. I should build upper-body strength and other things not covered by biking, though. One way for me to deal with this is by bargaining with myself: if I’m not going to the gym, I have to do kettle bells or similar exercises instead of spending the time writing. Or maybe I’ll train speech recognition on my computer so that I can increase the value of that activity… (Procrastination explanation: Low value because I don’t particularly like that form of exercise; low expectancy because of salient bad experiences, even though I’ve also had very positive ones.)

I put off shopping, especially when they are so many choices. I do this because I feel overwhelmed. I deal with it by limiting my choices based on predetermined criteria and focusing on items that meet my price thresholds. For example, I buy only flat/low-heeled shoes and machine-washable clothes. I eventually buy things when sales, thrift stores, or other buying opportunities intersect with my criteria. (Procrastination explanation: Low expectancy because of the feeling of being overwhelmed; low value because I have lots of things that still work for me.)

I put off learning skills if I think the costs associated with learning outweigh the benefits I get from doing so. For example, although driving is widely acknowledged as a useful skill, I haven’t gotten around to learning it because becoming a confident driver requires several big lifestyle changes: expenses related to cars, fuel, parking, and maintenance; I would need to shift my work to somewhere that requires a car-based commute instead of one that can be reached with public transit or biking; and I would need to get used to the thought of controlling this big, heavy, potentially lethal machine. The money I save by not driving can pay for quite a few cabs during the times that I do need to get around (say, accompanying a friend post-surgery). So far, clear costs (money! no free exercise from biking!) outweigh vague benefits (possibly being able to drive W- if he needs help, being able to navigate more cities). I’ll get to it when it makes sense. Or slightly before it makes sense. (Procrastination explanation: Low value.)

I put off putting some things off. Sometimes I feel myself getting annoyed for something I have to do. I could go round and round, internally whining about it, but sometimes it’s more productive to put off the annoyance, get things done, and then channel that annoyance into making sure that I don’t have to do similar things in the future. This actually works out quite well. (Procrastination explanation: Well, this is actually a useful thing…)

There are a lot of other things I procrastinate, but since I want to actually publish this blog post at some point, this is probably enough of a sample.

I use a lot of pre-commitment to deal with procrastination. I’m also halfway decent at recognizing when procrastinating something takes more energy and emotion than just doing the thing I’m procrastinating. I’m good at discovering (or even inventing) meaning for my tasks to make them more palatable. I need to work on being more conscious, though. All these techniques are useful only when I detect that I’m procrastinating. If I want to stop absentmindedly putting something down somewhere instead of putting it away, then I need to make putting things away automatic, and I need to get better at checking impulses.

There aren’t any big ominous tasks hanging over my head that I need to un-procrastinate, but I want to get better at catching unconscious procrastination. (Which was not quite the focus of the Less Wrong blog post on beating procrastination, but I lump it together with deliberate procrastination…) I’ll be focusing on being more mindful over the next month or so. It’s difficult to track how well I’m doing with this, so I track failure instead by recording “foggy” moments. I’ll probably never get rid of it, but I can develop more automatic behaviours to catch the common cases. One of the nice things about being married is that W- can help me catch things. =) Onward!

Analyzing my London trip decisions: What worked well? What can I improve?

Update: Fixed incomplete sentence regarding Google navigation – thanks to Geoffrey Wiseman for pointing it out!

I’ve just come back from a trip to the UK for an Emacs conference. (Emacs!) While the memories are still fresh, I want to think about what worked and what can be even better next time I travel.

What worked well:

Keeping a close eye on flight fares versus visa paperwork: When the conference date firmed up, I checked the flight prices (~$1200)… and then realized that I still needed to get my visa paperwork sorted out. It took me about a week to gather all the papers, and then another three weeks to get it processed. I didn’t want to book the flight until I got the visa, but I also didn’t want to pay sky-high last-minute prices. Because I wasn’t sure that I’d be granted a visa, I kept a close eye on the flight prices throughout the period. I figured that if it got to two weeks before the trip or flight prices started trending up, I’d book the flight and then deal with the change fees in case I didn’t get the visa after all. Fortunately, I got the visa notification two weeks before the flight, and I booked my flight for ~$1000 – cheaper than it would’ve been if I’d booked it right away. It won’t always work out this neatly, but I’m glad that it did!

Couchsurfing: It was super-nice of the organizer and his wife to let me stay at their place during my trip. Not only did that make it much easier to fit the transatlantic flight into my budget, but it also meant that I got a glimpse of everyday life: buying groceries, walking around the neighbourhood, eating yummy home-cooked food and discovering Serbian tastes. That worked out much better than staying at a hotel.

Oyster card: The Oyster card was my very first purchase, and it worked out wonderfully. I had no problems navigating the London public transit system, which I used to and from the airport and around town. I could probably have loaded 20 pounds on it at the beginning instead of topping it up throughout the trip. I ran into a negative balance at one point and ended up paying the cash fare on the bus because I didn’t want to delay other people. Still, public transit = good! I returned my Oyster card for a refund when I got to Heathrow.

Withdrawing cash from the ATM: I withdrew GBP 50 from an HSBC ATM once I reached Paddington. It worked out to CAD 79.19 plus a CAD 5.00 fee, for an effective total exchange rate of 1 GBP = 1.684 CAD. This was better than the foreign exchange rates posted there, although slightly worse compared to how much it would have cost if I’d gotten my act together and either converted cash through my bank before leaving (penalty: ~$5, which was the bank withdrawal fee) or switched my account to something that doesn’t have international withdrawal fees (but that would cost me maybe $53 in forgone interest per year, and I don’t travel or withdraw enough to make up for that). So it all worked out. It was the right amount of cash to have handy, actually, although I could’ve probably gotten away with GBP 40.

Sketchnotes: I took notes during the conference and I posted them right away. People really liked the notes! I need to go back and add more details so that they’re more understandable even for people who weren’t at the event or who aren’t familiar with the topics, and that will be part of my Emacs Conf followups.

Meeting people: The Emacs conference was incredible. I’d never seen so many Emacs geeks in one place, and it was fantastic to meet all these people I’d gotten to know over IRC and elsewhere. During the rest of my trip, I met several people for coffee. I chatted with Dave, Louise, and Joanne(sp?) about travel, paperwork, comics, and drawing. John Wiegley and I brainstormed ways to make the Emacs community even awesomer. I hung out with Michael Olson while on a walking tour (see below). I didn’t get around to meeting everyone I’d wanted, but it was great meeting lots of people face to face. Such is life!

Walking: I walked to places whenever I could – an hour-long walk along Regent’s Canal from home to Camden Town, another long walk coming home from Covent Garden… Walking around in London is enjoyable because there are plenty of shops and interesting sights, and I felt safe.

Walking tour: Michael Olson suggested meeting up for one of the London Walks, so I did. It was a lot of fun hearing the guide tell stories about the buildings and the people who lived or worked in them. Walking tours might be an excellent way to observe well-polished storytellers.

Offline navigation using Google Maps: I downloaded the map of London, which was handy. Although I couldn’t search for places while offline, I could use the navigation function if I’d already set it up previously. I also used the map to verify that I was walking in the right direction. I also wrote addresses down in my notebook in case I ran out of battery or lost my phone.

Eating supermarket food: Quite a few of my meals were from supermarkets and department stores, which worked out wonderfully. One time I snagged a 99-pence chicken tikka masala meal (warmed and ready to go, marked down from 3.50) from Sainsbury Local and ate that in a nearby park. Three pigeons tried to mug me for the food, and about 30 pigeons stared at me throughout the meal. ;) Supermarket food turns out to be tasty and inexpensive. One downside is that I hadn’t realized that self-checkout lanes sometimes don’t give you exact change, and I neglected to ask the assistant for the rest of my change. Oh well.

Free museums: I spent most of Monday at the British Museum, where I got to see the Rosetta Stone and other amazing things. Neato!

Fish and chips: Yummy, crispy fish and chips. I had these with mushy peas for the first time. I could’ve probably walked around a little more and found cheaper fish and chips, but the one I settled on was very filling.

Bank holidays: My trip coincided with the long Easter weekend, which was nice because that meant people were generally relaxed and unhurried, and my hosts had plenty of time to hang out. It meant that many shops were closed, but I wasn’t there for shopping anyway.

Evernote: Evernote worked really well for saving small maps, directions, contact info, and so on.

Technical flexibility: There were some technical issues during the conference, but we managed to make things work. For example, the Mac we were using to project the Google Hangout didn’t pipe its audio out the headphone jack, so we got my laptop into the hangout and routed audio out that way. This meant that taking notes was more awkward, but it was worth it. At one point, I had to write things down on an index card (forward and backward, just in case my webcam was set to mirror!) in order to pass messages along to Steve Yegge, who might not have been monitoring the text chat in the Google Hangout. Audio feedback was a challenge, too, so we ended up typing questions in. Anyway, it all worked out! =)

Weather: I can’t claim any credit for this one, but it was great to have sunny weather throughout the trip. =)

Hat: My black Tilley winter hat was a practical choice – a wide brim to shade me from the sun, and earflaps to keep me warm. I got several compliments on it, too.

Bringing stationery for a thank-you card: It’s always nice to say thanks, and it’s even nicer to not have to raid your host’s stationery stash or write it on plain paper. ;)

Saving the next day for recovery: I kept the day after my trip free of appointments, which was nice because I didn’t have to worry about jetlag. I ended up doing productive stuff anyway, but at least that was completely optional. =)

What I can improve:

Packing: One pair of comfortable winter boots saw me through the whole trip, and my scarf was also really handy.

  • I could probably have packed more thermals, but I compensated by walking faster and the cold didn’t bother me.
  • I didn’t use the headphones or the tablet as much as I had hoped.
  • I forgot the USB cable for my phone, so I conserved power for the first few days. Then I realized I could borrow a cable from Alex, which allowed me to charge my phone and use it more for navigation. Yay!
  • I think I misplaced my tablet USB cable at the conference venue. It must have gotten tangled up with my power cord. No worries!
  • Since I didn’t have anything liquid in my suitcase on the way back, I might have been able to carry it on and so skip waiting for baggage in both Montreal and Toronto. I wasn’t sure if I could get away with it, though. Anyway, I made it through the 1-hour transit in Montreal by asking people in the security line if I could cut in ahead of them. (“I’m so sorry, but my plane is boarding now – can I please go ahead of you?” Everyone said yes.)
  • I didn’t need the foreign cash I brought (USD, EUR, and CAD), siwith the ATM withdrawal worked fine. It would probably have been good to carry one currency just in case.

Roaming: I forgot to enable roaming before flying out to London, so I had to use payphones. This made it harder to coordinate, but I managed. There was one time when I had the opportunity to meet up with Alex and someone else who had flown in for the conference. I received their e-mail while using Michael Olson’s portable hotspot, but that was two hours after they’d met up. I didn’t think of finding a payphone and calling them to see if they were still going to be in the area for a while; instead, I walked around London some more. If I had called them, I’d probably have met up with them instead of walking around as much (although that was fun too!).

Tools: Camtasia Studio crashed and wasn’t able to record my part of the keynote presentation. =( I think it had to do with missing or disabled audio devices. This is the second time this has happened to me, so I have to figure out how to reliably capture my screen. My tablet video capture stopped after a while. The livestream wasn’t working in time for the keynote. It’s a good thing that my phone captured all the audio from the keynote, so at least we have that!

Setting aside time for video editing, or finding someone who can do it: We’ve got all these recordings… now what? I’ve volunteered to spend some time slicing them up into talks and getting them out there, and I plan to spend one day a week focused on this and other Emacs goodies.

In general, blocking off time for follow-up: There’s a lot of good stuff to follow up on, and I don’t want it to get buried in the day-to-day.

Publishing presentation: Would probably have been nice to have a Dropbox folder all ready to go. And screenshots/sketches of my own so that I don’t feel weird about the licensing of other people’s images…

More productive use of plane time: I mostly watched a few movies and slept a little bit. On the plane ride to the UK, I had an empty seat beside me, so I knew I wouldn’t be interrupted by anyone who needed to use the facilities. That meant that I could break out my computer and write code. I wrote my presentation code, and it actually worked. =) On the plane ride back, I was next to two people who needed to use the facilities frequently, so I didn’t feel comfortable setting up my notebook or even writing letters. And the Air Canada in-seat entertainment system wasn’t working for me on the ~8-hour trip back. =| Maybe I should use plane time to listen to audiobooks instead?

Better camera? I probably should’ve packed a small camera instead of using my phone. It would also have been nice to remember to take pictures, especially of the conference. I’ll just have to draw from memory.

All in all, an excellent trip!

Debugging my brain: typos (write-os?) in my sketchnotes

Embarrassing mistakes are excellent ways to find and deal with bugs in your life. A couple of months ago, I wrote about phone problems, and I’m happy to report that the extended battery is working out well for me. On to the next bug!

I occasionally make small errors while sketchnoting. I get some URLs wrong, swap pictures around, or drop or switch letters. In about 200 sketchnotes, I’ve had embarrassing errors turn up in three of them – one I caught myself, and two that clients caught. Those numbers tell me that it’s not actually as bad a problem as I thought it was. Plenty of other people’s sketchnotes have spelling or grammar mistakes. Still, it would still be nice to figure out how I can reduce the risk further.

Here are some likely causes of error and what I can do about them:

  • Brain hiccup: A momentary distraction causes me to misspell a word. I usually catch these through visual inspection or by mentally sounding out the words as I draw them, and they’re easy to catch a few seconds after I make them because I’m focused on that area of the screen. However, I rarely do a full review of the sketchnote before I publish it or send it, so I may miss errors that I didn’t detect right away. Possible fix: Slow down and do a full review, possibly guided by a finger so that I make sure I cover the entire sketch instead of missing something because my gaze skips around. I can also review my past sketches to see if I can calibrate myself to a higher level of abstraction (less detail), which will give me more time to focus.
  • Forgotten layers: The lack of full review also means I sometimes forget to hide layers I’m no longer using. Same fix as the previous item – slow down and look at everything to see if it makes sense, and view the sketch as a whole as well.
  • Spots left over after erasing: These are hard to see when zoomed out, so there might not be a workaround other than reviewing everything zoomed in.
  • Working memory failure when rewriting stuff: When I redraw parts of my sketch, I need to make sure that I re-copy information correctly. Possible fix: I can avoid context-switching and reduce working memory load by using my phone or tablet as a second screen. That way, I can refer to e-mail or the previous image while drawing. I can also work with layers, drawing the new thing on top and then erasing it from the previous layer when done.
  • Order when copying or writing: This can be tricky in panels and multi-speaker talks. I need to slow down and make sure that I have the speakers in the right order so that I can attribute ideas correctly. Some panels don’t have people sit in the same order as the program, so keeping the panel information on a single layer would make it easier to rearrange. I should also double-check speaker information and make sure I get the complete set before drawing, to reduce the number of edits.

I like having another person doublecheck my sketchnotes before they go out, although it does add a bit more time. Alternatively, I could figure out how to improve my editing workflow so that making changes to published sketchnotes is easy. So far, the ones I’ve needed to tweak were in Dropbox and therefore easy to update, but I might need to update blog posts too someday.

Continuous improvement!

The Sketchnote Challenge: Those Algorithms That Govern Our Lives (Kevin Slavin)

Eva-Lotta Lamm and a great panel of sketchnote artists are running a challenge to sketch a particular talk. I managed to squeeze in a sketchnote just before today’s deadline.

20130317 Those Algorithms That Govern Our Lives - Kevin Slavin

What do I like about this sketchnote?

I captured enough to help me remember, and I had time for little doodles too. The light blue images and dark blue text look calmer than the red-black combination I used in some of my other sketchnotes. The brush size worked out fine in terms of the proportion.

I didn’t switch pen sizes or vary the size much because I wasn’t sure what was going to be important. Instead, I used simple borders to emphasize key points.

I’ve been experimenting with using a light shade to add more depth to my images. It usually takes me five minutes to go through an image. I didn’t do it here because the size and detail of the images felt right already.

Drawing with plenty of whitespace around each element allowed me to easily reposition things when I needed to rebalance the columns and reorganize the information. I’m sometimes tempted to go for more creative, overlapping layouts, but I do like the flexibility of being able to change my mind. I usually publish things shortly after drawing, so I didn’t spend a lot of time tweaking this image.

What would I like to improve?

I’ve been experimenting with different colour schemes. The first colour I drew the images in was too light, so I used GIMP to change the curve to something darker. Depending on what I want people to focus on, I’ve been trying out light text / dark images vs dark text / light images. It would be great to find a quick way of experimenting with the same image. Experimenting would be easier if I drew text and images on separate layers, but the presentation was information-dense, so I didn’t feel comfortable switching back and forth. I’ve tweaked my standard colour palette to include a darker blue like the one I used for the images here. That way, I can keep the light blue for shading, and I don’t have to adjust the colours after drawing. Next: Tweak my colour palette, and find a way to experiment more easily.

The presentation was only 30 minutes long. It turns out that the usual size I draw things at results in a one-page-per-hour sort of density, so I used only half the page. (Hooray for consistency!) It might be good to develop a dot grid that’s calibrated for half-hour talks so that I’m encouraged to draw at a larger size while preserving my usual landscape aspect ratio. Still, these columns worked out fine. Next: Try a different-sized dot grid for short talks, or get used to drawing larger.

It was pretty fast-paced, too. I don’t feel like I’ve fully captured the overall logic of the presentation. It would be nice to make this understandable for someone who hasn’t seen the presentation yet, which I think I can do with a little post-work (adding headings, explaining things in sentences instead of keywords). It feels a little disjointed at the moment, and I think I missed potentially interesting points like the one about the monoculture. The individual components are enough to remind me of what I want to remember about the talk, though. Next: Add more time for post-processing so that I can draw anything I missed the first time around.

Check out the other submissions! First set, second set: Kevin Mears (second set) has a good printout image. I like Andy Fisher’s (second set) puppeteer image, the cute robot, and the whitespace balance of the page.

Taking advantage of a bad cold

Optimist Kitteh is Optimistic!

I’m feeling under the weather. Instead of fighting it, I can embrace this feeling of fuzziness and figure out how I can make the most of it. I spent most of Thursday in bed, except for a chicken soup lunch and a congee dinner (the latter thanks to W-, who is totally wonderful). Friday was just as relaxed: chicken soup for breakfast, congee for lunch; playing video games, writing letters, and drawing.

I spent some time thinking about what gets affected when I have a bad cold, and how I can work around those. Here’s what happens:


  • I sniffle and sneeze. No avoiding that – it’s part of a definition of a cold. Having a box of tissue around helps me feel a lot more dignified. Hankies are a decent second. W- has some really soft ones.
  • I go between hot and cold. I feel hot after drinking soup. I feel cold after that effect subsides. It’s all about layers: warm bathrobe, fuzzy socks, flannel pajamas.
  • I feel tired and a little sore. Good reason to stay in bed or on the couch. No heavy lifting or vigorous exercise, although walking is probably all right. It’s also tiring to draw, but typing is somewhat okay. My skin sometimes feels a little sensitive, too. So: typing, playing video games, and some motion.
  • I can’t smell food. This is probably a good time to load up on vegetables and other things that are good for me. Also, chicken soup or congee every meal, yay!
  • I need to drink plenty of fluids. I can keep the kettle close by, and drink out of one of my favourite mugs. I like hot water. It’s simple and soothing. Oh, and if I’m sick, I get to have a glass or two of fizzy vitamin C. Redoxon’s effervescence seems to do something about calming down my nose and throat quickly, although Redoxon unfortunately has aspartame in it. Maybe it’s the placebo effect, though, as research concluded that taking vitamin C doesn’t really do much once you have a cold. (And doesn’t really do much for preventing colds, either, unless you have a stressful lifestyle.)


  • I overlook things. This is not the time for system administration. I’m allowed to do backups, but nothing major or irreversible. Good time to slow down and consciously pay more attention.
  • I find it difficult to concentrate or remember. Not a good time to read reference books or non-fiction books that I want to absorb, but good for reading fiction and playing games. Programming is tough, but simple drawing is okay.
  • I don’t feel creative. Drawing new things is hard, but practising drawing simple figures is okay. It’s a little tiring to do that, though, so I can only do so much. Clipping other people’s images for study is easier to do and that’s a good fit for my sniffles-brain, actually, although it makes me feel even more uncertain and pessimistic (see below).


  • I don’t feel awesome or productive. Time to go through all those “gray day” tasks, such as balancing my books and entering data. Also a good time for positive emotions from other sources such as comic books, I Can Has Cheezburger – Lolcats, and spending time with W-.
  • I don’t want to interact with people. I don’t want to answer e-mail or step outside the house, aside from what I need to do in order to meet commitments. (People are pretty understanding, though. Makes sense. Colds are contagious.) Anyway, if I take a while to get back to you by e-mail, this could be why.
  • I feel more uncertain and pessimistic. It seems to focus on two areas: life plans and drawing, with drawing getting the brunt of the blah-ness because I don’t feel as comfortable with it as I do with writing or coding. Deliberate practice helps me deal with that feeling.
  • This is an excellent time to make and double-check plans because of that extra rationality. Can I poke holes in my plans and patch those holes? What does my disbelieving self need to prove true in order to feel confident in something?
  • It’s also a good time to review good memories such as letters and stories, feel that tide of gratitude, and reach out to people. It gets around the “I don’t want to interact with people” bit by being something people aren’t expecting.

I’m going to have many more colds in my life. This is a state like any other state. Each moment is a potential gift. If I can figure out how to make the most of it, that’s another small fraction of my life that I can turn to good use. =)

Things I learned from the GenArtHackParty

I spent Friday evening and all of Saturday at the Generative Art Hack Party that Xavier Snelgrove organized. It was a good excuse to learn paper.js and d3js.

Here’s what I made:

  • Bouncing spline: Reminds me of that old screensaver, with a little bit of randomness thrown in.
  • Flowers: Playing around with opacity
  • Faces: Simple shapes for awesomeness
  • Kapow: I read too many comic books.
  • Pasketti: Because drawing curves like this made me think about spaghetti, but not quite.

I thought Partycles was cool. infinitedaisyworld was nicely done, too. =) Check out the rest of the submissions.

In addition to learning more about HTML5 canvas drawing with Javascript, I learned that:

If I start thinking of things as “art”, I can get stuck waiting for an interesting idea, especially if I’m in that mid-afternoon slump. If I don’t worry about coming up with a vision first and instead read the documentation or play around with functions, I can let curiosity take me to interesting places.

A room full of 20-30 geeks coding away isn’t distracting, although I still haven’t figured out how to interrupt people and ask about stuff.

Add another ~20 people and switch into party mode, and I begin to shut down socially. I don’t particularly feel like engaging in conversation, and I don’t feel like I’m completely there in conversations. It might be a decibel thing, it might be a listening thing. I wish I’d thought of sneaking downstairs for quieter conversations instead.

Xavier Snelgrove, Jen Dodd, and TinEye know how to have a great event with awesome healthy food.

After lots of social interaction, I tend to get wiped out. I slept for twelve hours the following day.

An evening and a full Saturday feels like it was enough to disrupt our home routines, which is not good news in terms of my participation in hackathons. I think I need to be more social in order to make the most of hackathons, anyway.

So, how do I want to follow up on this?

I’d like to add that d3js calendar visualization to I think it would be interesting to see heatmaps of activities.

HackLab will probably be a good way to practise being around other people when I’m coding, and the open houses on Tuesday would be good desensitization for mingling.

I’d love to learn more about Quantified Self and visualization.

Sometimes, if I start thinking of things as “possibilities,” I get stuck waiting for an interesting idea. What if I set aside one morning each week to do this kind of planning / brainstorming / looking ahead, knowing that the rest of the week can be focused on actually trying things out and making things happen, even if they’re not Super Brilliant things? If I brainstorm a list of things I can explore, then I can keep moving forward even if the creative part of my brain wants to procrastinate. I trust that if I keep exploring, curiosity will lead me to interesting places.

Good experience. Would do it again, especially if I can figure out how to hack the social parts.