I terms of usability this seems to me up there with the set theoretic formulation of relational model. I.e. not as something everybody needs to do but offering an efficient descriptive model for complex systems.
When designing programs or datastructures I prefer to use pen and paper and some simple set theoretic ad hoc notation system.
I write code for production daily and without this higher level design model my code would be uk terrible shape and very slow to modify.
"As a philosopher, it pains me to know people don't think that way, but if you aren't changing people's lives then all the theory is just mental masturbation."
Basically really good programmers seem to see the optimal structure for a specific problem out of practice. I need to have some sort of theoretic framework which to use to compose my program logic.
I've not had the time to look into category theory but this post succeeded in convincing me it's a practical mental tool to help in program composition.
So, based on my personal preferences, I disagree this would not have practical benefits.
When designing programs or datastructures I prefer to use pen and paper and some simple set theoretic ad hoc notation system.
I write code for production daily and without this higher level design model my code would be uk terrible shape and very slow to modify.
"As a philosopher, it pains me to know people don't think that way, but if you aren't changing people's lives then all the theory is just mental masturbation."
Basically really good programmers seem to see the optimal structure for a specific problem out of practice. I need to have some sort of theoretic framework which to use to compose my program logic.
I've not had the time to look into category theory but this post succeeded in convincing me it's a practical mental tool to help in program composition.
So, based on my personal preferences, I disagree this would not have practical benefits.