The No brown M&M’s rule

Jan 10 2012 Tags: , , ,

There once was a band, let’s call them Van Halen, who had a very long and complex contract for venues. Partly because they were famous and venues would do anything to get them, partly because people could literally die.

Van Halen performs their song "Jump"...

Image via Wikipedia

The contract was full of useful things like “The floor should support such and such weight” and “We need power outlets there and there and there [or our guitars won't work and you'll have a shitty show]”

In the middle of nowhere was a demand for a bowl of M&M’s backstage, without any brown pieces.

An outlandish request, by flamboyant rockstars stretching their decadence? Not really, just a very good way to make sure the contract was followed to the letter and, you know, they’d survive the show. Find a brown piece – go check over the whole production. You will find something wrong.

With the current startup climate developers are the modern rockstars. We may not get all the groupies and we may be quite well behaved for the most part – but it’s time we started making fun outlandish requests don’t you think?

Designers are usually seen as the extravagant bit of the startup world, getting all the cool toys, working from rooms filled with inspiration and mojo … developers concern themselves much less with these things – give us a good set of monitors, free reign on our computer, some peace and quiet and we’ll be happy.

But when there are so many opportunities out there, you need a brown M&M so you don’t end up wasting even a day at a company that doesn’t quite live up to expectations.

For me, the brown M&M is version control.

If a company isn’t using git or mercurial, I can be pretty certain there will be other problems as well. Everything from a shoddy codebase, to expecting my physical presence before my brain has had a chance to boot in the morning.

Usually the use of old-ish tools also correlates with a corporate feel to the company, which goes directly against my rule of only working with [small] startups. Plus it usually means I won’t be given freedom in choosing the best technology stack for the job, but will have something mandated from above.

I could probably go on, but you can imagine the rest. Use of SVN or, god forbid, nothing, is a deal breaker for me and it’s the symptom I can discover very early in the process … haven’t gone so far as putting it in the contract yet.

Do you use a brown M&M technique to assess potential clients?

Enhanced by Zemanta

Related Posts

---
Need a freelance developer? Email me!

You should follow me on twitter
 Subscribe to RSS

2 responses so far

  • Guest

    what’s wrong with svn?

  • http://swizec.com Swizec

    There’s nothing in particular wrong with SVN, just that it’s a bit difficult to work with. I enjoy using branches and such things comfortably, I like it when merging things many people have worked on just works magically.

    It’s not that SVN is bad, it’s that newer tools are so much better that a company having a policy of using SVN is sending me a signal that they don’t care about how easy it is for me to do my job, they care about dotting all the i’s, crossing all the t’s.

    Some people like those kinds of companies, I don’t.

« Collatz, Haskell and Memoization Minimum substring cover problem »