Rewrite or Reuse? | Code Walks 001

When to re-use code and when to re-write code? I think we choose to re-use other people's existing code much too often. Let me explain why.
This video is part of a series where we go back to the basics and question common assumptions that we often make.
Talks mentioned in the video...
Robert C. Martin:
www.youtube.co....
Sandi Metz:
www.youtube.co....
Original upload date:
28th January 2016

[@JavierPortillo1]

Man, I really like the way you explain this concepts. I'm trying to get better at programming and just watching the list of your videos I know I will learn a lot from you, so thank you!

[@ChristopherOkhravi]

Thanks, I'm glad :) Please feel free to leave suggestions if you want me to cover specific topics.

[@djpunisha29]

In the company i work for we had this problem, we coupled with Angular 1.5.x and over the years Angular was just getting old and there was no easy way to replace him with React/Redux it became our technical debt, and it was expensive to change, expensive in time, decision making, research on React/Redux, lack of developers with certain experience. The hard thing here is, at the moment (4 years ago) we took Angular and it seemed that it was the best choice at the moment, we couldn't have known that the Goole will drop the support and that we will have so many issues, if u could go back in time it would be not an easy task to wrap somehow around Angular so it is easy to replace him. Sometimes due to business, competition and market the only option you have is to introduce 'the latest and greatest' and than after sometime pay off that decision as a technical debt, like we have what React/Redux, and again writing this post, i have just realized that we coupled with React. Time will tell if in several years we have to pay off R/R as a technical debt. Cheers and thanks for the talk :)

[@BothoHohbaum]

Yes. This exactly is the point. You decided to use a well known Framework over implementing the parts you used yourself. This means, the bugs in your system are as well known as the framework. This makes your application much more vulnerable. At least the vulnerabilities are more publicly known. The real vulnerability of your application might be even greater with custom developed components. But the probability of getting hacked is the product of "how well known are my vulnerabilities" * "how many of them do I have". This has exponential aspects... So in this case security by obscurity is exceptionally the better solution... ;-)

[@ehsanenayati882]

Thanks for great videos. In an ideal world I agree with the idea of reinventing the wheel, because then it is your wheel and you have full control over it. In reality, though, money talks. In a company struggling with financial issues and trying to meet the release dates, you as programmer are forced most of the time to use the ready made libraries out there.

[@gopalakrishnann7756]

Thanks a lot for sharing your knowledge with us. The links you have mentioned in the description are broken. I mean, those videos aren't available now. If possible, kindly update with new links.