Tomas Petricek

Searching for new ways of thinking in programming & working with data

I believe that the most interesting work is not the one solving hard problems, but the one changing how we think about the world. I follow this belief in my work on data science tools, functional programming and F# teaching, in my programming languages research and I try to understand it through philosophy of science.

The Gamma

I'm working on making data-driven storytelling easier, more open and reproducible at the Alan Turing Institute.

Consulting

I'm author of definitive F# books and open-source libraries. I offer my F# training and consulting services as part of fsharpWorks.

Academic

I published papers about theory of context-aware programming languages, type providers, but also philosophy of science.

Tomas Petricek
  • Tomas Petricek
  • Home
  • F# Trainings
  • Talks and books
  • The Gamma
  • Academic

F# in Academia: Present at upcoming events!

The F# language was born as a combination of the pragmatic and real-world .NET platform and functional programming, which had a long tradition in academia. Many useful ideas or libraries in F# (like asynchronous workflows and first-class events) are inspored by research in functional programming (namely, the work on monads, continuations and functional reactive programming).

Exchanging the ideas between the research community and the real-world is one of the areas where F# excels. Indeed, the first applicatiosn of F# inside Microsoft (in the Machine Learning group at Cambridge) were all about this - combining research in machine learning with a language that can be easily used in practice.

However, F# and the F# users also made numerous contributions to the programming language research community. Influential ideas that come from F# include active patterns and the F# style of meta-programming for translating F# to JavaScript). I think there is a lot more that the academic community can learn from the F# community, so I'd like to invite you to talk about your ideas at two upcoming academic events!

What, why, when, where and how!

  • What? Do you have some interesting experience to report? Do you have an interesting F# DSL or novel application? Can you compare your experience with F# and other languages? Or do you have some interesting extension for F#?

  • Why? Collaboration between researchers and practitioners is just important! Presenting your experience can influence researchers to improve languages in a useful way. You can get useful feedback from people who think about problems in a different, but interesting way!

  • When & Where? Both of the events are co-located with ICFP 2012 in September 2012 in Copenhagen. This is one of the largest functional conferences, so you can learn about some interesting ideas from the research world too!

  • How? Both of the events are quite informal, so you don't need to write an academic paper! For CUFP, you just need talk abstract and for ML Workshop, you need to write 2 page summary (see below for details).

Commercial Uses of Functional Programming

To quote the official CUFP announcement, "The annual CUFP workshop is a place where people can see how others are using functional programming to solve real world problems". The workshop is looking for presenters who have interesting experience with using functional programming in commercial sector. There are two kinds of talks, both should be about 25 minutes long:

  • Experience reports - explaining how you used functional programming in practice, what worked well and what were the difficulties; these talks can also discuss interesting non-technical aspects.

  • Technical talks - these talks should focus on some interesting technology or on some interesting application of functional programming. For example, how to solve certain difficult problems, how to build scalable solutions etc.

For some inspiration, you can take a look at videos from the last year. If you are interested in offering a talk, send an e-mail to sperber(at)deinprogramm(dot)de or avsm2(at)cl(dot)cam(dot)ac(dot)uk by 29 June 2012 with a roughly 1 page description of what you'd like to talk about. If you want to discuss an potential F# topic informally first, get in touch with me at tomas@tomasp.net.

ML Workshop

The other event that may be interesting to F# programmers is Workshop on ML (see official announcement). Traditionally, the workshop has been focused mainly on research around ML, OCaml and F#. However, this year, it also welcomes practical topics. To quote the announcement: "This workshop aims to provide a forum where users, developers and researchers of ML languages and related technology can interact and discuss ongoing research, open problems and innovative applications."

You can contribute one of the following three kinds of talks:

  • Research presentation - describe new research related to ML (or F#), including work in progress and outline of possible research directions.

  • Experience reports - present interesting story about an application of ML-style language; this may include innovative or unexpected use of some interesting aspects of the language.

  • Demos - demonstrations or short tutorials of new tools, libraries or applications developed for, or using ML-style languages.

If you're interested in presenting your ideas at the ML workshop, you should write a brief description of the idea (up to 2 pages) and submit that to the submission web site before 4 June 2012. Again, if you'd like to get some informal feedback before the submission, feel free to get in touch: tomas@tomasp.net.

Published: Monday, 16 April 2012, 12:19 AM
Author: Tomas Petricek
Typos: Send me a pull request!
Tags: presentations, f#, haskell, research

Contact & about

This site is hosted on GitHub and is generated using F# Formatting and DotLiquid. For more info, see the website source on GitHub.

Please submit issues & corrections on GitHub. Use pull requests for minor corrections only.

  • Twitter: @tomaspetricek
  • GitHub: @tpetricek
  • Email me: tomas@tomasp.net

Blog archives

October 2020 (1),  July 2020 (1),  April 2020 (2),  December 2019 (1),  February 2019 (1),  November 2018 (1),  October 2018 (1),  May 2018 (1),  September 2017 (1),  June 2017 (1),  April 2017 (1),  March 2017 (2),  January 2017 (1),  October 2016 (1),  September 2016 (2),  August 2016 (1),  July 2016 (1),  May 2016 (2),  April 2016 (1),  December 2015 (2),  November 2015 (1),  September 2015 (3),  July 2015 (1),  June 2015 (1),  May 2015 (2),  April 2015 (3),  March 2015 (2),  February 2015 (1),  January 2015 (2),  December 2014 (1),  May 2014 (3),  April 2014 (2),  March 2014 (1),  January 2014 (2),  December 2013 (1),  November 2013 (1),  October 2013 (1),  September 2013 (1),  August 2013 (2),  May 2013 (1),  April 2013 (1),  March 2013 (1),  February 2013 (1),  January 2013 (1),  December 2012 (2),  October 2012 (1),  August 2012 (3),  June 2012 (2),  April 2012 (1),  March 2012 (4),  February 2012 (5),  January 2012 (2),  November 2011 (5),  August 2011 (3),  July 2011 (2),  June 2011 (2),  May 2011 (2),  March 2011 (4),  December 2010 (1),  November 2010 (6),  October 2010 (6),  September 2010 (4),  July 2010 (3),  June 2010 (2),  May 2010 (1),  February 2010 (2),  January 2010 (3),  December 2009 (3),  July 2009 (1),  June 2009 (3),  May 2009 (2),  April 2009 (1),  March 2009 (2),  February 2009 (1),  December 2008 (1),  November 2008 (5),  October 2008 (1),  September 2008 (1),  June 2008 (1),  March 2008 (3),  February 2008 (1),  December 2007 (2),  November 2007 (6),  October 2007 (1),  September 2007 (1),  August 2007 (1),  July 2007 (2),  April 2007 (2),  March 2007 (2),  February 2007 (3),  January 2007 (2),  November 2006 (1),  October 2006 (3),  August 2006 (2),  July 2006 (1),  June 2006 (3),  May 2006 (2),  April 2006 (2),  December 2005 (1),  July 2005 (4),  June 2005 (5),  May 2005 (1),  April 2005 (3),  March 2005 (3),  January 2005 (1),  December 2004 (3),  November 2004 (2), 

License

Unless explicitly mentioned, all articles on this site are licensed under Creative Commons Attribution Share Alike. All source code samples are licensed under the MIT License.

CC License logo