Meetup: http://bit.ly/1VOG3eT
Book: http://bit.ly/1Lhaxfo
Slides: http://bit.ly/1G1QPHK
Audio: http://bit.ly/1jzWz0J

-------------------------------------------------------------------------------------
Sponsored by Two Sigma (@twosigma).
-------------------------------------------------------------------------------------

Description
------------------
How is computer science research done? What we take for granted and what we question? And how do theories in computer science tell us something about the real world? Those are some of the questions that may inspire computer scientist like me (and you!) to look into philosophy of science. I’ll present the work of one of the more extreme (and interesting!) philosophers of science, Paul Feyerabend. In “Against Method”, Feyerabend looks at the history of science and finds that there is no fixed scientific methodology and the only methodology that can encompass the rich history is ‘anything goes’. We see (not only computer) science as a perfect methodology for building correct knowledge, but is this really the case? To quote Feyerabend:

"Science is much more 'sloppy' and 'irrational' than its methodological image."

I’ll be mostly talking about Paul Feyerabend’s “Against Method”, but as a computer scientist myself, I’ll insert a number of examples based on my experience with theoretical programming language research. I hope to convince you that looking at philosophy of science is very much worthwhile if we want to better understand what we do and how we do it as computer scientists!

Bio
-----
Tomas Petricek (@tomaspetricek) recently submitted his PhD thesis at University of Cambridge on context-aware programming languages. He is active in the functional programming community, contributes to various F# open-source libraries, writes and talks about F# and offers trainings and consulting at fsharpWorks. When he isn’t writing equations or code, he enjoys reading philosophy of science books and occasionally publishes an essay combining philosophy and computer science.