Please log in to watch this conference skillscast.
Best practices always comes as snippets of advice. Nowadays you are told to be 'functional', 'immutable', 'pure', and 'reactive'. To really understand these buzzwords you need to go back to basics.
In this talk, we will strip back these terms to the fundamentals. By understanding what they solve and how they solve it you will be able to make a much more informed choice over which rules to apply to your software and when it is OK to break them. By the end of this talk, you will have discovered best-practices in a more refined light, and leave writing better code than before.
YOU MAY ALSO LIKE:
- What Colour is Your Function? Red vs Blue (SkillsCast recorded in November 2018)
- Functional Concurrency in .NET with C# and F# (in London on 9th - 10th September 2019)
- Fast Track to F# with Tomas Petricek & Phil Trelford (in London on 9th - 10th September 2019)
- Haskell eXchange 2019 (in London on 10th - 11th October 2019)
- Clojure eXchange 2019 (in London on 2nd - 3rd December 2019)
- Hands-on: Fractal art with Fable and WebGL (in London on 20th June 2019)
- Keynote by Dick Wall on Why API Design Matters, and Why Yours Sucks! (and mine sucks too!) (in London on 24th June 2019)
- The Elements of Tagless Final Style (SkillsCast recorded in May 2019)
- Scala 2.13 and Beyond! (SkillsCast recorded in April 2019)
Back to Basics aka 'When to Break Rules'
Rory spends his life fighting to find a balance between writing ugly high performance code and beautiful maintainable code. He fights from the trenches to make software better, contributing to open source and has has worked across the entire gamut of software from building a JVM to optimising grid computing.