Develop by describing the problem (not the solution) – Romeu Moura – KanDDDinsky 2017

video:

Every test should describe the problem & not the solution, every program should do both.

Most of your current programs describe only the solution to a problem long forgot in time.

Let us change this, let us write programs that are a description of the problem (as much as possible).

Let us program by describing the results we seek instead of how to meet them.

Let us embrace the declarative style of logical/relational programming! But do so without switching our current language of our current legacy project. Using MiniKanren (exemples in clojure, but works in your lang too)

Tags

Follow us

Read our latest news from Virtual DDD on any of these social networks!

Recent videos

Systems Thinking Intro with Lorraine Steyn

Systems thinking is the macro behaviour that we must understand in analyzing our world. A system always produces what it is designed to do, even if that isn't at all what we meant it to do! Systems are self-maintaining, and contain balancing and/or reinforcing...