StackOverflow DevDays, in Pictures

The travelling tech conference arrived in Toronto last Friday.

A full day of inspiration and learning for developers, brought to you by the team behind StackOverflow.com and FogBugz. Lunch is provided so you’ll have plenty of time to hang out and meet other developers. Hope you can join us!

Here’s the guy who organized it. Contrary to appearances, I don’t think Joel Spolsky is tweeting: Update: he says:

I was checking the time, I think… we had so much on the agenda we timed everything down to the minute.

Unfortunately, I only arrived midway through the conference so I only have photos from the last two talks. It also means the only front-row seat left was behind a TV monitor on the stage - lots of awkward shots.

Read the rest of this entry »

How to run a code sprint*

*this post only offers hints

While many students this week were busy partying reading, a handful of computer science students participated in a code sprint to work on various open source project courses. This is most of us, three days of hard work later:

Up front at the whiteboard is Greg Wilson leading our post-mortem discussion about how we felt the code sprint went.

What worked

First up, the whiteboard itself. Beyond its obvious scratchpad benefits, it allowed people outside of a discussion to jump in.

Having a room full of developers and potential rooms made for good usability testing opportunities, from the “hey, got a second?” variety to the longer, structured sessions.

But most people agreed that the best part of the three days was simply all being in the same room together. For some, it was the first time connecting faces to names — in particular, four collaborators travelled from Ann Arbor, Edmonton and Waterloo to help out.

Pair programming also worked well, keeping people focused and writing sane code. Working alongside partners meant that you if you didn’t understand a line of code, you could go up to the person who wrote it and ask them. More generally, filling a room with developers meant that lots of command line tricks, clever solutions, and handy libraries got thrown around.

And what didn’t

The obvious flipside to working in the same room were the constant interruptions.

The grizzled Blake Winton (Basie’s dedicated code reviewer) stated it elegantly: he enjoyed getting interrupted to share knowledge that he accumulated over his many years. On the other hand, he hated getting interrupted to share knowledge that he accumulated over his many years.

And like all good computer science problems, there were the challenges of scale. Eating donuts and sitting on lousy chairs is fine for a few hours but not for a few days.

Some other thoughts:

• Our list of objectives could have been more explicitly defined — there wasn’t an official “scrum list” to use the nifty agile term.
• Some felt that the sprint could have used a few more veterans and alumni. The ones who were there were often spread thin.
• Aran suggested we try breakout rooms for when smaller groups need to focus.
• “Demonic child coughs.” James Leung’s advice: don’t come from out of town and stay with professors who have sick children.

Getting Things Done

Like many things in the oft-inverted world of academia, results often take a bit of a backseat to the actual learning experience. But thankfully, we got lots done. Greg, Aran, Phylis, and Mike have the details.

Doling out some thanks

In the spirit of last night’s Oscar’s, some thanks need to be handed out:

• the “adults” who managed the projects: Greg Wilson, Karen Reid, and sanity checking from Blake Winton.
• tech support / setup from Alan Rosenthal, Vlad Sekulic, and David Wolever. The network didn’t go down once!
• the students from other schools who travelled to Toronto to help out: Liz Blankenship, Heather Grant, James Leung, and Jason Whyne.

And now for some pretty pictures

X-Plane gets an inside peek into Apple HQ

X-Plane is a simulator that’s nearly as good as Microsoft’s Flight Simulator but developed with a fraction of the programmers: in fact it’s basically a one-man-show run by a guy named Austin Meyer.

So what happened when he called up Apple and asked if it would be possible to port his simulator to the iPhone? They told him that a keynote was coming up in a week and they’d love to have him finish the game before then. To help him out, they shipped him to Apple HQ in Cupertino, and set him up in an office. His story provides an intimate look into the bowels of one of the most secretive offices in the world. At times, it almost seems like a recruiting pitch:

Everyone is working harder, faster, and with more urgency than I have ever seen at any company.

The whole time, he and his sub-contractor were treated like rock stars. Some of the anecdotes are pretty intriguing.

When we need a bigger monitor to do the ARTWORK for the iPhone version of X-Plane (for example), all we would do is say the word and huge cases full of Quad-Core desktops and 30-inch monitors were rolled into our office. Why the huge cases to hold this stuff? As it turns out, we were given the SAME computers that are shipped off to Hollywood to appear in movies!

So after a week of the “most time-pressured, intensive, focused work [he had] ever done”, what did iGod think?

The Verdict: “No-Go”. The sim is fine, and Steve likes it, but it is not FAST-PACED enough for a keynote demo.

But it wasn’t all for naught: the $10 X-Plane app is currently sitting at #3 on the Top Paid app list — not bad for two weeks of work.

• Link: The story of X-Plane for iPhone (via shazow)

Update: seems like the story is down now. I guess Apple got annoyed. The Google cache is still up.