[Skip Navigation] [Remove Frame] [CS320] [Text Version] portfolios.html Sat Dec 23 08:00:35 PST 2006


    What Makes a Good Portfolio?


      It provides a record of things that you have learned and done that you can use, in the future, when you need to remember it. It guides you to examples of things that work and things that are bad, and things that are interesting.

      Keep It Simple!

      You should have links to very simple examples of code that demonstrate the rules you want to remember. It should say what the rules are and point to the examples of the rule:

      "In LISP it is simple to simulate records by defining function to construct them and functions to extract components from them."

      "In Prolog you don't have any functions so you simulate y=square(x) by square(y,x)".

      "In Java there is no main program, but a class of objects can have a method that works like a C/C++ main program"


      It should be about you. It should point to code that interested you, even if you found it somewhere else. Your comments should be your own even if the code is somebody else's.


      If you didn't write it, then you must say where it came from.

      Looks good

      It should be something that you can have some pride in.

      It should have some kind of structure, perhaps have a few small decorations, and must be easy to read. It should be written and designed so that you won't feel ashamed of it later because of spelling mistakes, bad grammar, or something silly.

      A little complexity

      You might want to have some pointers to something complicated you have done as well as several simple examples, just to show what you are capable of.

    . . . . . . . . . ( end of section What Makes a Good Portfolio?) <<Contents | End>>