Hacker News Reader

Comment by discordance | Hacker News Reader

Awesome, thanks for this!

I have been thinking a lot about the time when I can start jamming with GPT inside my dev environment and code base and this is a step closer.

Use case 3, where you define tests and it tries to give you a passing implementation is the dream.

View on HN

Thanks for saying this. I feel the same way. There's something magic about telling the robot to "make the tests pass" and watching the implementation magically appear. It does surprisingly well sometimes. I think if I put some work into the prompts then things could perform better and more consistently.

I firmly believe that there will always be a horizon effect whereby there will be a solution that matches all of the tests but fails for the general case. Computers are more likely to find that test-solving solution that doesn't handle the general case because of their iterative nature, whereas humans want to solve the general case first and then add in conditions to handle the unexpected cases.

As I understand it, the proponents of TDD would argue that as long as the implementation tends towards laziness (avoiding unnecessary complexity), adding more and more tests to handle additional edge cases should cause the code to converse to solving the general case (and avoid local minima).

I suppose that the crucial piece is the laziness, including refactoring whenever possible, to save time on addressing each subsequent test case.

`expect(true).to be true`

Reply on news.ycombinator.com