The less code you use, the less there is to break Love it!

Thanks for your very detailed answer, it is very clear. There is a lot of way to do the same thing, especially when loops are involved: imperative loop? declarative loop? recursion? iterable? etc. I take great care not to overengineer my code. Like Dan Grosman said on its coursera "programming languages" course: also beware the wrath of premature optimization favor clear, concise code but do use less space if inputs may be large

Adding a library means more code to maintain I do agree.

My belief is that it is the same for all libraries or frameworks (guava, django, etc.). In the context of a library, I prefer a native implementation that allows you to avoid knowing the library, and in the context of a framework, I recognize that you need to know the framework to get as close as possible to it.

I took a look at your slides, that was useful. Thanks for your answer.

We used to have such softwares that transform WYSIWYG graphic into bunch of code. But noone work like that anymore. The more you can do to work with coders is to give them data about your design choices: margins sizes, fonts policies, colors used, etc. The designers in my work team use zeplin.io , see information it gives when you browse the design sheet.

The very recent eslint-scope adventure shows us that CI and 100% test coverage are not enough to automate dependency updates, even minor versions.

Thanks Eric, I did not know aboyut python/mr.developer . We should take a look at nodejs/mr.developer to adapt it to our development flow. Even if it did not answer the question in application maintenance: when and how do you update your dependencies? And corollary: what should be the commit message prefix? fix? feat? core? I vote feat as it change production code.

Before asking I made up my own conclusion and it is quite the same as yours. That's why I appreciate it.

Let use another code sample (like fizz buzz kata): if ( x % 3 === 0 && x % 5 === 0) { return "fizz buzz" ; } else if ( x % 3 === 0 ) { return "fizz" ; } else if ( x % 5 === 0 ) { return "buzz" ; } else { return x } See this jsbin Note: You can use the result as a expectation in tests, and try to write some new code with Test-Driven Development. For instance, in OOP you can use polymorphism: https://www.refactoring.com/catalog/replaceConditionalWithPolymorphism.html Let us know if you found an elegant way to answer your needs.