It is excusable, because people are human and make mistakes.
Escaped security holes are a development PROCESS problem not a programmer problem.
It is excusable, because people are human and make mistakes.
Security holes are a development PROCESS problem not a programmer problem.
It is excusable, because people are human and make mistakes.
Security holes are a development PROCESS problem not a programmer problem.
It is excusable, because people are human and make mistakes.
Security holes are a development PROCESS problem not a programmer problem.
Those wanting to blame programmers are ignorant of software development process improvement and do not know wtf they're talking about.
Don't blame me for your companies bad processes.
It is excusable, because people are human and make mistakes.
Security holes are a development PROCESS problem not a programmer problem
Security holes are a development PROCESS problem not a programmer problem.
It is excusable, because people are human and make mistakes. Do you think I told Stripe that their php programmer who wrote their Go API and fucked up using an unordered structure as an ordered structure throughout the entire API made an inexcusable mistake and should be fired? No. I didn't. And there's a reason, because people are human and make mistakes. The guy will learn from his mistake.
It is not the job of a SE to do security testing. That doesn't mean write shit.
If you don't pay for/budget time/money for security testing/bullet proofing, don't expect your shit to be secure. Also don't blame me for your stupidity.
It is excusable, because people are human and make mistakes. Do you think I told Stripe that their php programmer who wrote their Go API and fucked up using an unordered structure as an ordered structure throughout the entire API made an inexcusable mistake and should be fired? No. I didn't. And there's a reason, because people are human and make mistakes. The guy will learn from his mistake.
It is not the job of a SE to do security testing. That doesn't mean write shit.
If you don't pay for/budget time/money for security testing/bullet proofing, don't expect your shit to be secure. Also don't blame me for your stupidity.
Security holes are a development PROCESS problem not a programmer problem
It is excusable, because people are human and make mistakes. Do you think I told Stripe that their php programmer who wrote their Go API and fucked up using an unordered structure as an ordered structure throughout the entire API made an inexcusable mistake and should be fired? No. I didn't. And there's a reason, because people are human and make mistakes. The guy will learn from his mistake.
It is not the job of a SE to do security testing. That doesn't mean write shit. It just means it's not your specialization.
If you don't pay for/budget time/money for security testing/bullet proofing, don't expect your shit to be secure. Also don't blame me for your stupidity.
It is excusable, because people are human and make mistakes. Do you think I told Stripe that their php programmer who wrote their Go API and fucked up using an unordered structure as an ordered structure throughout the entire API made an inexcusable mistake and should be fired? No. I didn't. And there's a reason, because people are human and make mistakes.
It is not the job of a SE to do security testing. That doesn't mean write shit. It just means it's not your specialization.
If you don't pay for/budget time/money for security testing/bullet proofing, don't expect your shit to be secure. Also don't blame me for your stupidity.
It is excusable, because people are human and make mistakes. Do you think I told Stripe that their php programmer who wrote their Go API and fucked up using an unordered structure as an ordered structure throughout the entire API made an inexcusable mistake and should be fired? No. I didn't. And there's a reason, because people are human and make mistakes.
It is not the job of a SE to do security testing. That doesn't mean write shit. It just means it's not your specialization.
If you don't pay for/budget time/money for security testing/bullet proofing, don't expect your shit to be secure. Also don't blame me for your stupidity.
It is excusable, because people are human and make mistakes. Do you think I told Stripe that their php programmer who wrote their Go API and fucked up using an unordered structure as an ordered structure throughout the entire API made an inexcusable mistake and should be fired? No. I didn't. And there's a reason, because people are human and make mistakes.
It is not the job of a SE to do security testing. That doesn't mean write shit. It just means it's not your specialization.