I'm often asked how to turn a security-related interest or hobby into a job. For the longest time, I'd say pretty much the same thing written here: get a book, do some research, build some projects, talk to people in industry. I've been going to DEF CON for about 25 years now, so I've had this conversation countless times.
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.