Hello! Languages of the real and artificial is using DISQUS, a powerful comment system, to manage its comments. Learn more.
Community Page
- osteele.com Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- NoTV service is not available in my area. Something about low demand :)
- I also read recently about Ethanol polluting more than gasoline. Not sure if its true coz I couldn’t keep up with all of the chemistry..but im very much interested with fuels becoz im a car...
- We got NOtv when we lost cross country wireless and moved to a new house. We found that DSL was a better item and we can actually limit what we see. The NOtv has been a shock to many folks who are...
- Absolutely beautiful post. Thirty minutes after reading it, my whole way of doing git business has changed.
- Wow, this is awesome! You should talk a little more about the code behind how this works, would be a great read.
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
@Pseudonym: Congratulations on catching the subtleties in the title ("every programmer" versus "some programmers"; "needs" versus "should"). Nonetheless, I'm curious as to whether knowing category theory helps anyone program. The parts of category theory that relate to programming (functors, isomorphisms, monads and co-), I realized I was able to understand by using specific programming constructs as examples, and that knowing their categorial expressions didn't lead me to think about them any more deeply or to find analogies or solutions (the way that, say, realizing that you've implemented a state machine, or that your problem can be expressed in linear algebra, do).
And I haven't been able to apply the other parts of category theory to programming at all, although I've found them incredibly useful in doing, and teaching, math, and in thinking about other activities such as project management and other aspects of life. The Yoneda Lemma, for example, says that you aren't lost if you can find a landmark that you can get home from. (Think about it :-)
1 year ago
In software engineering, if a pattern shows up in several applications, we give it a name so we can talk about it independently of any single application. Same with category theory. Initial objects, products, equalisers and so on are names of patterns which turn up in a lot of algebras.
One thing that I see a lot is that programmers come out of university with a lot of knowledge about how to implement a function/procedure/whatever, but almost none about how to implement the interface. Making things worse is the problem that an interface is harder to change than an implementation. It's more important that you get it right early.
One theme that I'm seeing is that the best interfaces, the best APIs, are the most "mathematical". Even simple things, like binary search trees, are simpler to implement and use if you think about them algebraically. Even some .NET APIs are using monads in anger these days.
Yes, you could come up with that without knowing any category theory. However, category theory is another tool in the programmer's toolbox that can be used to talk about, understand and ultimately solve a problem.
1 year ago
1 year ago
1 year ago