Comment by hombre_fatal
14 hours ago
It's pretty amazing what you can do when you embrace LLMs, figure out how to build one high-quality rigorous project with them, and then start working on more projects.
You become a machine with your workflow, once again limited only by your time/energy, tokens, and your discretion on how to spend it.
matching decompilation is a verifiable target. Its hard to create slop that still matches. The same does not hold up for coding with llms normally.
> It's pretty amazing what you can do when you embrace LLMs, figure out how to build one high-quality rigorous project with them, and then start working on more projects.
Indeed. But I think it's fair to say that just embracing LLMs is not enough.
I'd consider embracing to include developing expertise in the tool.
[flagged]
Using AI is cognitive surrender. It's not your code, it's not your work.
When I was in high school, graphing calculators were pretty new. New enough that most teachers had not yet encountered them.
I was a pretty nerdy kid even then, and I saw graphing calculator as 'portable computer' in 1993! So, of course I wanted one.
When our teachers found about them, they banned the use of graphing calculators, some teachers going so far as to only allowing 'four-bangers' (a basic one) for classes lower than Trig (I never got to Calc in high school).
Funny, but your statement reminded me of what one of math teachers used to say: "If you use a graphing calculator, you aren't doing math." It seems really quaint today.
8 replies →
Actually it is your code and it is your work.
2 replies →
Using typewriters is surrender!
Not your handwriting, not your work!
16 replies →
Using automated looms or wearing textiles woven by it is cognitive surrender. It's not your fabric, it's not your work.
Yes it is
its a decomp, it wasnt your code to begin with
There's a time for cognition and a time for just moving quickly and getting shit done.
Downloading a bunch of open source libraries and putting together some project with a bunch of glue code also requires little thinking, but before AI no one really said that was "cognitive surrender". People even got pats on the back... for using other people's work to build something.
IMO it's fine if you use it to review hand-written code. Vibe-coding (and especially 100% slop projects) on the other hand, is indeed cognitive surrender as it's identical to cheating on homework back then.
Could you not say the same about using a compiler or higher level language or a library you don’t understand or an algorithm you don’t understand or a chip that you don’t understand?
2 replies →
Producing shit code slowly hasn't held me back so far and I don't intend to start letting it do so now.
> You won't be able to produce as good code
This says more about you than anything else. You weren't able to produce good code before AI, and you are not producing good code after AI.
Username checks out.
You might be right. I'm a better programmer than most, but I'm nowhere near as good as I could be, and there is still so much I could learn and improve upon. But back when I was saying that "AI is better than most programmers", ~6 months ago, I figured people at my level were still somewhat safe, as the average programmer, even working professionally, is a shockingly low bar. Do not judge the entire profession by Hackernews posters; most of us are in the upper quartile or so.
These days, for small to medium-sized tasks, frontier LLMs are consistently well within that upper quartile. People at my level have a lot to be concerned about, as most of our day-to-day can be automated away. Sure, there's need for judgement and architectural discipline, but in most shops that's done by the people we used to make fun of in the 2000s, who sit in design review meetings and produce box-and-arrow diagrams, not code. Those are now the real bringers of value to a software development company or division.
At a bare minimum, it is irresponsible to ship code that has any sort of security requirement without using AI. Frontier models are able to discover zero days in minutes that would have taken months with human investigators, and if you're not auditing and red-teaming your own code with AI, someone else will use AI to pop it.
You are just not working to a professional standard in 2026 if you're not using AI.
2 replies →