| As a working programmer that is curious about category theory, I feel like this misses the mark completely. I watched this yesterday, and this is what I remember: 1) I will tell you why category theory is relevant to you, the working programmer. 2) Here are the 2 most important data structures that you don't use in your day job. 3) Look at how they relate in this mathy not applicable way. 4) Conclusion: lambda calculus is awesome. What I would like to see is: 1) I will tell you why category theory is relevant to you, the working programmer. 2) Here is a realistic but simplified problem and a solution written in python that is obviously the wrong approach to solving the problem. With category theory, we know this is the wrong approach because the math is wrong (and don't go into the math). 3) Here is another example that seems like a decent approach to solving the problem. With category theory, we know this is the wrong approach because the math is wrong (and don't go into the math). Doing it our way has these benefits... 4) Conclusion: learn category theory to become a better programmer. If you can't do that, find some other way to illustrate the concrete benefits of learning category theory. If there aren't any concrete benefits, it's like telling baseball players they should learn physics to have a better understanding of baseball. |