You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Functional Programming (FP) to write better, easier to reason about, easier to test and terser code
Abstract
What is functional programming and how can we use it (specifically tools like curry and pipe and higher-order functions) to better manage complexity, improve our understanding of our code and simplify our problem domain?
We'll go over the basics of functional programming in JS, hitting on some of the core tenets of the paradigm, highlight some of easier-to-fall-into pitfalls along the way and ways to write around them. Then we'll generally talk through the process of going from imperative code with implicit side-effects to functional code with explicit side-effects.
Hey hey @brekk, thanks for submitting a talk 🙌 Great topic. I've added you to our internal waitlist and we'll let you know when we'll be able to have you. Are you based in Berlin?
Talk title
Use Functional Programming (FP) to write better, easier to reason about, easier to test and terser code
Abstract
What is functional programming and how can we use it (specifically tools like
curry
andpipe
and higher-order functions) to better manage complexity, improve our understanding of our code and simplify our problem domain?We'll go over the basics of functional programming in JS, hitting on some of the core tenets of the paradigm, highlight some of easier-to-fall-into pitfalls along the way and ways to write around them. Then we'll generally talk through the process of going from imperative code with implicit side-effects to functional code with explicit side-effects.
The core content of the talk will definitely hit on the information framed in this article: https://codepen.io/brekk/post/functional-workaholism but will likely build on top of it a little bit as well.
Your name (and pronouns)
Brekk (He / Him)
Contact Details
Twitter @brekk
Github @brekk
Gitlab @brekk
BerlinJS Slack @brekk
;)
Code of Conduct
The text was updated successfully, but these errors were encountered: