by lfittl on 7/3/24, 4:48 PM with 39 comments
by 0cf8612b2e1e on 7/3/24, 7:38 PM
by taeric on 7/3/24, 9:38 PM
It is a shame, as most programs work against the ideas here by trying to have a singular representation of their data. This is just not reasonable for most things and leads to a lot of contortions to get the algorithms to work on a new representation.
This article touches on it with the brief touch of declarative at the top. I always regret that more of my code is not translating between representations more often. You can wind up with very concise representations when you do this, and then you can get a double bonus by having things run faster by virtue of being concise.
(And, yes, I realize I'm basically describing many data pipelines. Where you spend most of your time translating and fanning out data to places for more compute to be done on it.)
by mark_l_watson on 7/4/24, 2:43 AM
MiniZinc is a constraint programming system. There is a good Coursera class using MiniZinc.
by bartkappenburg on 7/3/24, 6:52 PM
I love the subject and reading this brought back a lot of memories. Also the realization that translating constraints to a model (variables, structure etc) is 90% of the work and the most difficult part.
by d_burfoot on 7/4/24, 3:21 PM
by Elucalidavah on 7/4/24, 4:25 PM
It so often bothers me that I have to guesstimate some values for parameters I don't initially care about, instead of constraining the parameters I care about and then optimizing the rest.
by richard___ on 7/3/24, 7:04 PM