Part1: Domain driven development in F# - Part2: Full-stack F# applications

Details

NOTE: this event is all going to be in English. Cet événement sera complètement en anglais.

Part 1: Safer development of business applications with functional domain driven development
Speaker: Kevin Olivier Avignon

Description:
We have all been there: what started as a simple billing engine for an e-commerce website rapidly becomes more complex than initially thought. The workflows are full of intricacies, the domain grows faster than expected and as time goes by, features get delivered more and more slowly as bugs are creepy their way in. In this case study, we will look at how F# helps tackle the complexity; its type system allows for a clean and intuitive representation of the domain, while keeping us from introducing all sorts of accidental bugs. In the end, it’s about giving us the freedom and some peace of mind when extending our models.

Bio:
My name is Kevin Avignon and I’m a robotics software developer at Hypertherm and my main focuses are functional development, performance and clean code. I’ve had a long passion for technology which drove me to get my undergrad in software engineering. On my spare time, I’m actively working with the F# community to push the language forward and working on side projects which let me test new ideas or are directly correlated with main interest.

Part 2: Build SAFE full-stack applications with F#
Speaker: Kevin Olivier Avignon

Description:
In the modern web applications, the issues are many. Developers must be expert of different stacks to be able impact the software. One of those issues is to be able to move from the back-end to the front-end using different languages which involves a lot of context switching and potentially duplicating code such as for validation, or introducing bugs by manually creating objects in a Javascript and sending them back to the server for it to handle. SAFE brings many technologies together into a single type-safe and flexible F# stack. It enables skill reuse since the models can be shared and all you’re required to know is F# for your next web application.

Bio:
Same as bio for Session#1