Portfolio Building

Discussion in 'Mac Programming' started by MorphingDragon, Nov 1, 2011.

  1. MorphingDragon macrumors 603

    MorphingDragon

    Joined:
    Mar 27, 2009
    Location:
    The World Inbetween
    #1
    Can someone give me or point to some articles on tips for making Portfolios aimed at Programming jobs?

    I'm applying for an Internship, I pretty much have the position but the project manager wants to see some of my work.
     
  2. chown33 macrumors 604

    Joined:
    Aug 9, 2009
    #2
    No articles, just tips.

    Make an HTML page. Clean and concise is better than clever or fancy.

    If possible (and it should be if you know anything about HTML), make it handheld friendly: e.g. add a viewport meta tag in the header. The reason for this is that a lot of casual browsing is migrating to handheld devices, and the easier you can make it for everyone (mobile or not) to see your stuff, the better that stuff will be perceived.

    Don't rely solely on rollover text (tooltips). They don't work on touchscreens.

    Be accessible (read and follow web accessibility guidelines).


    Add a descriptive summary and a link to each program you've written that you want to detail. Each one of those detail pages should stand on its own. For example, it can be the project page of your code on google-code. If the program isn't long enough for its own detail page, just summarize it.

    If some of your past programming is JavaScript and/or fancy CSS, put a link to it on your portfolio page, rather than making it reside on your portfolio-summary page. Same thing goes for Flash, Silverlight, or any other content that needs a browser plugin. In each summary, say what plugin or capability level (e.g. CSS 3) is needed. The reason for not putting these things directly on the main page is to give users a chance to see what's needed. If your main page is wholly or partly unreadable, you've already blundered.

    For each summary, put your role. If it's relevant, put the dates that you worked on each program in the summary. If you had collaborators, list them and their role.

    Write the HTML and CSS as if they were part of your CV (because they are).

    Run everything through a validator:
    HTML validator: http://validator.w3.org/
    CSS validator: http://jigsaw.w3.org/css-validator/
    MobileOK validator: http://validator.w3.org/mobile


    In short, make the same kind of summary/detail list you'd put on a CV, so someone can easily get an overview, but can also look at any item in detail.
     

Share This Page