{"id":2278,"date":"2018-06-25T15:59:11","date_gmt":"2018-06-25T12:59:11","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=2278"},"modified":"2018-06-25T15:59:27","modified_gmt":"2018-06-25T12:59:27","slug":"evolutionary-design-talk-newcrafts-paris-18-mai-2018","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2018\/06\/evolutionary-design-talk-newcrafts-paris-18-mai-2018\/","title":{"rendered":"Evolutionary Design Talk – NewCrafts Paris 18 May 2018"},"content":{"rendered":"

Evolutionary Design Talk<\/h2>\n

Evolutionary Design: The art of growing a system by observing its natural traits and then normalizing and optimizing its growth<\/p><\/blockquote>\n

Evolutionary Design seems to be one of the black arts of software development.<\/p>\n

Evolution<\/strong> = transformation.\u00a0Evolving the code is not done by magic, we the programmers evolve the code. And we need specific techniques for that. When we evolve, we transform the code to something else. We will talk about some of these transformations, when to use each one and why.<\/p>\n

Simplicity<\/strong> We work feature by feature and not layer by layer. All the development is done on a vertical thin slice through all the layers. We use evolutionary refactoring with many design principles in our mind, but not with a predefined design. We respect the principles, but focus on finding the simplest solution for the problem.<\/p>\n

Focus on the problem, not the solution<\/strong> We want to rather focus on the problem and not the solution, rather than when we know the solution, but we just find the fastest way to implement it. When we know the solution, the question is: can it be improved; is it worth it? We will talk about some heuristics of \u201cgood enough\u201d.<\/p>\n

Video<\/h2>\n

http:\/\/videos.ncrafts.io\/video\/275530160<\/a><\/p>\n

Slides<\/h2>\n