Questions on how to work with a freelancer

Discussion in 'Programming' started by mrx345, Dec 24, 2011.

  1. #1
    I am going to place a project on developing a website in PHP which will be a clone of one of the existing web sites (let say Groupon complexity level). Since this is my first time on freelencer.com I got a few questions.

    1. How do I explain to developers what I need? do I need to create mockups? how detailed it should be?

    2. Do they also take care of the design? do I need to provide them with pictures and logo?

    3. Since I am a developer myself, will I be able to see the code (partly ready) during the development and provide my comments. Maybe when each milestone is over?

    4. just wanted to double check that I will I have the full rights for the code?

    5. they will hand me over the code (not fully completed) after completion of each milestone, right?

    6. are there any tutorials or tips that I can read?

    Thank you very much
     
    mrx345, Dec 24, 2011 IP
  2. proactiv3

    proactiv3 Peon

    Messages:
    55
    Likes Received:
    7
    Best Answers:
    4
    Trophy Points:
    0
    #2
    1. Compile a complete list of requirements\functionalities that you'll need for your website. Any *decent* freelancer will translate each and every one of those features into time needed for completion - and will present a budget accordingly.

    Once again keep in mind that if you decide to add/change features along the way, you should expect a price adjustment. That being said planning (on your behalf) is absolutely critical. When asking for a price estimate make sure you provide a detailed description of what you want.

    For complex projects I usually sign a contract stating (amongst other things) a detailed list of items I'm suppose to deliver. There's no such thing as too much information.


    2. It depends on the guy you choose to work with. From my experience a UI\UX\front-end developer (whatever you like to cal it) is not a great programmer (and vice-versa). If you think about it makes perfect sense - a guy who's into programming languages, structuring good algorithms, ... - does not make a good designer.

    Guys who are good developers and good designers are pure gold and usually not available. If you do find one, give him everything he wants in order to stick him around...

    Now it depends on the quality of output that you're expecting and (most importantly) on the investment you are willing to make. Guys who state that are great designers and programmers and ask $10/h are usually mediocre in both web design and programming.


    3. If its a big project schedule weekly meetings where you give feedback about what has been done. Do not flood your developer's inbox everyday - you'll end up with a very unhappy programmer who will associate your name to a plague.

    From my experience the best projects are the ones where I'm able to meet with the client from time to time. For example every friday afternoon you'd sit with the developer, look at what has been done and plan the week ahead.

    Milestones are a great way to motivate a freelancer, specially if you release a part of the payment upon a milestone completion. This way you'll give him a sense of accomplishment (no one likes those "never ending projects").


    4. If you're a programmer yourself discuss this with the programmer. If you can sign a contract, even better - but usually yes the code is yours. Also openly ask\discuss with whoever you hire the possibility of using third party libraries \ frameworks.


    5. Once again establish the way you want to work beforehand. It's better to see a freelancer drop on a project because he doesn't like your terms, than having it quit at the middle of it, because he's tired of working with you.

    From my personal experience I'd recommend that you set up a code revision system of your own (SVN, Git, ...) and ask the programmer to commit the changes to the repository. Obviously in order to work this way, you'll need to have an escrow payment of some kind or to release payments along the way (so there's no chance of you keeping the code and not paying anything).

    Good luck!
     
    proactiv3, Dec 25, 2011 IP
    aceriker likes this.
  3. aceriker

    aceriker Banned

    Messages:
    274
    Likes Received:
    6
    Best Answers:
    5
    Trophy Points:
    70
    #3
    I'm not sure if there is too much I can add to the great post by proactiv3 but I would recommend breaking the project down in to very small iterations. When you are outsourcing, anything that can be misunderstood will be misunderstood, especially if you can't meet the person face to face.

    What's the most basic website you can make to get the functionality and build from there. Each feature should be a separate project. It's good to give the developer an overview of what's required but it's better to start with something very basic. If you are doing a shopping cart then creating the ability to add categories, sub-categories and products is the first feature you need. Then you might add the ability to have variations and options associated with the product - but this comes under a different project. As each project is completed, test, test and test some more and only then move on to the next part.

    Peter
     
    aceriker, Dec 28, 2011 IP
  4. ColinLiang

    ColinLiang Peon

    Messages:
    135
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    0
    #4
    1. You should create some kind of mock-up for website design. Using either hand or some picture editor just do a rough example of what you want the site to look like. At the very least give them three examples of the types of similar sites.

    2. Depends. Some programmers do design as well. From personal experience, programmers at the best at creating UIs. You should hire a designer (a creative type) to collaborate and create design, while the web developer works on the site's functionality.

    3. Yeah, just get them to email you the code. In fact, it's highly recommended that you keep in close contact with your developer. After the first three hours they work on the project, get them to email you back immediately and tell you about any complications they had. Sometimes, the project is just not possible for them.

    4. It's yours, yes.

    5. Completely up to you and the programmer. Set up the conditions of the working relationship before hand. Write it out very specifically and you'll be fine.

    6. There are a couple of good books out there. 4 Hour Work Week for general outsourcing tips.
     
    ColinLiang, Dec 28, 2011 IP