Artwork

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

Ep 095: Composing Core

17:37
 
공유
 

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

Each week, we discuss a different topic about Clojure and functional programming.

If you have a question or topic you'd like us to discuss, tweet @clojuredesign, send an email to [email protected], or join the #clojuredesign-podcast channel on the Clojurians Slack.

This week, the topic is: "core and composition." We venture toward the core of a solution.

Our discussion includes:

  • Why do functional programmers like to talk about composition?
  • What composition means in object-oriented programming vs functional programming.
  • Must simple be simplistic?
  • What is idiomatic composition?
  • Common kinds of functions.
  • Why functional programming is more like Legos than taxonomies.
  • What Clojure already knows and what you have to teach it.
  • Why Clojure allows you to put things together quickly.
  • Why side effects can ruin everything.
  • How Clojure encourages composition.

Selected quotes:

  • "I don't think you want me to read code to you. That sounds like an excellent way to fall asleep if you have insomnia!"
  • "Maybe we need a white noise track of keyboard noise."
  • "Composition in a functional language is much simpler because we just have functions."
  • "Why have we spent so much time talking about composition when it's just functions calling other functions?"
  • "These names are a little on the nose, but programmers aren't always the best at originality!"
  • "Functional programming is essentially based on transformation. Everything is a transform at some point in time."
  • "The only way to get anything done is to return a new thing."
  • "Core is a backbone, a spine, and you're connecting a progression of things together."
  • "Your job, as a functional developer, is to teach Clojure core about your domain."
  • "They're all functions that remix very well."
  • "Everything must be pure because side effects mess up this whole world."
  • "Make functions small because functional programming makes it very easy to combine smaller functions into bigger functions. Build up your functionality from those pieces."

Links:

  continue reading

118 에피소드

Artwork

Ep 095: Composing Core

Functional Design in Clojure

72 subscribers

published

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

Each week, we discuss a different topic about Clojure and functional programming.

If you have a question or topic you'd like us to discuss, tweet @clojuredesign, send an email to [email protected], or join the #clojuredesign-podcast channel on the Clojurians Slack.

This week, the topic is: "core and composition." We venture toward the core of a solution.

Our discussion includes:

  • Why do functional programmers like to talk about composition?
  • What composition means in object-oriented programming vs functional programming.
  • Must simple be simplistic?
  • What is idiomatic composition?
  • Common kinds of functions.
  • Why functional programming is more like Legos than taxonomies.
  • What Clojure already knows and what you have to teach it.
  • Why Clojure allows you to put things together quickly.
  • Why side effects can ruin everything.
  • How Clojure encourages composition.

Selected quotes:

  • "I don't think you want me to read code to you. That sounds like an excellent way to fall asleep if you have insomnia!"
  • "Maybe we need a white noise track of keyboard noise."
  • "Composition in a functional language is much simpler because we just have functions."
  • "Why have we spent so much time talking about composition when it's just functions calling other functions?"
  • "These names are a little on the nose, but programmers aren't always the best at originality!"
  • "Functional programming is essentially based on transformation. Everything is a transform at some point in time."
  • "The only way to get anything done is to return a new thing."
  • "Core is a backbone, a spine, and you're connecting a progression of things together."
  • "Your job, as a functional developer, is to teach Clojure core about your domain."
  • "They're all functions that remix very well."
  • "Everything must be pure because side effects mess up this whole world."
  • "Make functions small because functional programming makes it very easy to combine smaller functions into bigger functions. Build up your functionality from those pieces."

Links:

  continue reading

118 에피소드

모든 에피소드

×
 
Loading …

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

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

 

빠른 참조 가이드

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