New tool for weekly planning: Teux Deux

I’m not sure about you, but I struggle with planning and prioritizing things. My problem is that I’m too efficient at capturing thoughts and ideas, and I’m always overwhelmed by what things I should be doing because my ‘to do’ list is way too long!

One of the productivity steps I’ve read about but had problems implementing was planning out the major things I’d like to get accomplished in the week ahead. All the techniques I tried to visualize and track this data never seemed to work for me until I remembered a piece of software I had demo’ed long ago – Teux Deux:

Teux Deux screencapture

I love the layout – perfect for visualizing the tasks allocated each day for the whole week. If you don’t finish the tasks for a day, they’re automatically moved to the next day which is helpful. Once you enter a string/task, you can re-arrange the order (or move to another day) by dragging and dropping. You can also check off the task once it’s done (shows a line drawn through the task) or click an ‘x’ at the end of the line to delete it. Unfortunately, to edit a string, you need to delete it and re-add it which is kind of stupid. Helps to read the FAQ: you can edit a string by dragging to the inpput box! But it does have an iPhone app now so you can take your list with you.

Give it a try and see if it can’t help you focus on getting more major accomplishments done each week!

Cooling Stand for Mac Book Pro from Mad Minds

I just wanted to pass along a tip to those of you with Mac Book Pros. As you well know, the bottom can get pretty hot, especially when it’s sitting in your lap! I had another cheap wedge-shaped plastic pad that I had doctored up with non-slip drawer lattice to keep it from sliding around. It actually worked great, but I ran across The Tilt from Mad Minds a while back:

The Tilt from Mad Minds

I had ordered it in mid-December and it was on backorder, but it finally arrived this week and it’s slick!  It clips on firmly to the bottom of the MBP, and it has a USB plug-in to power the fan which is remarkably capable of keeping things cool without adding too much thickness or weight to things.

I highly recommend it to anyone with a Mac Book Pro!

Rain City Burgers

I have to give a quick shout out to Rain City Burgers on the corner of 65th and Roosevelt. I stopped in there recently and had an unbelievable bacon double cheeseburger (my Yelp review). Highly recommended!

Thoughts about Startup Weekend

It’s taken me a few days to gather my thoughts about Startup Weekend (and ok, I was slightly distracted by the snowpocalypse this week).

I’m not going to give you a play-by-play because I’m not sure I could improve upon Dwight’s perfect summation (part 1, part 2, part 3) – he really captures what it was like to be there and be involved.

I had said before in my previous Startup Weekend post, I was a little nervous because I didn’t know what to expect. Some of my fears were confirmed, but I was pleasantly surprised in many other areas.

First, my overall experience was incredible. Everyone (literally everyone!) there was super nice, really excited to be there, eager to meet you, find out about you, etc. It didn’t matter who you are or what you do – people were enthusiastic talking with you. Definitely a very friendly, gregarious crowd.

Based on the raise-your-hand survey at the begining, it appeared that most of the room were first-timers which was surprising. For some reason, I expected more grizzled veterns.

One of the other things I was surprised about was the amount of abandonment by team members throughout the weekend. I heard that other teams had people leaving because they couldn’t get along or didn’t want to take part any more. Even on our own team, we lost one person the first night, and one person the second night. So strange!

As for my team, there were some really talented people on it. Our team leader and pitch’er (Eric Butler) turned out to be the guy who wrote FireSheep (Firefox extension that demonstrates HTTP session hijacking attacks) which made a big splash when he released it, so he’s famous! (well, internet famous – at least to technical people). I didn’t know this when I first talked to him about joining his team, but I was certainly impressed when I learned this.

But that basically confirmed my worst fear – being on a team with tons of über-level talent. What exactly could I contribute? Even worse, the code was being done in Ruby on Rails, something I have ZERO experience with. I spent quite a bit of time getting my own RoR setup configured and running our source code which is another post in-and-of itself. Ugh!

I contributed what I could in various other aspects, but I did feel a little marginalized. It’s clear Eric had thought about this idea quite a bit, including researching competition, sketching wireframes, mocking up icons, and figuring out how to monetize it. This being my first time, I surely didn’t want to overstep my bounds or step on any toes by trying to take on too much oversight.

Here’s a guy who has a lot invested in his project, and extremely busy writing the backend code, and seemingly did not want (or is not able time-wise) to be the project manager, but also did not want to relinquish control of the project – it was definitely an awkward situation.

I was ok being a cog-in-the-wheel the first time around though. In retrospect, it was probably a good thing that I didn’t get thrown into the deep end and being primarily responsible for the technical aspects of a project. I got a chance to see how the process worked (and how I might handle or manage the process differently) and it was a very valuable experience.  I did find out at the end that there was at least one team that didn’t have a developer though. I wonder how it might have worked out if I’d have found that out and migrated to that team? I’m sure it would have been a completely different experience!

There were some incredible teams coming out of the event – some teams I thought were well on their way to forming an actual company and making a go of it.

In the end, I really had a great time – met a lot of great people, got some extremely valuable experience that I will be applying to my next Startup Weekend:

  • I will definitely blog/photograph/tweet more. Documentation!
  • I will definitely take notes (and possibly even photos) during the pitches. I had a hard time remembering all the pitches, what they were about, who pitched, etc. 54+ pitches in an hour or so – very hard to keep track of!
  • I am definitely going to pitch next time! I don’t feel bad that I didn’t the first time around, but now that I have a better idea of what pitching is all about, it’s something I really want to do.
  • Picking the right team – pick a team that you can contribute to, and something that you feel strongly about.
  • Confirming that I really need to tighten up my technical chops in some areas that I’m lacking (especially front-end work)

My last thought: this SW was held at in Pioneer Square so I was wandering around the streets morning, noon and night. I can’t believe how far the area has fallen with regard to hustle and bustle. Granted, it was the weekend so maybe the foot traffic was less than it might be during a normal 9-to-5 weekday but Friday and Saturday night were D-E-A-DEAD! I remember back in the 90’s when it was THE place to be, and now, nothing. No one in the bars, no one walking around on the street. Nothing. How sad.

Pre-Startup Weekend Bootcamp

I had my pre-Startup Weekend bootcamp last night at the co-working facility StartPad. The premise was to get Startup Weekend participants’ laptops set up with Google AppEngine, Bootstrap, jQuery and GitHub, since those tools were likely to be in use over the weekend.

The only one of those tools I didn’t know much about was Google AppEngine (cloud-based Java/Python service), but that was primarily because I don’t know how to code in either Java or Python. Still, I set it up anyway to get the experience and see how it worked. The service itself was pretty cool, but the Mac-based software used to interface to it was a mess.. installing shit all over the place on my MacBookPro. (sigh)

An aside: I really hate installing package software because it has a tendency to install things in various places. Give me a straight source-code install every time to specific directory location. That way, I know where it was installed, what it installed and can easily remove it or update it.

Having my own servers and doing all my own sys admin, I don’t often use cloud services. Plus I don’t write in Java, Python or Ruby on Rails which is what most cloud services seem to be focused on these days. I’ve used PHPFog before and it’s a neat service. If I had something that really needed to scale, I wouldn’t hestitate to use them, or set up Amazon EC2 servers.

Anyway, the valuable part of the bootcamp was getting to know my fellow participants and being able to ask questions of the more experienced leaders of the group, like @mckoss and @kavla. I had questions like, “So everyone works on something together, who owns what?” and how the team selection process works. Getting them answered beforehand really gave me a good idea of what to expect which put me much more at ease.