Ep 101: Sportify!

We tackle a new application, thinking it'll be an easy win—only to discover that our home run was a foul, and the real world is about to strike us out!

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: "introducing Sportify!". We tackle a new application, thinking it'll be an easy win—only to discover that our home run was a foul, and the real world is about to strike us out!

Our discussion includes:

Introduce a new series!
Sportsball! Sportsball!
Going back in time.
An overview of video production workflows.
What is a media asset manager?
How hard could it be?
What could possibly go wrong?
What are all the things we'll need to handle?
What is a situated problem?
Does immutability matter when most of the work is I/O?
Code stability in Clojure.

Selected quotes:

"Clojure has made our lives fun, so we want to make your lives fun."
"What do people love when they're watching sporting events? They love their highlights."
"This is not a business problem. This is a sports problem, and sports problems are different."
"Now this is where we're reaching the edges of reality, but just hang on. Come with us."
"How hard could it be?!"
"What could possibly go wrong?!"
"But this MAM...do you have to be polite? Can I have the video ma'am?"
"We've got to do the right amount. That's the hard part: the right amount."
"Is there a fraught problem that's not situated, or a situated problem that's not fraught?!"
"Situated, in my mind, is useful. I don't just want to heat the room up with my computer. I want to actually get something done!"