Download to read offline
More Related Content
Similar to Do you even Function? Guiding Through Functional Interfaces
More from Dmitry Vinnik
Do you even Function? Guiding Through Functional Interfaces
- 1. Dmitry Vinnik @DmitryVinnik dvinnik.com Doyou even Function? Guiding Through Functional Interfaces
- 2. What are ourgoals? @DmitryVinnik dvinnik.com
- 3. Goals Functional Programming (FP): What,How, When and Why Default FP Capabilities in Java Custom Functional Solutions
- 4.
- 5.
- 6.
- 7.
- 8. Concurrency is a NewReality @DmitryVinnik dvinnik.com
- 9. Concurrency is a Reality @DmitryVinnikdvinnik.com
- 10.
- 11. What’s in itfor us? @DmitryVinnik dvinnik.com
- 12. Benefits No Idling ↑UX Abstraction @DmitryVinnik dvinnik.com
- 13. Only good parts,right? @DmitryVinnik dvinnik.com
- 14.
- 15. How do wetackle it? @DmitryVinnik dvinnik.com
- 16.
- 17.
- 18. Design for FP Designby Contract Temporal Coupling Immutability & Atomicity Lazy Evaluation Lazy Evaluation No Temporal Coupling Immutability & Atomicity @DmitryVinnik dvinnik.com
- 19. Design by Contract @DmitryVinnikdvinnik.com
- 20. “Require No More, PromiseNo Less” Quote from Bertrand Meyer, “Design by Contract” @DmitryVinnik dvinnik.com
- 21. Design by Contract @DmitryVinnikdvinnik.com
- 22. Design for FP Designby Contract Temporal Coupling Immutability & Atomicity Lazy Evaluation Lazy Evaluation No Temporal Coupling Immutability & Atomicity @DmitryVinnik dvinnik.com Design by Contract Lazy Evaluation
- 23.
- 24. "Lazy Evaluation islike Filing Taxes" Quote from Venkat Subramaniam, “Let’s Get Lazy” @DmitryVinnik dvinnik.com
- 25.
- 26. Design for FP Designby Contract Temporal Coupling Immutability & Atomicity Lazy Evaluation Lazy Evaluation No Temporal Coupling Immutability & Atomicity @DmitryVinnik dvinnik.com Design by Contract Lazy Evaluation Lazy Evaluation No Temporal Coupling
- 27.
- 28. “When time &order really matter” @DmitryVinnik dvinnik.com
- 29.
- 30.
- 31.
- 32.
- 33. Design for FP Designby Contract Temporal Coupling Immutability & Atomicity Lazy Evaluation Lazy Evaluation No Temporal Coupling Immutability & Atomicity @DmitryVinnik dvinnik.com Design by Contract Lazy Evaluation Lazy Evaluation No Temporal Coupling No Temporal Coupling Immutability & Atomicity
- 34.
- 35.
- 36. How would wewrite Functional Code? @DmitryVinnik dvinnik.com
- 37. Let’s consider twostyles: Imperative and Declarative @DmitryVinnik dvinnik.com
- 38. Assume a UseCase: Searching for a word in a phrase @DmitryVinnik dvinnik.com
- 39.
- 40.
- 41. Styles Side bySide @DmitryVinnik dvinnik.com
- 42. Benefits of Declarative Style ↑Readability ↓ Verbosity↓ Complexity ↓ Verbosity ↑ Readability @DmitryVinnik dvinnik.com
- 43.
- 44. Benefits of Declarative Style ↑Readability ↓ Verbosity↓ Complexity ↓ Verbosity ↑ Readability @DmitryVinnik dvinnik.com ↓ Complexity ↓ Verbosity
- 45.
- 46.
- 47.
- 48. Benefits of Declarative Style ↑Readability ↓ Verbosity↓ Complexity ↓ Verbosity ↑ Readability @DmitryVinnik dvinnik.com ↓ Complexity ↓ Verbosity↓ Verbosity ↑ Readability
- 49.
- 50.
- 51.
- 52.
- 53.
- 54. Let’s see someFP in Java @DmitryVinnik dvinnik.com
- 55. Starting from theBase @DmitryVinnik dvinnik.com
- 56. Stream Optional Starting from theBase @DmitryVinnik dvinnik.com
- 57. What do wedo the most? @DmitryVinnik dvinnik.com
- 58. Dealing with Data @DmitryVinnikdvinnik.com
- 59. Dealing with Collections @DmitryVinnikdvinnik.com
- 60. How do weget Functional with Collections? @DmitryVinnik dvinnik.com
- 61.
- 62.
- 63. That’s all great @DmitryVinnikdvinnik.com
- 64.
- 65. What if Iwant to find something? @DmitryVinnik dvinnik.com
- 66. Optional is theanswer @DmitryVinnik dvinnik.com
- 67. Finding Optional Talk @DmitryVinnikdvinnik.com
- 68.
- 69.
- 70.
- 71. But it stillseems verbose @DmitryVinnik dvinnik.com
- 72. Method Reference to theRescue! @DmitryVinnik dvinnik.com
- 73. What is itgood for? @DmitryVinnik dvinnik.com
- 74. “There are onlytwo hard things in Computer Science: Cache Invalidation and Naming Things” Quote from Phil Karlton @DmitryVinnik dvinnik.com
- 75. Method Reference: Before @DmitryVinnikdvinnik.com
- 76. Why do weneed temporary variables? @DmitryVinnik dvinnik.com
- 77. Method Reference: After @DmitryVinnikdvinnik.com
- 78.
- 79.
- 80. But what about FunctionalProgramming and Debugging @DmitryVinnik dvinnik.com
- 81. One Line perStatement Style @DmitryVinnik dvinnik.com
- 82. Now we haveall the tools @DmitryVinnik dvinnik.com
- 83. Let’s Get Functional @DmitryVinnikdvinnik.com
- 84. High Order(HO) Functions Functions asFirst Class Entities Functions as Input Functions as Output @DmitryVinnik dvinnik.com
- 85. Why HO Functions? ↑Abstraction DRY by Design ↓ Complexity ↑ Readability @DmitryVinnik dvinnik.com
- 86. Are all Functionsequal? @DmitryVinnik dvinnik.com
- 87.
- 88.
- 89. Pure Functions Immutable SideEffects Same Input Same Output @DmitryVinnik dvinnik.com
- 90.
- 91. Let’s see Functions inAction @DmitryVinnik dvinnik.com
- 92. Let’s see Functions inJava @DmitryVinnik dvinnik.com
- 93.
- 94.
- 95. High Order Functions Out-of-the-Box Function<T,R> Predicate<T> Consumer<T> Supplier<T> Predicate<T> Consumer<T> Supplier<T> @DmitryVinnik dvinnik.com
- 96. Function<T, R> @DmitryVinnik dvinnik.com OneOutputOne Input
- 97.
- 98.
- 99.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107. High Order Functions Out-of-the-Box Function<T,R> Predicate<T> Consumer<T> Supplier<T> Predicate<T> Consumer<T> Supplier<T> @DmitryVinnik dvinnik.com Function<T, R> Predicate<T>
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115.
- 116.
- 117.
- 118.
- 119. High Order Functions Out-of-the-Box Function<T,R> Predicate<T> Consumer<T> Supplier<T> Predicate<T> Consumer<T> Supplier<T> @DmitryVinnik dvinnik.com Function<T, R> Predicate<T>Predicate<T> Consumer<T>
- 120.
- 121.
- 122.
- 123.
- 124.
- 125.
- 126.
- 127.
- 128.
- 129. High Order Functions Out-of-the-Box Function<T,R> Predicate<T> Consumer<T> Supplier<T> Predicate<T> Consumer<T> Supplier<T> @DmitryVinnik dvinnik.com Function<T, R> Predicate<T>Predicate<T> Consumer<T>Consumer<T> Supplier<T>
- 130.
- 131.
- 132.
- 133.
- 134.
- 135.
- 136.
- 137.
- 138. Summary High Order Functions @DmitryVinnikdvinnik.com
- 139. Function<T, R> Consumer<T> Data Transformation Predicate<T> DataFiltering Data Processing Supplier<T> Process Execution
- 140. Out-of-the-Box is nice @DmitryVinnikdvinnik.com
- 141. But what aboutCustom Functional Use Cases? @DmitryVinnik dvinnik.com
- 142. Let’s Build Custom FunctionalInterface @DmitryVinnik dvinnik.com
- 143.
- 144. What about some CommonUse Cases? @DmitryVinnik dvinnik.com
- 145.
- 146. FP: Error Handling @DmitryVinnikdvinnik.com
- 147. FP: Error Handling @DmitryVinnikdvinnik.com
- 148. FP: Error Handling @DmitryVinnikdvinnik.com
- 149.
- 150. FP: Error Handling @DmitryVinnikdvinnik.com
- 151. FP: Error Handling @DmitryVinnikdvinnik.com
- 152. FP: Error Handling @DmitryVinnikdvinnik.com
- 153.
- 154. FP: Error Passing @DmitryVinnikdvinnik.com
- 155.
- 156.
- 157.
- 158. But is thereanything to be avoided? @DmitryVinnik dvinnik.com
- 159.
- 160. Call For Action EmbraceFP Review Your Application Continue Learning @DmitryVinnik dvinnik.com
- 161.
- 162. About Speaker Twitter: @DmitryVinnik Blog:dvinnik.com LinkedIn: in/dmitry-vinnik/ Email: dmitry@dvinnik.com
Editor's Notes
- #5 How many of you have Macbook Pro? How many of you used AWS/Azure? Have you heard about Microservices
- #6 How many of you have Macbook Pro? How many of you used AWS/Azure? Have you heard about Microservices
- #7 How many of you have Macbook Pro? How many of you used AWS/Azure? Have you heard about Microservices Source: The Next Platform
- #8 Change or die situation at this point World perspective
- #9 Change or die situation at this point World perspective
- #10 Change or die situation at this point World perspective
- #19 “Always Design for Concurrency” - Pragmatic Programmer
- #23 “Always Design for Concurrency” - Pragmatic Programmer
- #27 “Always Design for Concurrency” - Pragmatic Programmer
- #28 Good example is http clienta
- #29 Good example is http clienta
- #30 Good example is http clienta
- #31 Good example is http clienta
- #32 Good example is http clienta
- #33 Good example is http clienta
- #34 “Always Design for Concurrency” - Pragmatic Programmer
- #43 Especially Complexity of Concurrency
- #45 Especially Complexity of Concurrency
- #49 Especially Complexity of Concurrency
- #63 Not a data stracture Cannot reuse
- #70 Note how field is not optional Always check before invoking get()
- #85 https://softwareengineering.stackexchange.com/questions/39742/when-is-a-feature-considered-a-first-class-citizen-in-a-programming-language-p
- #87 Java so flexible, need to be extra careful
- #88 Java so flexible, need to be extra careful
- #89 Java so flexible, need to be extra careful
- #94 Even Runnable is FI Annotation is optional
- #96 High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ... High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ...
- #108 High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ... High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ...
- #120 High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ... High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ...
- #130 High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ... High Order Function Javadoc Function<T, R> Represents a function that accepts one argument and produces a result Predicate<T> Represents a predicate (boolean-valued function) of one argument Consumer<T> Represents an operation that accepts a single input argument and returns no result Supplier<T> Represents a supplier of results ... ...
- #131 The simplest one Use as Executor
- #132 The simplest one Use as Executor
- #133 The simplest one Use as Executor
- #134 The simplest one Use as Executor
- #135 The simplest one Use as Executor
- #136 The simplest one Use as Executor
- #137 The simplest one Use as Executor
- #138 The simplest one Use as Executor
- #141 Making next step in FP
- #142 Making next step in FP
- #147 diffplug/durian
- #148 diffplug/durian
- #149 diffplug/durian
- #151 diffplug/durian
- #152 diffplug/durian
- #153 diffplug/durian
- #155 jOOQ/jOOL
- #157 jOOQ/jOOL
- #160 Early Optimization (Streams, or Parallel Streams)
- #161 Need to embrace, move java 9,10,11 Look at reactive