Reply to thread

Message

<blockquote data-quote="struppigel" data-source="post: 970288" data-attributes="member: 86910">&quot;if you’re going to re-use someone else’s wheel, shouldn’t you check that it’s reliable first?&quot;The person stating this has clearly never done software development. But sure, just read through 200 000 lines of code before you are allowed to use logging. And of course you also have to have the IT security knowledge to do that.Imagine you require from ever person before using any device, be it TV, fridge, bicycle, laptop, car, ... that they also know how it was built, how it looks from the inside and whether it is safe to use. That&#039;s about the same amount of work and time. We would still be living in trees.From the title I expected a warning about not using StackOverflow or tutorial code just as is,&nbsp; because those are often example codes without any safety checks. But calling library usage &quot;cut-and-pasted programming&quot; (sic) seems pretty odd.</blockquote>

[QUOTE="struppigel, post: 970288, member: 86910"] "if you’re going to re-use someone else’s wheel, shouldn’t you check that it’s reliable first?" The person stating this has clearly never done software development. But sure, just read through 200 000 lines of code before you are allowed to use logging. And of course you also have to have the IT security knowledge to do that. Imagine you require from ever person before using any device, be it TV, fridge, bicycle, laptop, car, ... that they also know how it was built, how it looks from the inside and whether it is safe to use. That's about the same amount of work and time. We would still be living in trees. From the title I expected a warning about not using StackOverflow or tutorial code just as is, because those are often example codes without any safety checks. But calling library usage "cut-and-pasted programming" (sic) seems pretty odd. [/QUOTE]

Verification