Since I'm fresh back from php|cruise, I thought I'd comment and ask for
comments on what it takes to give a good technical presentation. I'm
planning on writing about this topic in my next php|architect column, so be
aware that anything said here may appear in it.
This is in no way a jab at any
--- John W. Holmes [EMAIL PROTECTED] wrote:
Since I'm fresh back from php|cruise, I thought I'd comment and ask
for comments on what it takes to give a good technical presentation.
I'm planning on writing about this topic in my next php|architect
column, so be aware that anything said here may
From: Chris Shiflett [EMAIL PROTECTED]
3) Typing Code: Don't type code during your presentation.
Why not? From my experience, people appreciate live demonstrations of the
techniques you're discussing.
Yeah, live demos are great, but I don't want to sit there and watch you type
all of your
--- John W. Holmes [EMAIL PROTECTED] wrote:
Yeah, live demos are great, but I don't want to sit there and watch
you type all of your PHP code. Have it already typed and just load
it, explain it, and run it.
I guess it depends. I agree with you on some level, but I have seen the
live demos
On Fri, 2004-03-19 at 15:53, John W. Holmes wrote:
1) Rehearse: This is a must. You have to run through your presentation a
couple times and preferably in front of other people so they can provide
feedback. Some people are really good at impromptu speaking and can wing it,
This is a valid
5 matches
Mail list logo
