Incredible work, thank you very much for sharing! I’m a QA Engineer and all the data you’ve shown is very valuable and relevant to my work) Usually it is so hard to explain to the managers all these things regarding code quality / refactoring and rush without numbers. But now we have those + very cool visualizations - so thanks again!
Is a DRY violation always a bad thing? Some folk sometimes duplicate code on purpose in order to make sure that changes in one place are way less likely to break something else. I heard this for example earlier today in an interview by Kevlin Henney posted on this same channel.
Incredible work, thank you very much for sharing! I’m a QA Engineer and all the data you’ve shown is very valuable and relevant to my work) Usually it is so hard to explain to the managers all these things regarding code quality / refactoring and rush without numbers. But now we have those + very cool visualizations - so thanks again!
Very nice talk! It is very useful to have a reference for good research with exact numbers that can help to argue with business people.
This is incredibly cool
Is a DRY violation always a bad thing? Some folk sometimes duplicate code on purpose in order to make sure that changes in one place are way less likely to break something else. I heard this for example earlier today in an interview by Kevlin Henney posted on this same channel.
No it’s not always a bad thing. As a counterpoint you can use en.wikipedia.org/wiki/Rule_of_three_(computer_programming)
Have a look at vertical slice architecture