What Brown M&M's Taught Me About Software

17 January 2022 about a 4 minute read

I wrote this originally in 2013, and it’s been hosted on the Pivotal Labs, then Pivotal Software, and now VMware Tanzu blog ever since. But I wanted to keep a copy of it around. So here you go, with some light editing.

I had no clue how we were going to afford Branford Marsalis.

I’m not sure who was the instigator, but there was consensus. The Contemporary Concerts team wanted Athens, Georgia, home to an R.E.M.- and/or NCAA-Division-I-football-crazed University of Georgia campus, to host the Sting side-man and New Orleans Jazz scion to perform. I had been on the Concerts team since I was a freshman and was wrapping up my leadership year. A Branford show was a good “last show”: someone famous, interesting, and diverse.

The booking agent had just quoted a larger fee than expected. I had not negotiated the finances of a show before. This skill was in the job description but was rarely exercised. Students’ wallets only open so far. This wasn’t going to work. I was stumped.

This all came rushing back recently when Google announced that their traditional methods of recruiting and interviewing were not predictive of new college graduates’ success. They see the academic computer science environment as being very different than the corporate software environment. This was not much of a surprise to me. Submitting a class project is not the same as shipping production code. The job of a software engineer is to design, develop, and ship while working on project teams with other people, high stress, and big consequences.

Said another way, there the real world is not in a computer lab.

But my entire college career was not just in the computer labs on UGA’s South Campus. I was one of the few geeks who ventured to the middle of campus and got involved with the University Union. I “worked” with mostly North Campus majors – Journalism, English, Drama, and Art – at the Tate Student Center, booking movies, concerts, and lectures on campus. At the time, there were very few terminals, algorithms, or compilers around.

Computers were starting to proliferate around campus – I spent plenty of time teaching MS Word shortcuts, recovering deleted files, and solving PC LOAD LETTERs. But aside from one concert where I was able to re-program Dee-Lite’s lighting system – I was the only person who could count in binary and knew how to flip some barely-accessible dip switches – my CS knowledge did not get much use around the Tate Center.

I started as a freshman moving speakers and taking tickets. I worked my way up the ranks, finding artists on tour, working security, and buying the obscure things that were buried on contract riders. By my last year I was managing the sound and light crew and finding runners (who had approval to drive from the University motor pool) to pick up food for 40 people so we ate before show time.

There are so many similarities between producing a concert and shipping software. Each is a large project that involves a lot of moving parts: complex dependent subsystems, opaque politics, resource budgets, and vocal customers. I spent time coordinating multiple service vendors, student teams, and a musical artist. I managed budgets, ran marketing campaigns, and represented student interests to the school administration. I learned to be ready for anything – to stop, assess and find simple, effective solutions that achieve some manner of consensus.

I essentially double majored in Computer Science and Project Execution. My “classes” at the University Union provided a lot of practical experience that gave me a leg up that first day after graduation. I was ready when my project was canceled and we had to figure out how to document everything and close it down. I was unsurprised when I was asked to be on a plane in 4 hours to courier hardware to a business partner in Tokyo. I adapted each time I was laid off with little (or poor) explanation.

So what’s the big deal about a little negotiation? With no cards to play with Branford’s agent, I went for honest.

“I’m not sure we can afford this show after all. Our venue only seats 800 and at the ticket price we’d charge, I’d have a student revolt. Can you come down on the fee at all? Is there another way to make this happen? The team really wants some jazz on campus.” It was worth a shot – you don’t get answers if you don’t ask questions.

“Hang on…can we move to Saturday? That gives the guys a day off after your show and that means we can do two sets for you at the same price.”

I checked our schedule. The venue was open on the newly proposed day. It moved to a weekend which meant a nearly certain sell-out. And at half the ticket price with double the attendance. Everybody wins.

Then I responded, “That totally works. FedEx me the contract.”

Today I’d just say “Ship it!”

This article is tagged with software development, history, and personal.