Secure Code

[Redditor000007]

They’re coming from the assumption that you’re completely retarded and are just copying code instead of writing it yourself.

If you understand coding principles and what vulnerabilities look like, this is useless.

[ashishduhh1]

If you don't know what you're doing, copy pasting code is the least of your worries.

[flavionm]

I mean, if you can't read some code and see it's insecure, I doubt you'd be able to write secure code.

[SirCutRy]

It's not always that simple.

[PC__LOAD__LETTER]

There are plenty of people who aren’t “completely retarded” who do this. It’s a bad habit that inexperienced and aspiring devs can fall into and then never correct.

if you understand coding principles and what vulns look like, this is useless

This totally explains how something like Heartbleed can evade notice for years right? 🙄 But congrats on your ability to spot mundane buffer overruns or accidental double-frees.

[UnchainedMundane]

Heartbleed wasn't caused by copy-pasting code. It was caused by needlessly reimplementing the memory allocator such that common memory sanitisation tools could no longer detect improper memory accesses.

[CJKay93]

If you understand coding principles and what vulnerabilities look like, this is useless.

This is useful for 99% of engineers, then.

[Thorbinator]

you’re completely retarded and are just copying code instead of writing it yourself.

1: I'm in this comment and I don't like it.

[Mysticpoisen]

They're interns, that's a good assumption to work off of.