Categories
Tags
Archives
- February 2011
- October 2008
- September 2008
- May 2008
- April 2008
- February 2008
- January 2008
- December 2007
- November 2007
- August 2007
- July 2007
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- April 2005
- March 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- April 2004
- March 2004
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
- April 2003
13 Comments
Nothing? How poignant
Clever.
True enough. Only good programmers need to know about it.
umm, was that supposed to be an ironic joke?
Is this a joke? I cant see any content. I am using IE 6.
Nothing?
@nec, @Arjang: yes, nothing; sorry, it was intended as a joke, not a trick.
@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
Oliver: Category theory is to mathematics what design patterns are to software engineering (which is not, of course, what “every programmer” does).
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.
What .NET API is using Monads? (My googling is swamped by the Powershell use of the term).
Seems as tho there is no text under this article? i’ll try again later..
HAHA
I am using Fire Fox 3.0 and i can’t see a thing either ^^
I am using Fire Fox 3.0 Final, and besides the title I can’t see a thing either ^^