How Functional Programming Made Me a Better Developer
Download as PPTX, PDF0 likes463 views
The document discusses how the Single Responsibility Principle (SRP) enhances development practices, drawing on functional programming principles. It presents examples of applications such as 'task snapper' and 'love letter' to illustrate the implementation of SRP in various programming contexts. Additionally, it emphasizes the importance of interfaces in enforcing code contracts and the interplay between boundaries, business rules, and workflows in application design.
How Functional Programming Made Me a Better Developer
- 1. Cameron Presley @pcameronpresley Cameron@TheSoftwareMentor.com How Functional Programming Made Me a Better Developer
- 2. 2 Hello!
- 3. 3
- 4. 4
- 5. “ The single responsibility principle states that every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class. -Wikipedia 5
- 6. “ The single responsibility principle states that every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class. -Wikipedia 6
- 7. What Happens If You Follow SRP to the Extreme? 7
- 8. 8
- 9. 9
- 10. 10
- 12. Extreme SRP and ISP = lots of fine grain classes 12
- 13. Objects can be thought of data with behavior, but what if we flipped that around? 13
- 14. 14 F#
- 15. 15
- 16. 16
- 17. Task Snapper ￮ C# application that grabs a screenshot every so often ￮ Focus on the language, not the problem 17
- 18. 18
- 19. 19
- 20. 20
- 21. 21
- 22. 22
- 23. 23
- 24. Love Letter ￮ 8 different kinds of cards, each with their own rules ￮ Write more idiomatic fp ￮ No classes or exceptions 24
- 25. 25
- 26. 26
- 27. 27
- 28. 28
- 29. 29
- 30. 30
- 31. Blackjack! ￮ Still modeling a card game ￮ Something with easier business rules ￮ Already knew the rules 31
- 32. 32
- 33. 33 How would you score a hand in Blackjack? Figure out how many Points each Card is worth Add the Points up
- 34. 34
- 35. 35
- 36. 36
- 37. 37
- 38. 38
- 39. 39
- 40. 40 different outputs the same output A method, that when given the same two inputs, it returns…
- 41. 41 Methods that always return output solely based on input are known to be pure
- 42. 42 Sound crazy? Elm React with Redux
- 43. 43
- 44. 44
- 45. 45
- 46. 46
- 47. 47
- 48. 48
- 49. 49
- 50. 50
- 51. 51
- 52. 52
- 53. 53 Interfaces are powerful because they enforce a contract at the code level. If the contract isn’t observed, the code won’t compile!
- 54. Given this interface, what should GetById return? Pop Quiz! Anything that implements this interface will always return an Employee object, right?
- 55. 55
- 56. 56
- 57. 57 What Happened? Interface said that an Employee will always be returned But sometimes, there won’t be an Employee, so what to return? Compiler can’t enforce that I handle null / exceptions
- 58. 58
- 59. 59
- 60. 60
- 61. 61
- 62. 62 Boundary (data in/out) Business Rules (processing the data) Workflow (combination of both)
- 63. Boundary ￮ Databases, files, APIs ￮ Typically impure ￮ For easier testing of workflows, recommend using an interface ￮ Inspiration from Alistair Cockburn’s Hexagonal Architecture 63
- 64. 64
- 65. 65
- 66. Business Rules ￮ Bulk of the application ￮ Purity is key ￮ Remember SOLID when implementing 66
- 67. 67
- 68. Workflows ￮ Combines both Boundary and Business Rule ￮ General shape is: ￮ Data comes in through the boundary ￮ Data is processed by the business rules ￮ Data goes out through the boundary 68
- 69. 69
- 70. 70
- 71. 71
- 72. 72
- 73. 73
- 74. 74
- 75. 75 References F# • F Sharp for Fun and Profit (https://fsharpforfunandprofit.com) • The Book of F#: Breaking Free with Managed Functional Programming by Dave Fancher • F# Jumpstart (Pluralsight Course) by Kit Eason Functional • Mark Seemann’s blog: (http://blog.ploeh.dk) • Hexagonal Architecture (post) by Alistair Cockburn • Reid Evans YouTube (https://www.youtube.com/channel/UCMxR2KmDlDMEsvfKOjzRNbA) Code • CRUDy : https://github.com/cameronpresley/CRUDy • Optionally: https://github.com/cameronpresley/Optionally
Editor's Notes
- #4: The Road Taken Learning Functional Programming (i.e. What Got Me Started Down This Path?)
- #5: Some SOLID Inspiration SOLID = Mnemonic for software designed By following SOLID we tend to write more maintainable software Want to focus on S (Single Responsibility Principle)
- #9: Lot of small classes with a single public method A lot of ceremony Could use ReSharper or another tool to create the boilerplate, but how about eliminate the need for it?
- #10: Asking the Twitterverse for help
- #12: Like most things in software development, I wasn’t the first to come to this
- #15: Chose F# Familiar with .NET Comfortable with the tooling Community resources
- #16: I worked on/off with functional for a year Lots of heads down, then come up for air for a bit Rinse and repeat Took three attempts for me to really “get” it
- #17: First Attempt!
- #18: Decided to port a C# application (Task Snapper) Grabs a screenshot every so often Idea was to focus on the language, not how to solve the problem
- #19: Defined a type Attached functions to it Some of those functions threw exceptions
- #20: Defined a type Attached functions to it Some of those functions threw exceptions
- #21: Defined a type Attached functions to it Some of those functions threw exceptions
- #22: Defined a type Attached functions to it Some of those functions threw exceptions
- #23: I wrote F# But wrote OO in FP Didn’t really see the point Need to learn more about FP
- #26: Look ma, no exceptions! Learned more about data modeling (making illegal states unrepresentable) Game rules a bit more complicated than expected *Spent a lot of time learning the problem and attempting a solution, not porting
- #27: Modeling Data and State using Discriminated Unions
- #28: Using type aliases
- #29: Making new types out of existing types using records
- #30: No classes, no exceptions!
- #31: 3rd Attempt
- #33: Making Illegal States Unrepresentable
- #35: Modeling how to turn a Card into a
- #36: How to add two points together
- #38: Reflection * Comfortable with handling errors without exceptions Using pattern matching more effectively Working with built-in List operators Map and Reduce Starting to think about how to use these concepts in C#
- #39: Learned all of this cool stuff, how does it affect my coding habits now?
- #40: Code is easy to test implies code is easy to maintain The opposite may hold then, hard to test code may not be maintainable What defines easy to test code?
- #41: What’s easier to test? Which method would be easier to troubleshoot?
- #42: Implies there are no side effects (databases, file systems, apis, etc…) Easiest thing to test because no dependencies are needed
- #43: Elm Architecture (time traveling debugger) React with Redux (reducers)
- #44: Pure because 3 will always return the same value
- #45: Not pure because the API could fail or give me back different values
- #46: Improved LINQ Skills
- #47: When working with lists of data, here’s how I’d used to do it Quickly, what am I trying to do here?
- #50: Before and after The one on the left, I have to keep track of what I’m doing The one on the right, I can trust that LINQ works and I’m plugging my business rules into the correct places
- #51: Designing Interfaces that don’t suck
- #54: Allows us to lean on the compiler
- #60: Why doesn’t this work? Options have no clue about Id, FirstName or LastName
- #61: Pattern match to figure out what to do. Compiler forced us to do that! Win!
- #62: How I build software
- #65: Getting data into the system
- #66: Getting data out of the system
- #75: Learning functional was hard for me Lots of failures, but improved incrementally Made me re-evaluate how I build software Still use functional concepts in my coding Even if I’m not using a functional language