On Thu, May 31, 2012 at 11:53 PM, C K Kashyap
Hi folks,
I have the opportunity to make a presentation to folks (developers and managers) in my organization about Haskell - and why it's important - and why it's the only way forward.
You (and we) may believe that but saying so usually does not work. What is more likely to work is talking to people about what interests them (rather than you :-) ). For example teachers of CS are usually struck by and bowled over by quicksort in 2 lines because for them teaching quicksort is considered an important activity. Professional object-oriented programmers are unlikely to take to such an 'academic' example kindly. Likewise those interested in algorithms and data-structures would be caught by a (tree) dfs in 1 line, or that a graph dfs and bfs are the same except that a [x] ++ pending becomes pending ++ [x] But if they were not so interested in algos and data-structures (Java programmers more than C++ are particularly prone to being using-happy, understanding-chary) this example would not work. So in short find what matters to your audience and then survey, focus and drill into that -- using Haskell
I request you to share your experiences/suggestions for the following - 1. Any thoughts around the outline of the presentation - target audience being seasoned imperative programmers who love and live at the pinnacle of object oriented bliss. 2. Handling questions/comments like these in witty/interesting ways - a) It looks good and mathematical but practically, what can we do with it, all our stuff is in C++ b) Wow, what do you mean you cannot reason about its space complexity? c) Where's my inheritance?
Yes you need to find a hot OO guru saying that inheritance is best avoided where templates/STL etc work d) Debugging looks like a nightmare - we cannot even put a print in the
function?
Maybe a (concocted) example of how the typechecker does most of the debugging for you? Better of course if the example is genuinely hacked out in front of the class (ideally from some thing they want to see solved) that can be convincing re things like debugging. This also brings up what is (for me) a very important point regarding haskell -- using an interpreter, ie ghci. -- the tight feedback loop -- not being bound to having to write a main -- the general sense of a workbench in which various objects (some joke here for the OO guys?) are are in different states of under construction to shrink-wrapped Personally I do not see how I could teach (or do) haskell without emacs. Admittedly this attracts some strongly and repels others equally strongly e) Static types - in this day and age - come on - productivity in X is
so much more - and that's because they got rid of type mess. f) Is there anything "serious/large" written in it? [GHC will not qualify as a good answer I feel] g) Oh FP, as in Lisp, oh, that's AI stuff right ... we don't really do AI. h) Any other questions/comments that you may have heard. 3. Ideas about interesting problems that can be used so that it appeals to people. I mean, while fibonacci etc look good but showing those examples tend to send the signal that it's good for "those kind" of problems. 4. Is talking about or referring to Lambda calculus a good idea - I mean, showing that using its ultra simple constructs one could build up things like if/then etc
I'm gonna do my bit to wear the limestone!!!
Regards, Kashyap
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe