So there's a trend I've been noticing among the coding community: the intense mathematizing of programming activities.
But I digress. The point is, important results in math often come from taking a powerful idea and pulling it back onto specific constructs.
-
-
Math is not always about "abstract abstract abstract". What that leads to is Category Theory. And oh boy, does FP love it some Cat. Theory.
-
But Category Theory is like actually really hard to understand and is so general that it's hard to wrangle it into constructive results.
-
Often times, what you have to do is find patterns that work, then pull them back onto more specific spaces to establish results.
-
Programming needs to do that, too. But often times all that work really just leads us back to where we started anyways.
-
Or we find that we do a whole lot of abstraction work to get not a whole lot that's new. No new problems get solved that weren't solvable b4
-
This isn't an invective against FP. OO iss just as bad at this. Enterprise Java is notorious for abstraction upon abstraction.
-
This is more a call to like, think about abstraction and use it when it makes sense, but also to remember the problem you're addressing.
-
Because that problem usually has to do with people. And people can't be abstracted away so easily.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.