logoalt Hacker News

fsnovask • yesterday at 11:43 PM • 4 replies • view on HN

>The best hacker today is neither AI nor human. It is the centaur hacker, part human, part AI.

I think only really smart people are going to be left in Security and Software. I can barely fathom what this group is doing with AI right now (ignoring that their model probably isn't nerfed and mine would be) and I don't think any of this is trainable for the average developer. This is starting to feel like some of the scientific fields where careers start when you get a MS/PhD. Or like the average developer is on the same level of not being able to convert a Word document to PDF.


Replies

eru • yesterday at 11:55 PM

> I think only really smart people are going to be left in Security and Software.

I'm looking forward to eventually getting there. At the moment, there's so much low hanging fruit that even someone without a clue like me can just point a fuzzer at some random Linux kernel code and still discover problems.

(Most of the problems I found from that exercise are patched by now, if you use a recent enough kernel.)

I used Kimi to drive the fuzzer. The model didn't have to do anything smart, just do the tedious work of writing the glue code to make the fuzzing work. AFL++ did the 'smart' parts, and I had the idea to kick it off and oversaw the patches.

colonCapitalDee • yesterday at 11:54 PM

I don't know, it feels like just another skill to me. You learn your debugger, you learn the shell, you learn web development... you learn AI.

We'll see how long the centaur era lasts though. Hopefully a very long time

➕ show 1 reply
Pokepokalypse • today at 4:22 AM

Truth be told; as far as I can tell, the output the human gets from the AI can vary vastly in quality, depending on guardrails on the AI side. Guardrails that are internal (and opaque) to the user, combined with directives the user sets up, often manually.

(for example, I have mine keep ready reference to all of our CMMC controls and best practices)- and not only will my sessions cite referenced material as it responds, but it will do so when it writes code, as well - and it does a pretty decent job of keeping me honest. The one bit I'm struggling with is limiting complexity when it designs a solution to a problem. For larger projects, this can snowball quickly - and I haven't found an effective way to prevent this yet.

Skills can be shared, but it's a bit of a steep climb to getting an entire organization to pick the same skill (to get consistent behavior across the whole org)- sometimes an individual skill as it's written, will conflict with some other personal standard or quirk of how they work, so it's difficult to share them. This really seems, to me, to be very similar to how the software world used to work (as far as interoperability goes), earlier in history when there weren't many open standards, (and NO open source code) - and every competing OS vendor was trying to destroy their competitors so they could become a monopoly.

But yes, there's quite a bit of effort now that goes into maintaining this personal harness, and I'm sure the even smarter folks will come along and figure out workable ways of standardizing and sharing those kinds of harnesses.

I've been in this industry for 30 years, and the way I work has always changed with the times and new tools. It changed a LOT when Dev Ops became a thing. IaC, and containers. This feels kind of like that change, but maybe an order of magnitude. Almost feels like going from assembler to learning something like python; in terms of how much abstraction is being added.