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 tips and tricks. Show all posts
Showing posts with label tips and tricks. Show all posts

Monday, March 24, 2008

6 Firefox Extentions Every Developer Needs


I don't need to convince you why firefox is the best browser in the world, so let's get right into it. I want to go over some of the extensions that I love, and that you can't live without!
  1. Web developer toolbar. Alright, that one was obvious. The main things I like about it though are the outline css elements, display form details, and clear cookies. Especially since I use Emacs for my html editing, it helps to be able to visualize my html/css every once in a while, especially when debugging some gnarly html tables.

  2. MeasureIt. This one's great for pulling dimensions off the screen without having to do a screengrab and pull it into photoshop.

  3. ColorZilla. When you need to get the hex code for a color on the screen, look no further! A handy-dandy color dropper.

  4. Live HTTP Headers. I pull this bad-boy out of my back pocket for the more advanced ninja tactics when I'm trying to debug flash or ajax code. When you don't have a specific URL to hit when you're testing, use the live headers to see where your browser is pulling data from. Little annoying though how if you have gmail open and you're staring intensely at your header log, like every 5 seconds you see a hit to gmail.

  5. Lorem Ipsum Generator. Nice little convenience tool for generating our favorite latin nonsense for design mockups, etc. The other way I usuall grab latin quickly if I don't have this installed, is by searching lorum ipsum on google, but the site you get to, always takes me like twice as long...so I like the extension a lot better.

  6. Screengrab. Sweet little tool to pull a screen grab off your browser. Doesn't work with flash though. One of the recent features they did which I like is allowing you to grab a selected rectangle, instead of just grabbing the whole screen. One thing that doesn't seem to ever work the way I expect it to is the Copy feature - as opposed to the Save feature - it doesn't seem to let me paste it anywhere! Email, paint, or anything.
Now that you're strapped with your developer tools, you're ready to rock and roll. Now go build some cool stuff!

Friday, March 21, 2008

Who wrote the book on freelancing?

If you're thinking about getting ready to take the leap into a freelancing career for yourself, you may be wondering...who wrote the book on freelancing? Is there a definitive source of information for all the complex quandries you will have - all the scenarios running through your brain, all the excitement? All the fear?



Well, I've taken a peek at How to be a Rockstar Freelancer and I think it does a pretty solid job! It is written by some guys who really have some great experience in freelancing and have an obvious passion for it. You get the vibe from the opening quote in the book:
"Beginning a freelancing career is one of the most exciting things you'll ever do. Maybe it's the thrill of giving your nine-to-five the flick, maybe it's the prospect of being your own boss, or maybe it's just the knowledge that you are the master of your own destiny."
Here are a list of the chapters and topics that are covered in this book:
  1. Getting Started - what is freelancing, your job and freelancing on the side, etc.
  2. Your Brand - what is branding for a freelancer, what can branding do for you?, etc.
  3. The Working Day - home or office, a happy workplace, equipment, etc.
  4. Getting Your First Projects - your portfolio, your first leads, referrals, etc.
  5. Project Scope and Timing - taking a brief, documenting a brief, estimating timeframes, etc.
  6. Pricing Yourself - your costs and your break-even rate, calculating your hourly, etc.
  7. Doing the Project - setting expectations, tracking your hours, communication, etc.
  8. Clients - leads and clients, essential client skills, etc.
  9. Getting Paid - invoicing, cash flow, bookkeeping and accounts, etc.
  10. Marketing Yourself - positioning yourself, marketing cycles, etc.
  11. Expansion - subcontracting, partnerships, hiring staff, etc.
Notice that doing the project is #7 on the list! That is very true! There is much preparation that needs to be done - and much that I wish I would have done when I first first getting into this - in order to have a smooth ride along this path.

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.

Tuesday, March 18, 2008

Taming the Beast: Managing Client Expectations

There are few things in your consulting business which have as large an impact on your bottom line and on your overall piece of mind as managing client expectations. What may sound like a fluffy buzzword is actually an amazingly critical component to your success. It is the difference between getting a second project from the client and only getting one. The difference between getting the project done gradually over time, on schedule, and on budget - and wasting a whole weekend getting things finished up.

Now this business of managing expectations is a sticky issue and I definitely don't pretend to have all the answers. I don't have some experience though and have been through the trenches a bit and can offer a few hints in the right direction. I don't have sufficient space in this post to even go over everything, perhaps I will do a series on this topic later.
  1. Expect the unexpected. Realize up front and get it burned into your mind - the client is going to creep the scope on you! They are going to change their minds on you as much as they humanly can. They are going to say everything is a "small thing", a little change, something that "should be easy, right?". Don't expect the client to somehow understand when they are going out of scope, just realize that they will and stay on your toes!

  2. Early and often. You need to reinforce the scope of your project early in on the beginning of the project and mention it almost every time you speak with them. Remind them that they need to get everything figured out, get everything spec'd out, finalize the scope. Say it in as many ways as possible, because for some reason, it just doesn't get into their heads. You need to train the client on what the development process is - they will not know it coming in, unless someone else has already trained them, and they will not learn it easily. It is, from their perspective, very counter intuitive.

  3. Red flags. You need to keep your eyes open for some classic red flags that your project is going out of scope. Sometimes you'll be talking with them and they'll quickly mention - "oh ya and it should just tie into the database", or "and it will do some emails", or various other sweeping statements that although they sound deceptively simple, will add thousands of dollars to your budget. I remember, early on, being tempted to glaze over those details in the interest of time, or because I was just too tired at the moment to belabor the details. I beg you - belabor the details! Because if not, they will end up belaboring you, my friend!! Every hour you spend up front on scope and discovery will save you 3 on the back end.
Here are some quick tips to make sure you are staying on top of the client's expectations and keeping the scope manageable.
  1. Written contract up front - this is a must, you gotta have something in writin.
  2. Discovery phase - have a defined stage of the process where you are collecting information, and setting up the architecture for the application or website. This stage should have a definitive end date.
  3. Repetition. Again, you have to train the client to understand the necessity for clear specs up front.
After putting these tips into practice, you should be well on your way to managing client expectations in a way that will keep them happy, keep the project on track, and keep you with at least an ounce or two of sanity at the end of the day! ;)

Monday, March 17, 2008

Get Your Portfolio Up

If you're on the road to building your freelancing business, and you're answer to the question "Can I see your portfolio?" is any one of the following, you have a problem:
  • Ya, I worked on it in one of my classes but don't have it finished yet.
  • Yes, I have it on a CD, but its not online.
  • Yes, but its not ready yet.
  • No
You need to realize that your portfolio is the most important touch point to the outside world. When potential clients consider working with you, their initial impression is going to depend almost entirely on what they see in your portfolio.

"Well I don't have one, yet", you say? Not a problem. This is your first homework assignment. And there's good news, there are tons of people out there just waiting to take advantage... ahum... help you. Now, you don't want to work with just anyone who will work with you, and you're in luck because you have a rare moment in your career and business life to be picky! Pick whoever you want to work with and realize that although they are helping you build your portfolio, you are really helping them! Also, there's no reason you shouldn't be able to get at least some minimal pay while building your portfolio. But, unless you absolutely can't afford it, I highly recommend that you pick some high-end, nice sites to work on, because even if you're not paid up front, the value of having nice portfolio pieces will pay off in the long run.

Since I started working freelance gigs, I completely stopped providing resumes even when people asked me. I took it as a sign, that they as a client weren't very well informed about how to find a good developer, so I wouldn't even humor them by providing one of my older versions. And really, as you are working freelance and building your business, you need to get beyond the resume mindset, and realize that your reputation should go beyond that.

Now, once you get your portfolio up and running, that's great! However, you need to continue to update it periodically over time. Don't let it get rusty, and probably at least once a year you want to do a nice overhaul on it. I can't emphasize enough how much a nice portfolio will pay dividends by helping you bring in more business down the line. You can also tie it into a newsletter to further increase your reach.

Friday, March 14, 2008

Persistance


Wanted to share some perspectives on the topic of persistence. I feel that I learned a good deal about persistence in my experience finding and converting sales leads for my web development business. And it seems like the more people I come into contact with, the more I realize how few people have this skill down.

To give a little background on how I worked my sales leads, but without giving out all the secret sauce, I'll put it this way. Basically I had a simple system for following up with warm leads a certain number of times in a non-spammy way.

It seems like so many people and organizations either fail to be persistent at all or they setup some sort of spammy system which is not well thought-out and which leads ultimately to a lot of frustration and annoyance for the user. As an example, I remember calling Authorize.net about a question I had and I somehow gave them my email, and have been receiving like weekly emails ever since, I've probly received at least 100 emails by now. And the first time or two I really thought the emails were coming from the account exec I spoke with originally, at least they had a decent email template set up. But after like the 6th one I realized I had been duped! And from then on, my opinion of them just continued to go down until I setup a gmail filter so I never again saw their emails....ah yes the blessed gmail filter!

Thursday, March 13, 2008

Awesome Online Whiteboard for Remote Collaboration

Stumbled onto a really nice online collaboration app and the gears in my head are spinning as to how to implement this in the context of a web development team. I think that as development teams are increasingly geographically distributed, things like this are becoming more and more necessary. First email was not enough, and now IM doesn't quite cut it, voice chat doesn't give you the visual you need, and tools like this are coming in to fill the gap.

Ajax interface. From what I can tell this thing is built in ajax, which I still can't get my head around, I thought for sure it would be a flash app, but I can't get flash to reveal itself by any of my well-placed right clicks anywhere in the thing! Most of the tools are all very friendly to work with - easy drag and drop, resizing is simple, overall very impressive.

Quickstart with sandbox. Nice handy feature for those of us who are reluctant to register for a site. It's funny when I first got to the site, I figured "this quickstart thing isn't really going to let me do anything", so I went ahead and registered and checked it out. And only now when I went ahead and checked the quickstart out did I find that it lets you right in, no reg required. Great way to get in and start collaborating with others in real time.

Design concepts. I think this could be an awesome tool for the design process for websites. You can quickly pull a url screenshot into the app and then start marking it up with all kinds of drawings and notes. Many times it takes way longer than you would think to communicate to someone exactly where on the screen you are referring to! And then, sometimes you're talking for 20 minutes about one part of the screen, and little do you realize the other person is thinking of some other place entirely! Real time whiteboarding rocks!

Wednesday, June 7, 2006

On Reinstalling

This is a quick list of tips for reinstalling, or in my case, setting up your new computer and migrating all your apps and data from your old computer. Oh, a 710m - thanks for asking. Most are skeptical that it will make for a good full time computer b/c of the small keyboard, but I'm going to show'em all. I think it will be a slick companion for my coffee shop hopping.

Anyway, the list:
  1. My Music
  2. My Documents
  3. IE / Firefox bookmarks
  4. Any local webserver document root files you have. If you're like me, you do a lot of development off of your own local server, so don't forget all the files in that htdocs directory.
  5. Local mysql db - again, if you do local development you probably have a bunch of development db's that you'll need for future reference. There's a quicker way to transfer than just dumping into a sql statement, which is to just copy the mysql/data directory from your old computer to your new (I'm running xampp).
  6. VPN config files - if you connect to a vpn, remember to copy over your .key, .crt, and .csr files
  7. Any application config files. The only one I have to take care of is Emacs - don't leave home without your .emacs file.
  8. Firefox extensions - the essentials: MeasureIt, ColorZilla, Mouse Gestures, Web Developer
Showing posts with label tips and tricks. Show all posts
Showing posts with label tips and tricks. Show all posts

Monday, March 24, 2008

6 Firefox Extentions Every Developer Needs


I don't need to convince you why firefox is the best browser in the world, so let's get right into it. I want to go over some of the extensions that I love, and that you can't live without!
  1. Web developer toolbar. Alright, that one was obvious. The main things I like about it though are the outline css elements, display form details, and clear cookies. Especially since I use Emacs for my html editing, it helps to be able to visualize my html/css every once in a while, especially when debugging some gnarly html tables.

  2. MeasureIt. This one's great for pulling dimensions off the screen without having to do a screengrab and pull it into photoshop.

  3. ColorZilla. When you need to get the hex code for a color on the screen, look no further! A handy-dandy color dropper.

  4. Live HTTP Headers. I pull this bad-boy out of my back pocket for the more advanced ninja tactics when I'm trying to debug flash or ajax code. When you don't have a specific URL to hit when you're testing, use the live headers to see where your browser is pulling data from. Little annoying though how if you have gmail open and you're staring intensely at your header log, like every 5 seconds you see a hit to gmail.

  5. Lorem Ipsum Generator. Nice little convenience tool for generating our favorite latin nonsense for design mockups, etc. The other way I usuall grab latin quickly if I don't have this installed, is by searching lorum ipsum on google, but the site you get to, always takes me like twice as long...so I like the extension a lot better.

  6. Screengrab. Sweet little tool to pull a screen grab off your browser. Doesn't work with flash though. One of the recent features they did which I like is allowing you to grab a selected rectangle, instead of just grabbing the whole screen. One thing that doesn't seem to ever work the way I expect it to is the Copy feature - as opposed to the Save feature - it doesn't seem to let me paste it anywhere! Email, paint, or anything.
Now that you're strapped with your developer tools, you're ready to rock and roll. Now go build some cool stuff!

Friday, March 21, 2008

Who wrote the book on freelancing?

If you're thinking about getting ready to take the leap into a freelancing career for yourself, you may be wondering...who wrote the book on freelancing? Is there a definitive source of information for all the complex quandries you will have - all the scenarios running through your brain, all the excitement? All the fear?



Well, I've taken a peek at How to be a Rockstar Freelancer and I think it does a pretty solid job! It is written by some guys who really have some great experience in freelancing and have an obvious passion for it. You get the vibe from the opening quote in the book:
"Beginning a freelancing career is one of the most exciting things you'll ever do. Maybe it's the thrill of giving your nine-to-five the flick, maybe it's the prospect of being your own boss, or maybe it's just the knowledge that you are the master of your own destiny."
Here are a list of the chapters and topics that are covered in this book:
  1. Getting Started - what is freelancing, your job and freelancing on the side, etc.
  2. Your Brand - what is branding for a freelancer, what can branding do for you?, etc.
  3. The Working Day - home or office, a happy workplace, equipment, etc.
  4. Getting Your First Projects - your portfolio, your first leads, referrals, etc.
  5. Project Scope and Timing - taking a brief, documenting a brief, estimating timeframes, etc.
  6. Pricing Yourself - your costs and your break-even rate, calculating your hourly, etc.
  7. Doing the Project - setting expectations, tracking your hours, communication, etc.
  8. Clients - leads and clients, essential client skills, etc.
  9. Getting Paid - invoicing, cash flow, bookkeeping and accounts, etc.
  10. Marketing Yourself - positioning yourself, marketing cycles, etc.
  11. Expansion - subcontracting, partnerships, hiring staff, etc.
Notice that doing the project is #7 on the list! That is very true! There is much preparation that needs to be done - and much that I wish I would have done when I first first getting into this - in order to have a smooth ride along this path.

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.

Tuesday, March 18, 2008

Taming the Beast: Managing Client Expectations

There are few things in your consulting business which have as large an impact on your bottom line and on your overall piece of mind as managing client expectations. What may sound like a fluffy buzzword is actually an amazingly critical component to your success. It is the difference between getting a second project from the client and only getting one. The difference between getting the project done gradually over time, on schedule, and on budget - and wasting a whole weekend getting things finished up.

Now this business of managing expectations is a sticky issue and I definitely don't pretend to have all the answers. I don't have some experience though and have been through the trenches a bit and can offer a few hints in the right direction. I don't have sufficient space in this post to even go over everything, perhaps I will do a series on this topic later.
  1. Expect the unexpected. Realize up front and get it burned into your mind - the client is going to creep the scope on you! They are going to change their minds on you as much as they humanly can. They are going to say everything is a "small thing", a little change, something that "should be easy, right?". Don't expect the client to somehow understand when they are going out of scope, just realize that they will and stay on your toes!

  2. Early and often. You need to reinforce the scope of your project early in on the beginning of the project and mention it almost every time you speak with them. Remind them that they need to get everything figured out, get everything spec'd out, finalize the scope. Say it in as many ways as possible, because for some reason, it just doesn't get into their heads. You need to train the client on what the development process is - they will not know it coming in, unless someone else has already trained them, and they will not learn it easily. It is, from their perspective, very counter intuitive.

  3. Red flags. You need to keep your eyes open for some classic red flags that your project is going out of scope. Sometimes you'll be talking with them and they'll quickly mention - "oh ya and it should just tie into the database", or "and it will do some emails", or various other sweeping statements that although they sound deceptively simple, will add thousands of dollars to your budget. I remember, early on, being tempted to glaze over those details in the interest of time, or because I was just too tired at the moment to belabor the details. I beg you - belabor the details! Because if not, they will end up belaboring you, my friend!! Every hour you spend up front on scope and discovery will save you 3 on the back end.
Here are some quick tips to make sure you are staying on top of the client's expectations and keeping the scope manageable.
  1. Written contract up front - this is a must, you gotta have something in writin.
  2. Discovery phase - have a defined stage of the process where you are collecting information, and setting up the architecture for the application or website. This stage should have a definitive end date.
  3. Repetition. Again, you have to train the client to understand the necessity for clear specs up front.
After putting these tips into practice, you should be well on your way to managing client expectations in a way that will keep them happy, keep the project on track, and keep you with at least an ounce or two of sanity at the end of the day! ;)

Monday, March 17, 2008

Get Your Portfolio Up

If you're on the road to building your freelancing business, and you're answer to the question "Can I see your portfolio?" is any one of the following, you have a problem:
  • Ya, I worked on it in one of my classes but don't have it finished yet.
  • Yes, I have it on a CD, but its not online.
  • Yes, but its not ready yet.
  • No
You need to realize that your portfolio is the most important touch point to the outside world. When potential clients consider working with you, their initial impression is going to depend almost entirely on what they see in your portfolio.

"Well I don't have one, yet", you say? Not a problem. This is your first homework assignment. And there's good news, there are tons of people out there just waiting to take advantage... ahum... help you. Now, you don't want to work with just anyone who will work with you, and you're in luck because you have a rare moment in your career and business life to be picky! Pick whoever you want to work with and realize that although they are helping you build your portfolio, you are really helping them! Also, there's no reason you shouldn't be able to get at least some minimal pay while building your portfolio. But, unless you absolutely can't afford it, I highly recommend that you pick some high-end, nice sites to work on, because even if you're not paid up front, the value of having nice portfolio pieces will pay off in the long run.

Since I started working freelance gigs, I completely stopped providing resumes even when people asked me. I took it as a sign, that they as a client weren't very well informed about how to find a good developer, so I wouldn't even humor them by providing one of my older versions. And really, as you are working freelance and building your business, you need to get beyond the resume mindset, and realize that your reputation should go beyond that.

Now, once you get your portfolio up and running, that's great! However, you need to continue to update it periodically over time. Don't let it get rusty, and probably at least once a year you want to do a nice overhaul on it. I can't emphasize enough how much a nice portfolio will pay dividends by helping you bring in more business down the line. You can also tie it into a newsletter to further increase your reach.

Friday, March 14, 2008

Persistance


Wanted to share some perspectives on the topic of persistence. I feel that I learned a good deal about persistence in my experience finding and converting sales leads for my web development business. And it seems like the more people I come into contact with, the more I realize how few people have this skill down.

To give a little background on how I worked my sales leads, but without giving out all the secret sauce, I'll put it this way. Basically I had a simple system for following up with warm leads a certain number of times in a non-spammy way.

It seems like so many people and organizations either fail to be persistent at all or they setup some sort of spammy system which is not well thought-out and which leads ultimately to a lot of frustration and annoyance for the user. As an example, I remember calling Authorize.net about a question I had and I somehow gave them my email, and have been receiving like weekly emails ever since, I've probly received at least 100 emails by now. And the first time or two I really thought the emails were coming from the account exec I spoke with originally, at least they had a decent email template set up. But after like the 6th one I realized I had been duped! And from then on, my opinion of them just continued to go down until I setup a gmail filter so I never again saw their emails....ah yes the blessed gmail filter!

Thursday, March 13, 2008

Awesome Online Whiteboard for Remote Collaboration

Stumbled onto a really nice online collaboration app and the gears in my head are spinning as to how to implement this in the context of a web development team. I think that as development teams are increasingly geographically distributed, things like this are becoming more and more necessary. First email was not enough, and now IM doesn't quite cut it, voice chat doesn't give you the visual you need, and tools like this are coming in to fill the gap.

Ajax interface. From what I can tell this thing is built in ajax, which I still can't get my head around, I thought for sure it would be a flash app, but I can't get flash to reveal itself by any of my well-placed right clicks anywhere in the thing! Most of the tools are all very friendly to work with - easy drag and drop, resizing is simple, overall very impressive.

Quickstart with sandbox. Nice handy feature for those of us who are reluctant to register for a site. It's funny when I first got to the site, I figured "this quickstart thing isn't really going to let me do anything", so I went ahead and registered and checked it out. And only now when I went ahead and checked the quickstart out did I find that it lets you right in, no reg required. Great way to get in and start collaborating with others in real time.

Design concepts. I think this could be an awesome tool for the design process for websites. You can quickly pull a url screenshot into the app and then start marking it up with all kinds of drawings and notes. Many times it takes way longer than you would think to communicate to someone exactly where on the screen you are referring to! And then, sometimes you're talking for 20 minutes about one part of the screen, and little do you realize the other person is thinking of some other place entirely! Real time whiteboarding rocks!

Wednesday, June 7, 2006

On Reinstalling

This is a quick list of tips for reinstalling, or in my case, setting up your new computer and migrating all your apps and data from your old computer. Oh, a 710m - thanks for asking. Most are skeptical that it will make for a good full time computer b/c of the small keyboard, but I'm going to show'em all. I think it will be a slick companion for my coffee shop hopping.

Anyway, the list:
  1. My Music
  2. My Documents
  3. IE / Firefox bookmarks
  4. Any local webserver document root files you have. If you're like me, you do a lot of development off of your own local server, so don't forget all the files in that htdocs directory.
  5. Local mysql db - again, if you do local development you probably have a bunch of development db's that you'll need for future reference. There's a quicker way to transfer than just dumping into a sql statement, which is to just copy the mysql/data directory from your old computer to your new (I'm running xampp).
  6. VPN config files - if you connect to a vpn, remember to copy over your .key, .crt, and .csr files
  7. Any application config files. The only one I have to take care of is Emacs - don't leave home without your .emacs file.
  8. Firefox extensions - the essentials: MeasureIt, ColorZilla, Mouse Gestures, Web Developer