Eight Fallacies of Declarative Computing
Eight Fallacies of Declarative Computing
Join the DZone community and get the full member experience.
Join For FreeLearn how to operationalize machine learning and data science projects to monetize your AI initiatives. Download the Gartner report now.
Erik Meijer listed eight fallacies of declarative programming in his keynote address at YOW in Melbourne this morning:
- Exceptions do not exist.
- Statistics are precise.
- Memory is infinite.
- There are no side-effects.
- Schema doesn’t change.
- There is one developer.
- Compilation time is free.
- The language is homogeneous.
To put these in some context, Erik made several points about declarative programming in his talk. First, “declarative” is relative. For example, if you’re an assembly programmer, C looks declarative, but if you program in some higher level language, C looks procedural. Then he argued that SQL is not as declarative as people say and that in some ways SQL is quite procedural. Finally, the fallacies listed above correspond to things that can cause a declarative abstraction to leak.
(The videos of the YOW presentations should be available in January. I haven’t heard anyone say, but I imagine the slides from the presentations will be available sooner, maybe in a few days.)
Bias comes in a variety of forms, all of them potentially damaging to the efficacy of your ML algorithm. Our Chief Data Scientist discusses the source of most headlines about AI failures here.
Like This Article? Read More From DZone
Published at DZone with permission of John Cook , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}