4 ms·

Skill issue. The fact is that with the right spec, agentic guardrails, and evals, frontier models can now one-shot secure, performant code. This is the job of

by bitwize 2mo ago

Skill issue. The fact is that with the right spec, agentic guardrails, and evals, frontier models can now one-shot secure, performant code. This is the job of software engineering now. Learn to properly use the tools for the job.

hollowturtle 2mo ago
Very much not a skill issue; even with the best spec, guardrails and evals, frontier models will just do the hell they want. > one-shot secure, performant code. I call it reverse skill issue; it feels secure and performant because you can't verify properly, it feels right but it's actually broken in many nuanced ways. You can measure performance and produce a broken measurement as well. It's not as simple as you make it
- deleted 2mo ago
  [deleted]
baliex 2mo ago
Color me sceptical but I’d say that’s a bold claim. Can you give a concrete example of that being the case? I’d love to see the prompt and harness. And understand the scale of problem you’re talking about solving with a one-shot approach. How long will it take to write the right spec? How will you know ahead of time that the spec is correct? Which agentic guardrails do you mean? How can they be set up? - I’d say the job of software engineering is still firmly being able to stand by the work you present and being reasonably confident that it’s correct according to yours and others’ understanding of the problem you’re attempting to solve.
- bitwize 1mo ago
  > I’d say the job of software engineering is still firmly being able to stand by the work you present and being reasonably confident that it’s correct according to yours and others’ understanding of the problem you’re attempting to solve. Indeed. But how you came by that code has changed completely. If you still want to be able to produce at scale, at the speeds customers have come to expect now, you've got to use LLMs.

by bitwize 2mo ago

hollowturtle 2mo ago

Very much not a skill issue; even with the best spec, guardrails and evals, frontier models will just do the hell they want. > one-shot secure, performant code. I call it reverse skill issue; it feels secure and performant because you can't verify properly, it feels right but it's actually broken in many nuanced ways. You can measure performance and produce a broken measurement as well. It's not as simple as you make it

deleted 2mo ago
[deleted]

baliex 2mo ago

Color me sceptical but I’d say that’s a bold claim. Can you give a concrete example of that being the case? I’d love to see the prompt and harness. And understand the scale of problem you’re talking about solving with a one-shot approach. How long will it take to write the right spec? How will you know ahead of time that the spec is correct? Which agentic guardrails do you mean? How can they be set up? - I’d say the job of software engineering is still firmly being able to stand by the work you present and being reasonably confident that it’s correct according to yours and others’ understanding of the problem you’re attempting to solve.

bitwize 1mo ago
> I’d say the job of software engineering is still firmly being able to stand by the work you present and being reasonably confident that it’s correct according to yours and others’ understanding of the problem you’re attempting to solve. Indeed. But how you came by that code has changed completely. If you still want to be able to produce at scale, at the speeds customers have come to expect now, you've got to use LLMs.