Thinking Like a Programmer (means what?)

An anonymous reader writes: I've been asked to put together a half-day workshop whose title is 'Thinking Like a Programmer'.

The idea behind this is that within my institution (a university), we have a vast number of self-taught programmers who have never been taught 'best practice' or anything about software engineering. This workshop's intention is to address this lack of formal training.

So, the question is, what should be covered in this workshop?

If you have an idea — that also has an example of best practice — please share (I'm sure we'll all learn something)!