My version would be slightly bigger-picture (some are the same as yours, though): - Functional design is about breaking a problem up into a series of transform

My version would be slightly bigger-picture (some are the same as yours, though): - Functional design is about breaking a problem up into a series of transformations (functions) on data, rather than modelling object states and behaviors. - Compose the transformations by treating functions as first-class citizens. Introduce map, filter, foldr, etc. here - "Functional" = Avoid side-effects! (wrap an I/O layer around your pure core processing instead) Otherwise the composing breaks. (optional): - "Start little, grow big", "factor relentlessly" - these are good concepts in ALL programming, and they apply here too. I think if you just get those points in an hour, along with a nice example (I think F# comes with a web crawler that illustrates all these points), you'll have done very well.