My blog has moved!

You should be automatically redirected in 2 seconds. If not, visit
http://www.programmersmind.com/blog/
and update your bookmarks.

Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Thursday, March 20, 2008

Finding a Good PHP Programmer

Whether you're a designer, developer, or IT guy, at some point you're going to need to find a good php coder. I know, I know - I can hear you already saying it, because I also said it for so long - you don't want to sub out work, you want to do it all yourself. Well, you can continue on that way for as long as you like, but I'm tellin' you, eventually if you want to grow your business you're going to need to get some help ;) If you're not convinced, don't read any further...because you'll be wasting your time!

OK...glad we cleared that up and you're on board with me now. So - "how do I find someone I can trust" you ask? Well, lemme break it down for you. The overarching theme here is that you're not going to get it just right the first time, so you need to start small, and focus on building the skills of finding, interviewing, and managing good programmers.

Finding the talent

I would suggest you go to Guru.com and craigslist - between those two you should be able to find someone solid. Here's my process for each of them:
  • Create a form - there are a number of cool form builder tools out there if you don't know how to or want to do your own. I would include email, instant messenger, phone, name, and some 1-100 dropdowns for different key skill sets you're looking for. I think its important to build a form for a number of reasons. For one, you'll block all the spammers who automatically blast emails out when you create CL posts. And for two, you weed out the people who are only marginally interested. Whoever goes through the trouble of filling out that form is motivated and ready to work! You're going to post a link to this form on guru.com and craigslist.

  • Guru.com - you'll need to first create a free membership account. Now, the next thing you think you want to do is post a project...wrong! Well at least I don't like to do it that way, I'm cheap - and I'm pretty sure they still charge you to post a project. So the back door is to search for developers and then send them messages. I would send out a good 20 messages, that way you know you'll get at least 5 responses, and then you can move into interviewing them. You can filter by lowest pay, or highest rank. On Guru.com I think you'll tend to find larger dev firms, as opposed to individuals.

  • Craigslist.com - by now, you probly are familiar with this site. All you gotta do is go ahead and post an ad. Again, post a link to your form and don't list your email address at all. I would post this in a few different cities - but remember to word the title and body slightly different on each of them or else you'll get slapped by craigslist. You'll tend to find more individuals here than firms.
Interviewing the coder - how to know what to look for

Now don't get too intimidated here. Even if you don't know everything about coding, or if you do and you're nervous about whether you'll be able to find someone good, just relax. Here are two easy starting points for your interview.
  • Portfolio. Take a peek at their portfolio. Oh and yes, they better have a portfolio. Go through each of the projects and ask them specifically what they did on each of them. This will hit a few birds with one stone. You can get a deeper understanding of their experience level, and also get a feel for how honest and forthcoming they are. If they are skimming over things and not very open about what they contributed, you should be able to tell. You want to find someone who is honest! That is probably the most important trait in a subcontractor.

  • Ask between the lines. Now you want to take it to the next level. The key here is that you don't have to understand all the details of the technology in order to be able to feel them out. Just come up with a handful of questions to kind of ask between the lines of what they are telling you and see how they react. If they answer the question in a way that you don't understand at all that's a red flag. Because they are going to have to explain many technical issues to you throughout the duration of your relationship with them, so you want to have someone who is relatively strong at communicating.

  • Rinse and repeat. Again, you might not find a perfect fit the first go-round. So start them on something small and if it doesn't work out, move on to someone else. No harm, no foul.

Managing the coder - how to build a good ongoing relationship.

Now that you have someone that you like working with, you want to try to give them as consistent a flow of work as possible. Remember that sometimes it's important to keep them busy even if it isn't 100% profitable for you at the moment. You might want to think about paying them for a fixed number of hours, as opposed to asking for a bid for every single project. There are pro's and con's to each, which I can get into later.

Sunday, March 16, 2008

Web Design for Dummies


In my experience working on various web design and development projects, I wanted to offer some insights and tips on working with designers. Now, if you already have a designer you've worked with before and that did a good job the first time around, you're probably going to be in good shape obviously. When you're taking a first run at it, there are some more variables to keep in mind and more potential gotcha's.
  1. Talk. Try and speak with the designer over the phone before kicking the design phase off. As detailed as your wireframes or project description may be, its amazing how many things - big and small - can be glazed over when someone else is taking a fresh look at the specs. So just spend some time with them over the phone to make sure they understand the tone that you're shooting for. In today's economy where its not unusual for me to work with developers and designers who I never actually speak with - just IM or email with them - its important to take this step.

  2. Portfolio. Of course the main thing you're going to look into when looking at your designer is their portfolio. Aside from checking to see that they have some nice stuff, you want to also see that they have some diversity and variety in their work. If all their stuff looks the same, you may have trouble getting a very unique or custom design out of them, to please your customer.

  3. Availability. You're going to want to ensure that your designer is going to be available for you, especially when you need to make lots of (possibly small) revisions, but nevertheless important ones that your client wants to see right away. Unfortunately, many times the designer has to be available at a moment's notice to take care of changes, especially for a higher profile client. Check in with them on this, but go beyond that and see what they actually do. See how they respond to you over a period of time, and how their availability may change after the payment has been made.
That should get you started on the road to success with outsourcing your design work.

Wednesday, March 12, 2008

Collaborating with Developrs and Other Geekery

I picked up a little inspiration for a post that has been marinating in my brains for a little while now, which is to lay out some effective techniques I've gained in working with (don't use the "m" word) developers or as the article I referenced so endearingly puts it - geeks. And if you don't know already, geek is in fact an endearing term, and "uber-geek" quite an honor...more on that later.

Little background on myself. I was a math major in college, took a bunch of comp sci classes, and got into my first web developer position out of college. I too, am a geek....or was, well I'm not really sure which. So in all fairness it does help me quite a bit because I understand the lingo and have a similar brain chemistry to the geekdom - but really more than that I think its that I understand the common problems plaguing developers, how one feels as a developer, and simple ways to work with them in a non-intruding manner.

First off, I'd say you definitely want to have a casual style. Tech's aren't impressed by fluff or pomp and circumstance, they like to get right down to the meat of the matter, and it matters to them what you think, the content of your argument or statement. They just don't enjoy formal business attitudes or fronts very much at all.

Be nice. This one should be obvious but in the midst of urgent situations, fires that need to be put out, or clients that are confused and flailing their arms about looking for a solution, it can be easy to pass tasks off to them without acknowledging their effort or that they are busy with something else. So if you're going to ask for some help - something like "hey man, if this isn't a good time lemme know but I had a question for you". Also recognize the kinds of things that they don't like to do - repetitive or simple things that are a distraction from the complex work they are focused on - and try to work around their level of concentration at any given moment.

Communication Protocol. Tech's are most likely going to prefer to communicate by IM or email, even if they're sitting five feet away from you. They prefer it because it forces you to be more specific in your requests, and it can be much more efficient for them to respond to. And again, concentration. You have to realize this is a developer's currency - without concentration they can't get anything done, and what they do get done will be buggy, which....well that's a whole 'nother topic. So if they repeatedly ask you to IM or email them some detail, or to submit it by an online bug tracker, just get used to it - you're going to get more mileage out of their time, and they'll enjoy interacting with you much more.

Respect their time. You need to realize and really internalize that these guys are very smart and talented and they're doing important work. Think twice before asking them a question - especially if it has to do with troubleshooting Outlook, they most likely hate troubleshooting Outlook, or I don't know....maybe that was just me. And the stuff that you do need to pass off to them, do it in batches - don't give them onesy twoesy's all day long. That way, when you need something important, you'll have a good track record with them and they'll be willing to help because they realize you don't cry wolf all the time.

Hope some of these tips are useful....look forward to feedback on either side of the fence.
Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Thursday, March 20, 2008

Finding a Good PHP Programmer

Whether you're a designer, developer, or IT guy, at some point you're going to need to find a good php coder. I know, I know - I can hear you already saying it, because I also said it for so long - you don't want to sub out work, you want to do it all yourself. Well, you can continue on that way for as long as you like, but I'm tellin' you, eventually if you want to grow your business you're going to need to get some help ;) If you're not convinced, don't read any further...because you'll be wasting your time!

OK...glad we cleared that up and you're on board with me now. So - "how do I find someone I can trust" you ask? Well, lemme break it down for you. The overarching theme here is that you're not going to get it just right the first time, so you need to start small, and focus on building the skills of finding, interviewing, and managing good programmers.

Finding the talent

I would suggest you go to Guru.com and craigslist - between those two you should be able to find someone solid. Here's my process for each of them:
  • Create a form - there are a number of cool form builder tools out there if you don't know how to or want to do your own. I would include email, instant messenger, phone, name, and some 1-100 dropdowns for different key skill sets you're looking for. I think its important to build a form for a number of reasons. For one, you'll block all the spammers who automatically blast emails out when you create CL posts. And for two, you weed out the people who are only marginally interested. Whoever goes through the trouble of filling out that form is motivated and ready to work! You're going to post a link to this form on guru.com and craigslist.

  • Guru.com - you'll need to first create a free membership account. Now, the next thing you think you want to do is post a project...wrong! Well at least I don't like to do it that way, I'm cheap - and I'm pretty sure they still charge you to post a project. So the back door is to search for developers and then send them messages. I would send out a good 20 messages, that way you know you'll get at least 5 responses, and then you can move into interviewing them. You can filter by lowest pay, or highest rank. On Guru.com I think you'll tend to find larger dev firms, as opposed to individuals.

  • Craigslist.com - by now, you probly are familiar with this site. All you gotta do is go ahead and post an ad. Again, post a link to your form and don't list your email address at all. I would post this in a few different cities - but remember to word the title and body slightly different on each of them or else you'll get slapped by craigslist. You'll tend to find more individuals here than firms.
Interviewing the coder - how to know what to look for

Now don't get too intimidated here. Even if you don't know everything about coding, or if you do and you're nervous about whether you'll be able to find someone good, just relax. Here are two easy starting points for your interview.
  • Portfolio. Take a peek at their portfolio. Oh and yes, they better have a portfolio. Go through each of the projects and ask them specifically what they did on each of them. This will hit a few birds with one stone. You can get a deeper understanding of their experience level, and also get a feel for how honest and forthcoming they are. If they are skimming over things and not very open about what they contributed, you should be able to tell. You want to find someone who is honest! That is probably the most important trait in a subcontractor.

  • Ask between the lines. Now you want to take it to the next level. The key here is that you don't have to understand all the details of the technology in order to be able to feel them out. Just come up with a handful of questions to kind of ask between the lines of what they are telling you and see how they react. If they answer the question in a way that you don't understand at all that's a red flag. Because they are going to have to explain many technical issues to you throughout the duration of your relationship with them, so you want to have someone who is relatively strong at communicating.

  • Rinse and repeat. Again, you might not find a perfect fit the first go-round. So start them on something small and if it doesn't work out, move on to someone else. No harm, no foul.

Managing the coder - how to build a good ongoing relationship.

Now that you have someone that you like working with, you want to try to give them as consistent a flow of work as possible. Remember that sometimes it's important to keep them busy even if it isn't 100% profitable for you at the moment. You might want to think about paying them for a fixed number of hours, as opposed to asking for a bid for every single project. There are pro's and con's to each, which I can get into later.

Sunday, March 16, 2008

Web Design for Dummies


In my experience working on various web design and development projects, I wanted to offer some insights and tips on working with designers. Now, if you already have a designer you've worked with before and that did a good job the first time around, you're probably going to be in good shape obviously. When you're taking a first run at it, there are some more variables to keep in mind and more potential gotcha's.
  1. Talk. Try and speak with the designer over the phone before kicking the design phase off. As detailed as your wireframes or project description may be, its amazing how many things - big and small - can be glazed over when someone else is taking a fresh look at the specs. So just spend some time with them over the phone to make sure they understand the tone that you're shooting for. In today's economy where its not unusual for me to work with developers and designers who I never actually speak with - just IM or email with them - its important to take this step.

  2. Portfolio. Of course the main thing you're going to look into when looking at your designer is their portfolio. Aside from checking to see that they have some nice stuff, you want to also see that they have some diversity and variety in their work. If all their stuff looks the same, you may have trouble getting a very unique or custom design out of them, to please your customer.

  3. Availability. You're going to want to ensure that your designer is going to be available for you, especially when you need to make lots of (possibly small) revisions, but nevertheless important ones that your client wants to see right away. Unfortunately, many times the designer has to be available at a moment's notice to take care of changes, especially for a higher profile client. Check in with them on this, but go beyond that and see what they actually do. See how they respond to you over a period of time, and how their availability may change after the payment has been made.
That should get you started on the road to success with outsourcing your design work.

Wednesday, March 12, 2008

Collaborating with Developrs and Other Geekery

I picked up a little inspiration for a post that has been marinating in my brains for a little while now, which is to lay out some effective techniques I've gained in working with (don't use the "m" word) developers or as the article I referenced so endearingly puts it - geeks. And if you don't know already, geek is in fact an endearing term, and "uber-geek" quite an honor...more on that later.

Little background on myself. I was a math major in college, took a bunch of comp sci classes, and got into my first web developer position out of college. I too, am a geek....or was, well I'm not really sure which. So in all fairness it does help me quite a bit because I understand the lingo and have a similar brain chemistry to the geekdom - but really more than that I think its that I understand the common problems plaguing developers, how one feels as a developer, and simple ways to work with them in a non-intruding manner.

First off, I'd say you definitely want to have a casual style. Tech's aren't impressed by fluff or pomp and circumstance, they like to get right down to the meat of the matter, and it matters to them what you think, the content of your argument or statement. They just don't enjoy formal business attitudes or fronts very much at all.

Be nice. This one should be obvious but in the midst of urgent situations, fires that need to be put out, or clients that are confused and flailing their arms about looking for a solution, it can be easy to pass tasks off to them without acknowledging their effort or that they are busy with something else. So if you're going to ask for some help - something like "hey man, if this isn't a good time lemme know but I had a question for you". Also recognize the kinds of things that they don't like to do - repetitive or simple things that are a distraction from the complex work they are focused on - and try to work around their level of concentration at any given moment.

Communication Protocol. Tech's are most likely going to prefer to communicate by IM or email, even if they're sitting five feet away from you. They prefer it because it forces you to be more specific in your requests, and it can be much more efficient for them to respond to. And again, concentration. You have to realize this is a developer's currency - without concentration they can't get anything done, and what they do get done will be buggy, which....well that's a whole 'nother topic. So if they repeatedly ask you to IM or email them some detail, or to submit it by an online bug tracker, just get used to it - you're going to get more mileage out of their time, and they'll enjoy interacting with you much more.

Respect their time. You need to realize and really internalize that these guys are very smart and talented and they're doing important work. Think twice before asking them a question - especially if it has to do with troubleshooting Outlook, they most likely hate troubleshooting Outlook, or I don't know....maybe that was just me. And the stuff that you do need to pass off to them, do it in batches - don't give them onesy twoesy's all day long. That way, when you need something important, you'll have a good track record with them and they'll be willing to help because they realize you don't cry wolf all the time.

Hope some of these tips are useful....look forward to feedback on either side of the fence.