Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

Vanilla 1.1.5a is a product of Lussumo. More Information: Documentation, Community Support.

  1.  permalink

    I found a programmer thru craigslist looking for designers to work with on freelance pr projects. I am new to freelancing and I’m not sure what to ask this guy to make sure he’s legit. What kind of questions do you usually ask programmers to feel them out?

    Thanks!

  2.  permalink
    Just ask for regular credentials that he has.
    Resume, past project maybe references if he can provide it.
    If know nothing about programming it's doesn't make any sense for you to ask any question related to the programming field. Just ask general question to get a feel how he is working.
    What is really important for you it's result to get the job done in time and according specifications.


    Best, DS
    • CommentAuthorbrowntown
    • CommentTimeSep 29th 2006
     permalink
    these may come in handy.
    • CommentAuthordhayes
    • CommentTimeOct 1st 2006 edited
     permalink

    What to ask potential programming partners?


    What kind of questions do you usually ask programmers to feel them out?

    I would ask:
    -Are you currently partnering with someone else?
    -How many partners have you had?
    -Have you ever had a virus or been hacked?
    -How long has it been since your last virus or hack?
    -How many partners have you had since then?
    -Have you ever been treated for SQL injection?
    -Do you know how to tell if you're vulnerable to SQL injections?
    -Do you prefer having your apps tested by QA, or just using mod_security or SNORT

    the similarities are astonishing.

    /couldn't resist.
    //sorry..ehem.
    • CommentAuthorpxlronin
    • CommentTimeOct 4th 2006
     permalink
    that's funny
    •  
      CommentAuthorkenbacca
    • CommentTimeOct 4th 2006
     permalink
    I was getting ready to say this looked like a STD questionaire, then I saw the link.

    Well, I guess I said it anyway.

    If you are paying the programmer, I'd establish how updates / changes to the scope will effect the price / timeline. It's a good idea to figure out how to handle scope creep beforehand. It always happens...
    • CommentAuthorinovica
    • CommentTimeOct 6th 2006
     permalink
    From someone who has worked with different freelance programmers for eight years now (and for 6 we've got a pretty solid team that has stayed together through mutual respect) I would ask the following:

    - Do they have sites that they have programmed that you can go and see. Yes, you might only be able to use the front-end design, but you should be able to see if the programming works well or not
    - Do they have references from anyone else they've worked with
    - Do they have particular preferences when it comes to programming languages. If someone is ardent about only doing programming in ABC and "everything else is sh*t" then I would walk away. If you find a programmer willing to be flexible, they will understand the changing nature of the industry and you will also have someone keen to learn. The second side of this is sometimes clients dictate the programming language they want something created in and therefore you do not want to get locked into one language or method

    Finally, I would try them. The best way that I have found is to invest a little bit of money in a mini-projects - this could be something that you wish to create yourself anyway. Get them to do the programming and monitor the relationship. Are you updated regularly? Is it full of bugs when they tell you 'it's finished' or do they do their own thorough bug testing? Is the mini job delivered on time? Do they say "yes, this looks great" or "that will be difficult or might not be possible".

    I myself taught myself to program at a basic level just so that I was aware of what was required, and it helped to be able to converse, to a degree, about technical matters

    Hope this helps. Just my own take on it of course :)

    Ade
    inovica.com
    • CommentAuthorsean9999
    • CommentTimeNov 9th 2006
     permalink
    ask him about star trek
    • CommentAuthorMatt
    • CommentTimeNov 10th 2006
     permalink
    To invica, it is fairly difficult and/or time consuming to learn multiple server side languages and be proficient at them. If they can create what they need to in the language they use, and can do it in an acceptable time frame that I see no reason why they should learn a second server side language. Honestly, if someone told me they know coldfusion, ruby, php, asp, aspx, jsp and whatever else I could call them out saying they were just BSing to fluff their resume. If someone told me they were highly proficient in aspx or php I could be more likely to hire them (if I hired programmers).

    Honestly, try to find a good programmer you know to sit in on the interview, it really really help. I have been asked to sit in on some interviews, and even them just knowing there is someone who is good in their field watching will make them stop their bs. :-)
    • CommentAuthorvarland
    • CommentTimeNov 10th 2006
     permalink
    Matt—I see your point about it being difficult to master multiple server-side languages, but I'd be hesitant to hire a programmer who's only proficient in one. If you only know one server-side language, you're much less likely to see the pitfalls of that language, which can be dangerous. I concentrate on PHP, but I also know a good amount of ASP.NET and Ruby on Rails. Frankly, there are things that ASP.NET does better than PHP. If I only knew PHP, I would have had to turn down a few jobs because I wouldn't have been able to do in PHP what I was able to do in ASP.NET.

    I'm not saying that all programmers should be equally proficient in 16 different server-side languages, but proficiency in only 1 is a liability.
    • CommentAuthoreasement
    • CommentTimeNov 10th 2006
     permalink
    It all really boils to can they think like a machine and hit the deadlines.

    Once you know how to develop an algorithm, then it's just syntax for the particular language you are coding in. Most projects that would be partnered out don't require you to spec out the Big O notation and determine efficiency. I do all all the fun CS stuff because that's what I like doing, but I've had small projects that I've done some pseudo code and then went banged it out without doing any benchmarking tests because scalability wasn't going to be an issue and the budget was tight.

    Also, many languages are going to be nice to have, but that person usually comes with a higher price tag and will most likely code in the language he/she is most familiar with which is as good as knowing one language.
Add your comments
    Username Password
  • Format comments as (Help)