Artwork

Jim McQuillan & Wolf and Jim McQuillan에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Jim McQuillan & Wolf and Jim McQuillan 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.
Player FM -팟 캐스트 앱
Player FM 앱으로 오프라인으로 전환하세요!

4: Functional Programming - You're probably already doing it

28:57
 
공유
 

Manage episode 488754284 series 3660315
Jim McQuillan & Wolf and Jim McQuillan에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Jim McQuillan & Wolf and Jim McQuillan 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

People throw around the term Functional Programming but it's not always clear what they mean. In this episode, Wolf explains what goes into FP, and together we build a clearer picture that reveals you might already be doing it.

Show notes and things to think about:

  1. Functional programing isn't academic. It isn't overwhelming. It isn't impossible to use. It isn't inapplicable to ordinary problems like the ones you're solving right now.
  2. You can use functional techniques in almost any modern programming language. In fact, you probably already are.
  3. Main pillars of FP:
    1. Pure functions (no side-effects)
    2. Functions are first-class objects (you can pass them as arguments, you can return them as results, you can store them in lists or any other data-structure)
    3. Data is immutable by default
    4. FP languages often provide powerful pattern matching syntax (didn't mention this much in the episode other than briefly noting Python's new match statement)
    5. A couple of things not mentioned: in FP, your code is more about what you want, not about how to get it. That stack of functions for the sales data example looks declarative, not imperative.
    6. A couple of other things not mentioned: recursion and lazy evaluation. Not exclusive to FP, but very often available in functional languages.
  4. Papers and explanations about monads might be unreadable, but you're already using them and you already know how they work.
  5. Using FP techniques appropriately can make your code easier to test, harder to break, and possibly even prettier to look at.
  6. There are places in your code right now that you can make better right now with FP. Do it!

Links:

  • We mentioned a ton of languages. Most of them have easy to find home pages so I'm not going to list out all the links; but there are a couple of obscure ones

Hosts:
Jim McQuillan can be reached at [email protected]
Wolf can be reached at [email protected]
Follow us on Mastodon: @[email protected]
If you have feedback for us, please send it to [email protected]
Theme music:
Dawn by nuer self, from the album Digital Sky

  continue reading

18 에피소드

Artwork
icon공유
 
Manage episode 488754284 series 3660315
Jim McQuillan & Wolf and Jim McQuillan에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Jim McQuillan & Wolf and Jim McQuillan 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

People throw around the term Functional Programming but it's not always clear what they mean. In this episode, Wolf explains what goes into FP, and together we build a clearer picture that reveals you might already be doing it.

Show notes and things to think about:

  1. Functional programing isn't academic. It isn't overwhelming. It isn't impossible to use. It isn't inapplicable to ordinary problems like the ones you're solving right now.
  2. You can use functional techniques in almost any modern programming language. In fact, you probably already are.
  3. Main pillars of FP:
    1. Pure functions (no side-effects)
    2. Functions are first-class objects (you can pass them as arguments, you can return them as results, you can store them in lists or any other data-structure)
    3. Data is immutable by default
    4. FP languages often provide powerful pattern matching syntax (didn't mention this much in the episode other than briefly noting Python's new match statement)
    5. A couple of things not mentioned: in FP, your code is more about what you want, not about how to get it. That stack of functions for the sales data example looks declarative, not imperative.
    6. A couple of other things not mentioned: recursion and lazy evaluation. Not exclusive to FP, but very often available in functional languages.
  4. Papers and explanations about monads might be unreadable, but you're already using them and you already know how they work.
  5. Using FP techniques appropriately can make your code easier to test, harder to break, and possibly even prettier to look at.
  6. There are places in your code right now that you can make better right now with FP. Do it!

Links:

  • We mentioned a ton of languages. Most of them have easy to find home pages so I'm not going to list out all the links; but there are a couple of obscure ones

Hosts:
Jim McQuillan can be reached at [email protected]
Wolf can be reached at [email protected]
Follow us on Mastodon: @[email protected]
If you have feedback for us, please send it to [email protected]
Theme music:
Dawn by nuer self, from the album Digital Sky

  continue reading

18 에피소드

모든 에피소드

×
 
Loading …

플레이어 FM에 오신것을 환영합니다!

플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.

 

빠른 참조 가이드

탐색하는 동안 이 프로그램을 들어보세요.
재생