TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Technology

    Functional Design in Clojure

    Each week, we discuss a software design problem and how we might solve it using functional principles and the Clojure programming language.

    Advertise

    Copyright: © 2018-2019, Christoph Neumann and Nate Jones

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    Ep 079: Compose Thyself Jul 03, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "comp." We create a whole episode by combining examples of useful uses of comp.

    Selected quotes:

    • "It's the Voltron of functions."
    • "Our only tool for the job is functions."
    • "Getting your higher-order functional thinking going."
    • "Not only is it concise, it's really easy to understand, which is one of the awesome superpowers of Clojure."

    Links:

    • comp

    Related Episodes:

    • 061: Transcendental Transformations
    • 076: Multiple Views on Juxt
    • 078: Impartial Thoughts

    Ep 078: Impartial Thoughts Jun 19, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "partial." We cover some of the ways we use partial, without getting too literal.

    Selected quotes:

    • "We love punning so much, we pun in our code."
    • "It didn't help that I encountered this in academia."
    • "Not the function you have, but the function you need."
    • "I would use partial more if it wasn't so long."

    Links:

    • partial

    Episodes:

    • 014: Fiddle with the REPL

    Ep 077: Thread Some Jun 12, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "some-> and some->>." We spend some time going through how these macros help keep our code nil-safe.

    Selected quotes:

    • "Keep trying till you hit a nil and then stop."
    • "That seemed all well and good, and then I hit nil."
    • "It ends up being just a bit more concise."
    • "A nice way of testing something and then being able to use it right away."

    Links:

    • some->
    • some->>

    Ep 076: Multiple Views on Juxt Jun 05, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "juxt." We take a turn with juxt, looking at all the ways it can help line up data.

    Selected quotes:

    • "When it feels like core is missing something obvious, there's probably an idiom you need to learn."
    • "The way you become an excellent writer of Clojure is by reading excellent Clojure code."

    Links:

    • juxt
    • Advent 2019 part 4, A useful idiom
    • Bobby Towers' "Just Juxt" posts

    Episodes:

    • 012: Embrace the REPL
    • 013: Connect the REPL
    • 014: Fiddle with the REPL

    Ep 075: Merge With Fun May 22, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "merge-with." We focus in on merge-with, a powerful function for aggregating data.

    Selected quotes:

    • "We pick up idioms from other people."
    • "What sounds insane at face value actually starts to make a lot of sense."
    • "It's just a filter, you don't even have to write a function for that."
    • "The important part in the middle, where we might mess up, is all pure."
    • "We don't just have an O(n) problem, we have an 0(n) API calls problem."

    Links:

    • merge-with

    Episodes:

    • 047: What is "nil punning"?

    Ep 074: Deploy, They Said. It'll Be Fun, They Said. May 15, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "Deploying Clojure." We survey the myriad ways we've used to launch our code into production, and laugh about the various complexities we've found.

    Selected quotes:

    • "How do you get closure on the development of your Clojure code?"
    • "What do you mean by production?"
    • "Tomcat goes to war."
    • "That was back before containers."
    • "Trade a little bit of money for a lot of sanity."
    • "The problem with these things is the configuration you end up with is really simple after you've read 8 hours of documentation."
    • "The number of lines of code does not indicate the amount of effort."
    • "Every time you accept a new component into your system, you are also accepting its complexity."

    Ep 073: Silent Sockets Apr 17, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "Checking websocket health." We worry about the health of our websockets and, after looking for help from the standards bodies, roll up our sleeves and handle it ourselves.

    Selected quotes:

    • "It's the ghosting in the websocket world."
    • "With polling, every request is a fresh opportunity to recover from the last request's errors."
    • "Long polling is just beating the server up at a slower rate."
    • "By giving your code names with meaning, you can read the code that uses it and comprehend it faster."
    • "Complexity costs, and you pay in time and confusion."

    Related episodes:

    • 012: Embrace the REPL
    • 020: Data Dessert

    Ep 072: Sea of Sockets Apr 03, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "Organizing our websocket code." We switch to using a component to manage our websockets, enabling ease of development and future growth.

    Selected quotes:

    • "It feels like every time I use a global, a butterfly dies."
    • "We don't want to leave the REPL!"
    • "It's important to keep the abstraction un-leaky."
    • "When you lower the cognitive load of programming, that makes it more enjoyable."

    Ep 071: Socket Synergy Mar 20, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "Using websockets for notification." We wander into the weeds, jumping through the myriad hoops required to deliver a simple notification.

    Selected quotes:

    • "It's like we're taking a regular series and upgrading it somehow."
    • "Welcome to programming, where you'll spend hours diving into rabbit holes; and still love your work!"
    • "That sentence you just said sounds something they would say in a movie that would make all the programmers in the audience roll their eyes simultaneously."
    • "We just replaced one problem with another."

    Related episodes:

    • 053: How can I save my data from serialization?

    Ep 070: Socket Circus Mar 13, 2020
    Show notes

    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 feedback@clojuredesign.club, or join the #clojuredesign-podcast channel on the Clojurians Slack.

    This week, the topic is: "Websockets." We talk about spontaneously sending data from the server to the client to address our users' insecurities.

    Selected quotes:

    • "Classic engineering solution, let's just bend a couple of assumptions."
    • "Reloading the web page is 1995-style integration."
    • "Poll every tenth of a second? Yeah, that'll work till we need to scale past 4 users."
    • "In every engineering choice, there is always a tradeoff."

    Previous 1 3 4 5 6 7 12 Next

    Related Podcasts

    Reply All

    1

    Reply All Games & Hobbies
    Inside VR & AR

    2

    Inside VR & AR Gadgets
    Note to Self

    3

    Note to Self News
    BrainStuff

    4

    BrainStuff Natural Sciences
    This Week in Tech (Audio)

    5

    This Week in Tech (Audio) News
    Hands-On Tech (Audio)

    6

    Hands-On Tech (Audio) Technology
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights