This is a list of books currently on my To Read shelf... literally. I do not suggest or anti-suggest any of them at this time as I haven't read them yet.
Current Efforts:
Blue Parabola, LLC
web2Project
PHP'ers:
Ben Ramsey
Brandon Savage
Cal Evans
Eli White
Elizabeth Naramore
Joe LeBlanc
Matthew Turland
Matthew Weier O'Phinney
Planet PHP
Tony Bibbs
Business/mISV:
Bob Walsh
Eric Sink
Gavin Bowman
Guy Kawasaki
Joel Spolsky
Micah Baldwin
Paul Graham
Planet mISV
Past Projects:
CodeSnipers
HOBY
Judicial Watch
mobile FoxNews.com
NRTW
Great Tools I use:
Drupal
GitHub
phpUnit
Subversion
Zend Framework
This is not the home of dotProject or web2project. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
Alright, so you've been at your business for a few months or even a couple years and now it's time to grow... how do you do it?
Well, you could just hire one of your buddies. Odds are that you know him, you trust him, and you have numerous common interests and a few common goals that will help bring you together. Great idea, right?
Bzzt, wrong.
A respected collegue, collabatour, and ongoing partner of CaseySoftware - David All with the David All Group - recently brought on his Number Two and it got me thinking... In his space, the priorities are quite a bit different than the standard mISV but the core of the questions are the same... Why are you trying to recruit and what are you recruiting for? They're two fundamentally different questions that drastically affect your search and change your priorities throughout.
The first question is the easy one. It's the job description that you have in mind. Is this guy going to be answering customer email, fleshing out new functionality, making you coffee, doing the books? All of those things are quite tangible, easy to enumerate, and have a bit of "squish" to them that cover related areas. For example, in a samll shop, the guy answering customer email is probably expected to do a bit of testing and QA. There's absolutely nothing wrong with that but it needs to be acknowledged up front.
The second question is quite a fit more difficult. No matter what role you are recruiting for, the sheer fact that you have a Number Two will affect things. In some ways - regardless of their responsbilities - this person has just become your partner. Live or die, right or wrong, your fates are tied up together. No, I'm not kidding or exaggerating. If this person is of the right calibre and quality, your job may not get easier but you can hand some things to him. If this person is of the wrong calibre, you'll either realize it quickly and let them go. Or even worse - and unfortunately I saw this one last year - it's worse if you don't realize it and they stick around. The problems and extra work they cause can bury you and sink the ship.
Therefore, recruiting Number Two is one of the hardest things you'll ever do. You need this person to be a partner and feel some ownership in the organization even if they don't own any of it. Like it or not, they're a partner and a key contributor to any success or failure that comes about. And the most dangerous part is that you when you choose this person, you have to choose on that basis. Choose a friend and you'll likely lose that friend. Choose a stranger and you don't know what you're getting.
If you ever have any doubt, don't do it. It's easier finding someone else than cleaning up a mess and then finding someone else. If you have the need for a second person, you don't have the time or energy to clean up after them...
I like the picture, although
I like the picture, although I only wear the eye patch on Thursdays.
what can one say, nice
what can one say, nice advices, spound like to be working well, but you know, nowadays we live during the crises, so I think that this topic is a little bit not acute... though the ideas are really great, and I appreciate them...
Post new comment