# Fully understanding the "intricacies" of the Prolog code design process

**URL:** <https://swi-prolog.discourse.group/t/fully-understanding-the-intricacies-of-the-prolog-code-design-process/7552>\
**Category:** Help!\
**Created:** [June 24, 2024, 7:35pm UTC](https://swi-prolog.discourse.group/t/fully-understanding-the-intricacies-of-the-prolog-code-design-process/7552 "2024-06-24T19:35:28Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Boris](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/boris/32/7486_2.png) [@Boris](https://swi-prolog.discourse.group/u/Boris)\
**Post date:** [June 27, 2024, 4:59am UTC](https://swi-prolog.discourse.group/t/fully-understanding-the-intricacies-of-the-prolog-code-design-process/7552/21 "2024-06-27T04:59:48Z")

</div>

Several difficulties here.

- You can’t possibly fit the intricacies of multiple programming paradigms in a course.
- Programming paradigms themselves are usually (always?) pushed way beyond their usefulness.
- “Declarative Programming” is an oxymoron; [here](https://swi-prolog.discourse.group/t/a-pure-sort-2/2438/12) is one post on the topic but please search yourself, the topic pops up regularly.
- Reading library code is a fundamental part of learning programming.
- Terribly sloppy to save typing: Programming does not have general laws in the same way that nature does. It is invented by humans and we still don’t understand ourselves well enough.

I understand that this doesn’t answer your question directly.

---

_[View the full topic](https://swi-prolog.discourse.group/t/fully-understanding-the-intricacies-of-the-prolog-code-design-process/7552)._