Friday, November 6, 2009

Business of Software 2009 Cheat Sheet: Pecha Kucha

Water Taxi from West SeattleI had a little trouble tracking down some of the Pecha Kucha speakers. If you happen to have a good link to share, send it along via comment or email. See you in San Francisco!

JD Brennan

Twitter: @jazzdev

Mark Stephens
Blog: http://pdf.jpedal.org/java-pdf-blog/

Glen Lipka
Twitter: @glenlipka
Blog: http://commadot.com/

Daniel Kuperman
Blog: http://effectivemarketer.com/

Jurgen Appelo
Twitter: @jurgenappelo
Blog: http://www.noop.nl

Adam Ruth
Twitter: @AdamRuth
Blog: http://blog.brisworks.com/

Dave O’Flynn
Twitter: @daveoflynn

Alex Papadimoulis
Twitter: @TheDailyWTF
Blog: http://thedailywtf.com/Authors/Alex_Papadimoulis.aspx

Monday, November 2, 2009

Business of Software 2009 Cheat Sheet: Day 2

The Back of Pike Place MarketHere is your homework assignment to prepare for the second day of the Business of Software Conference. That would be Tuesday November 10th.

If you discover that I'm missing a twitter feed or cool video, let me know. Otherwise, I'll see you in San Francisco.

Ryan Carson

Twitter: @RyanCarson
Blog: http://carsonified.com/blog/author/ryan-carson/
Blog: http://ryancarson.com/
Video (How to Build a Web Startup): http://www.subhub.com/articles/Ryan_Carson_build_a_web_start_up

Paul Kenny
Blog: http://www.oceanlearning.co.uk/forum/
Video (Sales: it's in You): http://oceanlearning.co.uk/index.php?MenuID=317-317-317

Chris Capossela
Audio Interview: http://iinnovate.blogspot.com/2009/06/chris-capossela-senior-vp-of-microsoft.html

The Cranky Product Manager*
Twitter: @CrankyPM
Blog: http://crankypm.com/
Audio Interview: http://www.productmanagementpulse.com/cranky-product-management

Neil Davidson*
Twitter: @NeilDavidson
Blog: http://www.neildavidson.com

Kathy Sierra
Twitter: @KathySierra
Blog: http://headrush.typepad.com/
Wikipedia: http://en.wikipedia.org/wiki/Kathy_Sierra
Audio Interview: http://web20show.com/episodes/web20show-ep43-kathy_sierra

Jennifer Aaker
Twitter: @Aaker
Home Page: http://faculty-gsb.stanford.edu/aaker/index.html
Video (Authenticity): http://vimeo.com/4803475?pg=transcoded_embed&sec=4803475
Audio (The Psychology of Giving): http://sic.conversationsnetwork.org/shows/detail3854.html

*The Cranky Product Manager is sick! Neil Davidson will be speaking in her place. Get well Cranky!

Thursday, October 29, 2009

Business of Software 2009 Cheat Sheet: Day 1

Joel and Mr. DNAI'm counting the days to the Business of Software Conference. There seem to be ten of them, but I'm too bored to double check. Instead of counting again, I decided to do a little research about the speakers at BoS2009 (and yes, the twitter hash tag will be #BoS2009).

Why not share what I learned? Below you can find some interesting links for the speakers on day one: blogs, videos, interviews, and Wikipedia entries. I even found their twitter handles for you, where possible. You might find the Business of Software Schedule and the conference program handy too.

If you find any errors, or more interesting links, please comment below. Also, if you happen to want to sell your slot in Joel's (sold out) Startup Workshop, let me know! At the very least, send your notes to me.

Geoffrey Moore
Blog http://geoffmoore.blogs.com/
Wikipedia http://en.wikipedia.org/wiki/Geoffrey_Moore
Videos http://ecorner.stanford.edu/authorMaterialInfo.html?author=169

Paul Graham
Blog (essays): http://www.paulgraham.com/
Wikipedia: http://en.wikipedia.org/wiki/Paul_Graham
Video: http://omnisio.com/startupschool08/paul-graham-at-startup-school-08

Heidi Roizen
Blog: http://www.heidi.roizen.com/
Wikipedia: http://en.wikipedia.org/wiki/Heidi_Roizen
Audio interview: http://www.freshdialogues.com/2008/12/23/heidi-roizen-vc-tips-for-entrepreneurs/

Dharmesh Shah
Twitter: @Dharmesh
Blog: http://onstartups.com/
Stack Exchange: http://answers.onstartups.com/
Video: http://blog.businessofsoftware.org/2008/11/dharmesh-shah-on-insights-from-and-around-mit.html

Mat Clayton
Twitter: @matclayton
Blog: http://www.matclayton.com/
CrunchBase profile: http://www.crunchbase.com/person/mat-clayton

Don Norman
Wikipedia: http://en.wikipedia.org/wiki/Don_Norman
Webpage: http://www.jnd.org/
Video: http://www.youtube.com/watch?v=wQmwEjL6K1U

Wednesday, October 14, 2009

StackOverflow DevDays Austin 2009

I volunteered at the StackOverflow DevDays Austin conference all day today. It was a blast, nerd overload. believe it or not, this was my first conference in my field. Previously I've only ended up at the conferences for other industries: the beer industry, the science museum industry, the restaurant industry.

The highlight of my day was talking to Joel and Michael, the founders of Fog Creek Software, and rock stars in the programming industry. Michael was very gracious, especially considering that it took me a second to realize he was THE Fog Creek Michael. Off with my head! We talked about Windsurfing and scuba and swimming with Whale Sharks. Scuba lessons are definitely moved up on my to-do list.

We also discussed programmers who resist taking their vacation. For some reason I'm fascinated by the concept of hoarding vacation. I've know a few engineers that do it, and some of them actually seem to feel guilty about using their vacation time. Michael seemed to be in my camp: everyone should get away from work occasionally and enjoy the other aspects of life.

I also asked Michael a bit about the Business of Software Conference. Michael 90% convinced me to buy a ticket, especially with the Startup BootCamp. The remaining 10% of resistance comes from the steep price. Nearly $2000 for the conference, plus $750 for a hotel, plus air fare. If it was $1000? I'd be all over that. I'm not sure how I might better spend $3000 towards the goal of becoming some sort of software entrepreneur, but then again, $3000 represents a lot of camera or windsurfing equipment. It also represents months of runway.

So, I'll have to think about that BoSC thing. Maybe I can find someone (or several someones) to split a hotel room with. That's what I did at the Great American Beer Festival, and it worked fine. Any other cheapskate boot-strappers out there? Let's combine our forces.

Chatting with Joel was a different story. I was worried that I would say something ridiculous to someone who was basically (through Fog Creek, the Joel on Software Blog, and the StackOverflow Podcast) a hero of mine. But we had a nice little chat, and I don't think I said anything too strange or incoherent. At least I improved over when Neal Stephenson signed my copy of Anathem: "I really enjoy your writing, blah blah blah." I need to find a book on how to talk to celebrities; I'm such a dork.

By the way, has anyone else noticed that Joel has become some sort of software magnate? He is associated with all sorts of interesting ventures: StackOverflow and its sister sites, StackExchange, the Make Better Software Training Series, StackOverflow DevDays, and the Business of Software Conference. Most of these look like gargantuan projects. Joel either must have mastered delegation, or he is utterly insane. Maybe Joel is the Wizard and Michael is the man behind the curtain. Maybe he is a more relaxed clone of Steve Jobs. I don't know, but Joel and Michael make me feel lazy by comparison.

I also got to chat a bit with Ryan Carson of Carsonified, the organizer of the event. Really nice guy, and a real get-your-hands-dirty sort of leader. He was out there helping to hand out sandwiches when the developer lunch mob took the caterers by surprise. Who doesn't admire that? I love working with people who contribute at every level, who remain gracious under pressure.

Grass Island BleachersOh, I think there were a few technical presentations at DevDays too. Actually, now that I look at the schedule, there were a lot of presentations. Eight presentations, three breaks. I didn't catch all of them since I was volunteering, and also because I was chatting with the various cool folks hanging around the lobby.

The presentations I did see were pretty darn good. Maybe in one or two I would have enjoyed seeing more code, and more demonstrations of the code. But overall the presentations gave a nice taste of each of the technologies. I wouldn't say that I'm ready to go make an app in a new technology, but at least I have a better idea of the big picture, and how some of the underlying code works. I only wish there was some central page to download the example code from so I could review it after the fact.

Perhaps my favorite presentation was from Jason Cohen of Smartbear Software. He fired off a nice speech concerning an intersection of humanity and technology: code reviews. I'm a big fan of code reviews as part of the development and team-building process. He had some cool data on the subject to justify the practice and provide some guidance on best practices. Imagine that: data influencing the development process!

Anyhow, Jason's presentation was a lot of fun. He also had a booth at the Austin show. They handed out lots of free books containing his wisdom on code reviews. I think you can order them free from Smartbear's website, a nice price. I got to talk to Jason a bit too, a really nice guy. He's quite passionate about software development, which makes me happy.

After the conference, the attendees broke into groups by interest: those going home, and those going out to eat together. I joined an intrepid group of developers for Mexican food, margaritas, and developer nerd talk.

Overall, I really enjoyed the DevDays Austin conference. It was inspiring to see so many folks doing great things with software, getting their hands dirty. In some ways, I was reminded of Maker Faire, which is always a good thing. I really hope to be back at DevDays Austin next year. In the mean time, I'll be at DevDays Seattle next week. See you there.

*Edited for clarity and punctuation 29 October 2009.

Saturday, November 15, 2008

Y Strap: First Impressions

Y Strap InstalledThe Problem

One huge difference between SLR and point and shoot cameras is that you can't just store the SLR in your jeans pocket. If you want to carry a SLR around ready to shoot, you'll want a strap of some sort.

The neck strap that arrived with my Canon 40D dSLR camera drives me bonkers. It's ugly, to start, with lots of colorful branding calling attention to the camera. It gets twisted up, it blocks the viewfinder when I try to take photos, it makes my neck sore, and it makes me sweat on hot days. In some ways, a simple rope might be better.

If I actually wear the strap, it bounces and smacks me in the chest while I walk. Sometimes the bounces activate buttons on the camera. It protects my camera from drops, but not from smacking tables when I lean forward. It does prevent the camera from hitting the ground, but so would gluing the camera to my hand.

The R-Strap

I've been searching for a replacement strap ever since getting the camera. I strongly considered getting a Black Rapid R-Strap. Instead of going around the neck, the R-Strap goes over a shoulder and across the chest. The camera clips to the strap via a threaded bracket screwed into the tripod socket. It sounded great until Scott Bourne published his Black Rapid RS-2 review on TWIP.

Scott had such a bad experience with his RS-2 that he intentionally destroyed it. Scott had two incidents where the strap malfunctioned and dropped (or nearly dropped) a Nikon D700. In one case, the clasp holding the strap together accidentally opened. The other time, the camera actually fell off the clip. He felt that the strap was so dangerous that he destroyed it to prevent further mishaps. I immediately scratched the Black Rapid from my list.

The Y Strap

I learned about the Y Strap at my Austin flickr meetup. An attendee uses the strap on his tiny Leica M8. Like the Black Rapid, it's meant to be worn over the shoulder and across the chest. Unlike the Black Rapid straps, which monopolizes the tripod mount, the Y Strap attaches to one of the normal strap mount points on the camera.Shooting with the Y Strap (1)

The Y Strap is handmade by Stephen M. Schaub. It cost $25 + shipping at the time of this review.

The Construction

The Y Strap is very simple: there are four parts. There is a loop of nylon webbing, a slide for adjusting where the camera hangs, and two key rings. One large key ring is attached to the webbing, the other is shipped loose. The optional smaller ring can be used as an adapter for certain cameras, like my 40D (see photos).

The camera attaches on one side to the key ring -- the maker suggests attaching the camera on the same side you wear it. The strap goes over the shoulder and across the chest. When you raise the camera to take a photo, the key ring slides up the strap.

Unlike the R-Strap, the Y Strap can't become unbuckled. There are no fasteners holding the strap together, just an adjustment slide. In the unlikely event the slide were to fail, the camera won't fall. The ends of the strap fed through the slide are sewn together so that the nylon makes a continuous loop even without it.

The point where the two ends of the strap are sewn together is quite clever. Others might just overlap the ends and sew, rivet, or buckle them together. Instead, the ends are stitched together a few inches shy of the ends, and the loose ends are sandwiched into the stitching, forming a tiny "Y" shaped tail (see the photos). This construction means that there are no exposed rough ends to fray or irritate your skin.

Do it Yourself?

Wearing the Y Strap (1)The beauty of the Y Strap comes from the simplicity. There are no complicated moving parts. There aren't even any markings except for a hand-written serial number hidden inside the "Y" where the ends are sewn together.

Not everyone likes simplicity though. They point out -- correctly -- that most anyone could probably make an approximation of the Y Strap for much less than $25. You can find plans out on the internet for DIY straps. Most of them seem to imitate the R-Strap.

I'm okay with paying for labor, craftsmanship, and design though. Considering the thorough stitching holding the strap together, I'm surprised it's worth Stephen's time to sell these at $25 -- around half the price of the Black Rapid straps. The materials seem good too. The strap has a pleasantly soft and smooth texture. It's not the rough nylon strapping that you might use to lash a kayak to your car.

If you don't care about the details and just want something better than a normal neck strap, the DIY option will probably work fine. Just be careful to choose a design and materials that won't drop your camera on the pavement.

Possible Issues

My one reservation about the Y Strap was the reliance on key chain rings. I've never heard of a normal key ring failing, but it felt weird hanging an expensive SLR off of one. Incidentally, most of the reviews of the Y Strap are from users of the Leica cameras, not large SLRs. I'll be monitoring the condition of the rings closely.

Stitching DetailI haven't spent much time using the Y Strap in the field, but my initial impressions are good. If the strap length is adjusted correctly, the camera doesn't move too much when walking.

With shorter lenses, like my 50mm f1.8, the camera tends to prefer resting with it's back against my side instead of, say, the back facing forward. This has resulted in accidental button presses. Since my neck strap had the same button issue, I won't call it a deal killer.

Longer lenses seem to do fine pointed backwards along my side. More field use will tell if walking around will cause zoom lenses like my 20-135mm to telescope out.

The key ring slides smoothly up the strap, but the strap still shifts some. Since there is no padding on the Y Strap, this isn't too big of a deal. The little tail of excess strap material does work lower and lower as the strap rotates. Field use should reveal if this is problematic.

The Advantages

Just to quickly sum up, here are my initial thoughts on why you might want a Y strap:
  • Simplicity & elegance. The Y Strap doesn't attract attention (unless, maybe, you get it in red) or look goofy
  • It doesn't put pressure on the neck
  • It makes the camera less conspicuous
  • It keeps the camera near your hands
  • The camera bounces less
  • It interferes with camera operations less
  • It supports craftsmanship
I'll give more impressions later when I've actually had time to live with the strap.

Friday, October 17, 2008

The Joel on Software MBA: Peopleware

SunfishNot long after I graduated from college, I stumbled across a book which explained exactly why my employer's quarterly performance reviews felt so frustrating and useless. The authors of Abolishing Performance Appraisals: Why They Backfire and What to Do Instead went to great length to demonstrate that performance reviews were worse than useless.

When I told my supervisor about my discovery, her reaction surprised me. Rather than being interested in the book or the findings, she was totally ambivalent. If anything, she seemed to believe more strongly in the value of performance reviews. The reviews made sense to her. It didn't matter that there was research and data indicating otherwise.

I suspect that Peopleware: Productive Projects and Teams* falls into a similar category: books big companies are immune to. Having read Peopleware for my virtual Joel on Software MBA, I'm confident that the book's ideas would work great. I'm sure Joel Spolsky and Jeff Atwood agree -- they advise managers** to staple Peopleware to their face.

Like Abolishing Performance Appraisals, Peopleware resonates with me, but doesn't mesh well with the status quo. This sort of book would interest and inspire the engineers, but -- at large corporations -- ultimately let them down: most managers couldn't implement the suggestions if they wanted to.

For instance, about 58 of the 174 pages concern the work environment. If you work in the typical large office, this third of the book will explain how you couldn't design worse conditions for productivity. Cubicles? Noise? Interruptions? You might as well have your developers code from the local Jiffy Lube. Think of the money you'll save on office space and free Folgers coffee!

Peopleware explains why Joel Spolsky went to such great lengths to give his developers Bionic Offices, complete with windows and closing doors. Good luck convincing your typical corporation to give their engineers offices with windows. They'll have all sorts of excuses explaining why offices are a perk for management, cost too much, or don't allow for proper teamwork.

Aside from environmental issues, Peopleware addresses how to motivate developers, hire the best people, retain them, build awesome teams, and fight counter-productive bureaucracy. In other words, it's more about the engineers (and sociology) and less about technology.

This might seem like an indirect approach to productivity. It doesn't involve bossing people around, demanding long hours, or hiring consultants. You won't find justifications for treating your engineers like factory workers, buying fancy tools, or flying to exotic locations. Instead, it advocates making engineers happy and simply making productivity possible. Psychology and sociology do the rest of the work.

Unless you work at a very progressive company, Peopleware will have you constantly fighting bureaucracy, trying to fix the office environment, and struggling to make time so you can have conversations with your team. Worse, your peers probably won't understand or appreciate what you are trying to do.

Ultimately, you may find it easier become an entrepreneur and start your own people-friendly and productivity-friendly company. But maybe that's the point.

* I'm reviewing the first edition of the book, but there is a second edition of Peopleware: Productive Projects and Teams (Second Edition) available as well. You can help me and my publisher by purchasing from these links. In association with Amazon.
** Peopleware concerns the field of software development, although I believe it applies equally to other engineering fields. It probably applies to just about any intellectual and creative effort, especially those requiring teamwork.