Top
Best
New

Posted by craigmart 8 hours ago

How the Claude Code team thinks about verification(claude.dev)
185 points | 156 commentspage 2
gregwebs 6 hours ago|
After I created this skill for verification, it completely changed my level of trust with AI coding.

https://github.com/gregwebs/skills-sdlc/blob/main/skills/ver...

The implementation process that I am using also looks for verifications during planning and reviewing and makes sure they are completed. It does use a lot more time and AI spend than just asking AI to do something. I still do the latter for simple or noncritical changes. I had to switch to using DeepSeek as my workhorse to keep down my spend.

https://github.com/gregwebs/skills-sdlc/blob/main/skills/imp...

nelox 5 hours ago||
We are well on the way to recursive self improvement
holoduke 1 hour ago||
What we need are ultra fast testing suites. Specially e2e tests are notoriously slow. Runtime is big and its often difficult to isolate just a few tests. I want 1000 e2e tests in a few seconds instead of 10 minutes. It's also a mayor blocker for an agent that cannot work fast because of the constant waiting. At the same time you need the test feedback loop in order for the LLM to do proper shotgun programming.
sashank_1509 3 hours ago||
Take 10-20 skilled programmers, the kind that made web browsers, game engines etc. Give them a year. They will end up with a superior working version of Claude Code without thousands of bugs and issues, that keep getting fixed and unfixed and trillions of tokens spent by AI.

They won’t even do all this verification nonsense and their end product will be of superior quality.

anshumankmr 1 hour ago||
Honestly, the amount of bullshit unit tests Claude keeps pushing nowadays. I took a few hours the past few weeks, some with AI, some by myself to hand remove some really dumb fucking test cases. God knows how long the CI must be running when these guys push their code.
AlienRobot 45 minutes ago|
I wonder what was it even trained on?

Who ever had the time and will to write unit tests that mock every single function/class being called, checks the strings of thrown errors, etc., for every single function, for several tests per function?

The instant you change the implementation the tests break because it's testing how many times each method has been called of an object that was passed as argument.

That's just an insane way of writing tests. But for AI that's normal for some reason.

It feels like it's making unit tests the "textbook" way that in practice you wouldn't do because in practice half the things it's testing are inconsequential.

nandanadileep29 7 hours ago||
excellent content from the team. very concise and clear
johnrc 14 minutes ago||
[flagged]
tanmaycodex1 49 minutes ago||
[flagged]
arbor-group 3 hours ago||
[flagged]
adilbasari 3 hours ago|
[flagged]
More comments...