Ep 111: Loopify!

Functional Design in Clojure

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.

2y ago 28:54

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: "trying again". We throw our code in a loop, and it throws us for a loop.

It's a lot like having a project on a workbench. You have all of the tools and all the information laid out before you on that workbench. Nothing is tucked in a drawer or inside a cabinet.
That's a very important lesson for any developer: you can always stop—at least after it's working.
Nothing in the world is solved except by adding another level of abstraction.
I was not expecting that level of mutation! I was expecting a Kafka log written in stone!
The positive is it has everything. The negative is it has everything.
We would like more loop-native code inside of our cloud-native application.
Are you suggesting that just because we can, it doesn't mean we should? We're programmers! If the language lets us do it, it must be a good idea!
One of the reasons why I like Clojure is because it specifically tells me that I can't do some things that are bad to do.
All of the context is in one map. It has everything in it. One map to rule them all!
Might this be the fabled "single application state"?
We have the thinking function, the doing function, and the assimilate function.

72 subscribers

published 2y ago

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: "trying again". We throw our code in a loop, and it throws us for a loop.

It's a lot like having a project on a workbench. You have all of the tools and all the information laid out before you on that workbench. Nothing is tucked in a drawer or inside a cabinet.
That's a very important lesson for any developer: you can always stop—at least after it's working.
Nothing in the world is solved except by adding another level of abstraction.
I was not expecting that level of mutation! I was expecting a Kafka log written in stone!
The positive is it has everything. The negative is it has everything.
We would like more loop-native code inside of our cloud-native application.
Are you suggesting that just because we can, it doesn't mean we should? We're programmers! If the language lets us do it, it must be a good idea!
One of the reasons why I like Clojure is because it specifically tells me that I can't do some things that are bad to do.
All of the context is in one map. It has everything in it. One map to rule them all!
Might this be the fabled "single application state"?
We have the thinking function, the doing function, and the assimilate function.

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