2.0 Updates:

Showing computer code

P = presenter

  1. P briefly gives the context for a piece of code, explains why it is interesting.

  2. P Shows code.

  3. Displayed code has the following properties:

    • It is interesting code, or somehow recommends the group as highly skilled coders

    • It has very clear header—and in-line—comments. Don't shoot yourself in the foot with no comments!

    • The font is large and easy to read.

    • The code is interesting to technical people, but can be understood in a general way, by "money" people.

  4. P teaches some aspect of the code. Explain in a way that is not boring for technical people (possibly because it is interesting code on a novel idea), but yet also conveys information to non-technical people who feel they have learned something. It can be good to give references to resource web sites, etc. that can be "stolen" from you, even if the project is not adopted.

  5. It is best to not spend too much time on code.

  6. Notes: In a short amount of time you can convince technical people that you are very good at what you do, you can get everyone's attention by teaching some small part of what you did. You can "slide in" the point that you write well-documented, self-describing, code which is easy to maintain. The whole process can be completed in about three minutes.