Skip to content

A Developer’s Guide to Startup Weekend

December 1, 2014

I’ve terribly neglected this blog for the last several, well years. So while I’m pulling myself out of my post Thanksgiving stupor, I thought I’d get out a quick article.

Last weekend I did something I’ve never done before, but will definitely do again. I participated in a startup weekend. Startup Weekend EDU Seattle, to be precise. And, I had a blast! My team worked on a SaaS idea to capture educational artifacts that occur throughout a school day, and intelligently organize those artifacts for stake holders to later recall and utilize for a variety of purposes.

When you register for a startup weekend, you identify yourself as either a developer, designer, business/marketing, or specialist — in this case an educator. Of course I signed up as a developer.

Having never participated in one of these events before, and being me, I somewhat over prepared. So, here’s some thoughts on what to do, and perhaps not do, when attending your first startup weekend as a developer.

Your Role

I ended up fulfilling the role of front end developer. You really don’t know going in what you’ll be doing. The teams are small, and organically created, so you’ll take whatever role needs doing. And, probably several. Just like, well working in a startup.

Laptop

Everyone on my team brought a laptop, and I suppose the same was true for everyone there. I can imagine someone showing up without one, and still being an asset to a team, but probably not as a developer.

My laptop started showing problems early on Saturday, and in fact crashed for good after the event on Sunday night. A failed logic board I believe. And two months after AppleCare ran out. I have a new MacBook on it’s way now, and am typing this on an iPad. So, backup your laptop! Regularly! Mine was, and my data is safe. But still, this is a final warning.

Languages and Frameworks

The team I ended up in was six people strong, with four of us being developers. Three were most comfortable with Rails. I’ve read a bit, and done some tutorials, but Ruby is not my language. Nonetheless, I quickly concurred that Rails was the way to go. It was a good decision. All of us worked well together, and there was plenty of non-Ruby work for me to do.

Whatever your strongest language or framework might be, no matter how popular, might not be what’s needed, and that’s great. You’re there to learn and have a new experience after all, right? You’re more than one skill! Something you know will end up being critical to the success of your team. You just have to trust me on this. Language is the least of your worries.

That being said, your focus will be producing, or mocking up, your team’s most viable product (MVP) by Sunday afternoon. So, you’ll be hacking together code, rather than meticulously planning everything out. I’m normally all about elegant code, but there’s no points for that here. Just make the demo work.

Software and Services

I went in with a brand new empty public repository on GitHub, with an associated working copy on my laptop. Good thing too, because when the laptop started to fail that repository was possibly going to be my lifeline. I used Cornerstone SVN client and BBEdit as my primary development stack. The other three devs in my team were using Atom, and Heroku. I had all but forgotten I even had an account with Heroku, but that came in handy. Having accounts and some familiarity with these as well as DropBox, Google Drive, and possibly OneDrive (favored by the educator in our team) might be helpful.

One of the developers in our team had Photoshop on her laptop, which she used to create icons for the mobile app. I used Keynote and Apple’s Preview to create what graphics I needed for the website. A surprisingly powerful pair, but certainly no Photoshop. I couldn’t get GIMP to run, which might have been that logic board issue. Mostly though, I just avoided graphic needs, by using icons and glyphs already in an HTML framework (I used a blog-centric version of Bootstrap for this). If we had a dedicated designer on our team, this probably would have been different.

When we weren’t together, our team communicated by text message, and the organizers pushed Twitter as a means of promoting the event, so get used to both. I’m sure other social media was being used at the event as well. If you’re not a social media person, you’ll probably not end up being in charge of that for your startup, but you’ll need to at least participate with your team.

Computer Accessories

We did most of the collaboration over services like GitHub and Heroku, but a thumb drive was essential, especially during the last minute push on Sunday afternoon. You’ll of course need to power your laptop, so bring your charging cable. At least one charging cable got lost, so you want to write your name and phone number on yours. If your laptop is used in the presentation, you’ll need the appropriate monitor adapters. Usually that means a VGA output, but I thought I heard someone mention HDMI, so bring what you have. These can get lost in the shuffle between presenters, so again write your name and number on them. I had a bunch of other stuff with me — cables, task light, a power strip — but none of it was needed.

Internet Access

We had great internet access at our venue — Seattle Public Central Library. But don’t count on this. Be prepared to do what you can without the internet. I made sure I downloaded some docs and cheat sheets I normally just check online. Storing them as PDFs in iBook on my phone worked well. Most laptops can act as a wireless hub for collaborating, and I suspect some teams in our weekend were doing just that.

Paper and Pens

I had several different pens along, and a 9×12 spiral bound sketch pad. I really only used about two 0.5 tip gel pens for sketching designs and taking notes. The sketch pad came in very handy, and a couple of my team members borrowed it occasionally. I like the 9×12 size due to my background in graphic design. Really, a standard letter sized pad would have worked as well.

Office Supplies

I also had a small assortment of office supplies in my bag. My team members are only finding this out reading this now. None of it was needed, and just contributed extra weight to my bag. The organizers supplied big 20×30 poster pads for brainstorming, sharpie markers, and more post-it notes than I’ve seen in years. Every white board I saw had at least one dry erase pen available. Tape was supplied when needed. So again, nothing I brought was needed. Save yourself the back strain, and leave it all at home.

Clothing

Dress comfortably. Casual Friday comfortably. We spent our days sitting around large tables, working with laptops, pens, and papers. During presentations we were sitting in a movie theater-like forum. No one is expecting suit and tie, but dress for office work.

Sleep

The venue we were in closed down at 11:00 PM, and opened at 9:00 AM. So we did have some fixed start and end times for the days. I ended up doing a bit of work on my own for an hour or so before and after each day. And at least one of our team had a very short Saturday night. But pulling all-nighters was absolutely not necessary. In fact, I’d guess they’d end up being detrimental. Get your sleep! Go in being as rested as possible (many complete a full day’s work before arriving on Friday), and try to stay rested all weekend. You’ll do your best work that way.

Food

We were well fed, there was always enough, and it was always tasty. Coffee was available all day, but bottled water and soda mysteriously vanished at the end of each meal. If you’re like me and don’t drink coffee, but like having something to drink around, grab an extra water with each meal to keep with you. One of the sponsors was KIND, so the ubiquitous snacks was their bars. The selection was limited, and while I like KIND granola, I’m not a huge peanut butter fan as an ingredient. So I chose to forego the peanut butter flavored KIND bars. Luckily, I had along these Trader Joes green tea mints I’m addicted to. If you have something similar you’re always popping in your mouth, bring it along. But either way, you won’t starve.

I have no dietary restrictions, but I did notice there was always a vegetarian option. Perhaps this was just due to being in Seattle. If you have any restrictions beyond this, I’d suggest contacting the organizers with your concerns, and see what you’ll need to bring with you.

Participants

Don’t give a moments concern to who you’ll be working with, or whether you’ll be accepted on a team. Everyone was fantastic. I’m a people person. But like everyone, I know there are some personality types I don’t favor. It’s 54 hours. You can get along with anyone for 54 hours. Besides, everyone there is in the same position. Few if any of them know anyone else, and they all came to get the job done. Everyone found a team, every team could probably have used more participants. Whatever unique set of skills you have, there’s a team that can use them. And you might just find or validate a skill you haven’t thought about in quite a while.

Judges, Coaches and Organizers

All of the people who went into making the weekend happen were amazing. Before I went, I had read somewhere to read up on the judges. That wasn’t really necessary. But, I did review the names, photos, and bios of all involved, provided on the event’s website. This helped me keep everyone’s name straight, and to feel a bit more connected while I was there.

Registering

I watched the registration page on EventBrite for several weeks before taking the leap. This event at least filled slowly at first, and then filled up very quickly nearer to the start date. I talked to one participant who had to do some wheeling and dealing (he didn’t explain what) to get in at the last minute. If you’re interested, register now! You won’t regret the decision, and it will fill up.

Lodging

I live about an hour by bus from the venue, and I don’t know how far by car during rush hour. So, I chose to get a hotel room within walking distance of the venue for Friday and Saturday night. That was an expensive choice, and one I probably wouldn’t make again. Taking the bus would have been sufficient, and I could have done on the bus, any of the work I did in my hotel room.

Take the Leap!

My experience at this Startup Weekend was awesome, and I can’t wait to do this again. I don’t remember where I heard of this opportunity, possibly a LinkedIn group, or Seattle Tech Startup’s mailing list. I just don’t know. But I’ll definitely be keeping my eye out for similar happenings. If you’ve read this far through, I strongly suggest you do as well.

Hopefully, this post was in some way helpful. If you have any questions or addition thoughts, please leave them in the comments.

Advertisements
No comments yet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: