Christoph Neumann and Nate Jones public
[search 0]
×
Best Christoph Neumann and Nate Jones podcasts we could find (updated April 2020)
Best Christoph Neumann and Nate Jones podcasts we could find
Updated April 2020
Join millions of Player FM users today to get news and insights whenever you like, even when you're offline. Podcast smarter with the free podcast app that refuses to compromise. Let's play!
Join the world's best podcast app to manage your favorite shows online and play them offline on our Android and iOS apps. It's free and easy!
More
show episodes
 
Loading …
show series
 
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 usi…
 
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 in…
 
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…
 
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: “Request handler pitfalls.” We examine our histor…
 
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: “Serving static assets.” We tease apart the layer…
 
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: “Resource management for web handlers.” We manage…
 
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: “Making middleware to handle JSON.” We reinvent t…
 
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: “Ring middleware.” We find that the middle is a v…
 
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: “Ring, the foundation of Clojure HTTP” We focus o…
 
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: “HTTP and the Web of Complexity.” We launch a new…
 
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: “2019.” We look back at the past year and highlig…
 
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: “Transducers.” We unpack transducers and find a f…
 
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: “Reducers.” We look at clojure.core.reducers and …
 
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: “Sequences.” We examine the sequence abstraction …
 
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: “Reduce and reducing functions” We take a long ha…
 
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: “Clojure/Conj 2019 Recap” We go through our 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: “Opt-In Complexity” We discuss complexity and try…
 
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: “Sets! What are they good for?” We examine one of…
 
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: “Working with heavily nested trees.” We discuss t…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “How can I save my data from serialization?” We recor…
 
Each week, we discuss a different topic about Clojure and functional programming. If you have a question 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, our topic is: “Functions! Functions! Functions!” We wonder how we could …
 
Each week, we discuss a different topic about Clojure and functional programming. If you have a question 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, our topic is: “Maps! Maps! Maps!” We discuss maps and their useful featu…
 
Each week, we discuss a different topic about Clojure and functional programming. If you have a question 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, our topic is: “Parentheses! Parentheses! Parentheses!” We defend the low…
 
Each week, we discuss a different topic about Clojure and functional programming. If you have a question 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, our topic is: “Keywords! Keywords! Keywords!” We examine all the fascina…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “Help! How do I fix my REPL?” We catalog the many way…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “What is ‘nil punning’?” We gaze into the nil and fin…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “When is Clojure not the right tool for the job?” We …
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “Why have derived fields in data when I can just calc…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “What’s so different about Clojure’s REPL?” We evalua…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “What is ‘faking’ a resource?” We talk about the virt…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “What does it mean to be ‘data-oriented’?” We merge t…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “Why do Clojurians make such a big deal about immutab…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “Should I use lein, boot, or tools.deps?” We assemble…
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “Why use Clojure over another functional language?”. …
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “How do I convince my coworkers to use Clojure?”. We …
 
Each week, we answer a different question about Clojure and functional programming. If you have a question 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 question is: “What advice would you give to someone getting starte…
 
It’s summertime, and that means it’s time for something new. Each week, we will answer a different question about Clojure and functional programming. If you have a question you’d like us to discuss, tweet @clojuredesign or send an email to feedback@clojuredesign.club. This week, we’re starting off with “Why do you recommend Clojure?”. We take turns…
 
Christoph and Nate lift concepts from the raw log-parsing series. Reflecting on the lessons learned in the log series. (01:15) Concept 1: We found Clojure to be useful for devops. Everything is a web application these days, “The only UIs in Devops are dashboards.” For most of the series, our UI was our connected editor. We grabbed a chunk of the lo…
 
Christoph finds exceptional log lines and takes a more literal approach. Previously, we upgraded our log parsing to handle finding two errors instead of just one. “It’s amazing what you don’t find when you’re not looking.” We ended up with a set of functions that can parse out multiple errors. The result is a nice mixed sequence of errors that we c…
 
Nate needs to parse two different errors and takes some time to compose himself. Previously, we were able to parse out errors and give the parsing function the ability to search as far into the future as necessary. We did this by having the function take a sequence and return a sequence, managed by lazy-seq. (01:30) New Problem: We need to correlat…
 
Christoph finds map doesn’t let him be lazy enough. Last week, we were dealing with multi-line sprinkle errors. We were able to get more context using partition. (01:33) Problem: the component lines had to be adjacent. Solution last week was to create larger partitions to hopefully get the rest of the error. This became a magic number problem, gues…
 
Nate finds that trouble comes in pairs. Last week, we were able to make our parsing lazy. Each step was lazy, and we side-stepped the landmine of waiting to perform computation till after the file is closed. (02:00) There’s a new error: Sprinkles are failing! Sprinkles are the “likes” of DonutGram, and are the metric by which all donuts are judged.…
 
Christoph’s eagerness to analyze the big production logs shows him the value of being lazy instead. Last time: going through the log file looking for the mysterious ‘code 357’. “The error message that just made sense to the person who wrote it. At the time written. For a few days” Back and forth with the dev team, but our devops sense was tingling.…
 
Nate is dropped in the middle of a huge log file and hunts for the source of the errors. We dig into the world of DonutGram. “We are the devops.” Problem: we start seeing errors in the log. “The kind of error that makes total sense to whoever wrote the log line.” (04:10) We want to use Clojure to characterize the errors. Why not grep? Well…we grep …
 
Christoph has gigs of log data and he’s looking to Clojure for some help. Introducing a new topic. The last few weeks we focused on Twitter and automatically posting to it. Surprised by how much there is to talk about in a focused problem. “There will always be more problems for the world to solve.” (01:53) Imagine if you will, the world of DonutGr…
 
Nate and Christoph reflect on what they learned during the Twitter series. 6 months of podcast episodes! Situated programs: Part of the real world. Affect and affected by the world around it. (04:25) Concept 1: Was very helpful to focus on nailing down the algorithm before diving into the code. (06:00) Concept 2: Two kinds of data: operating data a…
 
Christoph thinks goals are data, not function names. We were talking about the twitter handle again. Last week, we talked about faking. It’s not mocking. The magic that makes it possible is using a protocol. Switch out the real handle or the fake handle in component based on configuration. “Yes, I do want to speak to the log file.” “Sometimes, the …
 
Nate wants to experiment with the UI, but Twitter keeps getting the results. “This thing that we’re making because we’re lazy has now taken 4 or 5 weeks to implement.” Last week: “worker” logic vs “decider” logic. Allowed us to flatten the logic. “You can spend months on the backend and people think you’ve barely got anything done. You can spend tw…
 
Christoph needs to test his logic, but he must pry it from the clutches of side effects. Last week we ended up with “imperative mud”: lots of nested I/O and logic. (01:45) Difficult to test when all the I/O and logic are mixed together. Object-oriented programming advocates for “mocking” objects with side-effects Mocking reinforces and expands the …
 
Nate gets messy finding ingredients for his algorithm cake. Last week we focused on how to determine what to post. This week we focus on getting the data so we can compare it. (01:55) Once again, we’ll use component to organize our app. What components should we have? Component 1: The worker that wakes up, checks the DB, checks Twitter, and posts a…
 
Loading …
Google login Twitter login Classic login