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

Impact Mapping – The Secret Sauce

Details "Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and...

Pragmatic Architecture: How to Know When It’s Enough

Details Overengineering wastes time and effort, while underengineering creates future pain. How do you strike the right balance? This talk explores how you can use the balanced coupling model to achieve the just-right engineering. You’ll learn to predict volatility of...