How to Break into Security, Ptacek Edition (2012)
57 points - today at 10:19 PM
SourceComments
But in 2026, tptacek says it best in the comments here: At this point, who knows?
Are we still telling kids to learn programming languages to become software developers? Perhaps system design is a more reasonable skill set.
That said, because this is the time to say it: security is still important, and it's not -- and shouldn't be -- fully automated.
The toolchain is changing just like it always has. I remember when interpreted languages replaced compiled ones, and people said that interpreters solved security. Then people went from writing their own codebases to implementing frameworks, and people said it solved security.
Barracuda Networks posters at every airport stated "Security Solved."
As long as people take risks, security is important. Now we just need to focus on designing resilient systems instead of finding bugs and vulns on the code-level. LLMs can do that part for us.
As for AI it’s been great for things like log review but those were already pretty low skill requirements. We haven’t had much luck past that.
I'm anticipating "the fundamentals are crucial," and as much as I want to agree, I think practical realities show us otherwise. We're at a point where all someone needs to know is how to AI-program-manage and how to glean enough about the discipline (or any discipline at this point) from AI to be dangerous enough in the field. To be a builder, breaker, or defender wearing any color hat of their choosing... that's it, really.
what the incentives are since hacking seems to be no longer a crime given how many hacking incidents have gone unpunished.