RSS
 

Just closed more funding? My condolences.

02 Oct

When a popular company announces a new round of funding, the Hacker News comment threads are usually overwhelmingly congratulatory. This attitude is horribly misguided. In my eyes, announcing post-seed funding is a BAD thing, and should be close to a PR disaster. The HN threads should be full of condolences. Here’s why.

The company hasn’t figured out how to pay its bills

At the end of the day, a company exists to make money. Every round of funding (past, maybe, a seed round) is an admission that you still haven’t figured out a business model that will keep the damn lights on. Every startup should want each round of funding to be its last.

The founders have ceded control

Companies in very strong positions are sometimes able to take funding without losing much control of the company, but this is rare. In general, founders are turning over substantial control to professional gamblers with horrible succes rates. A VC will never love your company like you do; he’s there only to get paid. This will forever taint your relationship.

Part of the company was sold prematurely

People seem to forget that “getting funded” really means “selling part of the store”. If you think your company is going to be worth more in the future, why are you selling part of it now?

Here’s an announcement I’d love to congratulate: “we’ve recently reached profitability and know we can keep the lights on. We think we can make even more money in the future, so we’re going to hang on to as much precious equity as we can. Offers for outside funding are flattering but unnecessary.”

 
No Comments

Posted in general

 

Don’t get blocked

26 Sep

Every day at our stand-up, each person shares what they did the day before, what they plan to do today, and, critically, whether or not they’re blocked.

Blocked is a crappy place to be. It means you’re trying to get something done but can’t. Current velocity: zero.

I’ve noticed something about programmers I admire: they’re extremely good at not getting blocked.

Some time ago I spent three days trying to get a feature working. I was blocked, and bad. Finally, I took a break and went to work on something else. The next day at standup, a colleague mentioned implementing that same feature, and then then going on to do two more tasks with the other half of his day. Incredulous, I asked him how he solved the problem I’d run into. He happily admitted he hadn’t. He’d run into that problem, spent a half hour on it, and then changed direction.

Me: got blocked, pounded on the barrier. Great programmer: got blocked, tried something else that worked and moved on.

Like most programmers, I have an strong desire to solve problems. Put some broken code in front of me and I’ll wrestle with it ’til it works. There’s lots to do but I’ve got to start by fixing this problem.

The best programmers I know have a different mantra: don’t get blocked. They’re focused on moving things forward, not getting bogged down making everything perfect. They’ll duck and weave, leaping over obstacles or tunneling beneath them. They like problems too, but they like something else even more: shipping.

Don’t get blocked.

 
No Comments

Posted in coding

 

Programmer Resumes are Deprecated

13 Jun

First, some exciting news: after a thorough (but enjoyable!) interview process, I’ve accepted a position at thoughtbot in Boston and will begin in a few weeks. I can’t wait to get started.

The interviews themselves will make great fodder for future posts, but I realized a startling fact the other day: I never once sent anyone at thoughtbot a resume.

Moreover, I was never asked about schools, degrees, nor much about my past experience. My “resume” took the form of links to this blog, some open source contributions, and access to a couple private github repos of Rails apps I’d built.

This experience confirms an idea that I’m glad to see gaining ground lately: resumes are deprecated. Code is king. Oh, and connections help a lot too.

A year ago I wrote that it was possible to land a Rails job with no experience, provided you had a portfolio application, some code on Github, and attended Ruby meetups to network. Some people were skeptical, but it was exactly those things that got me my first Rails job. Now, years later, the same set of things got me in the door at thoughtbot: code, more code, and the recommendation of thoughtbotter Dan Croak, who I got to know during the ’09 Rails Rumble (yet more coding!)

I’m starting to think this really is the secret sauce for professional programming success, regardless of experience level. Get some code out there for people to see, and get yourself out there to meet awesome programmers you might want to work with someday. Leave the bullshitty bullet points to the MBAs.

 
2 Comments

Posted in coding, rails