I did write the spec first — data model, algorithm, etc. That may have helped the agents get traction.
It's getting crowded down here in the rabbithole... One more to peek at: https://github.com/prb/pips-solver/blob/main/README.md
Just for grins, I ran stats on most (but not all of the puzzles): • Solution Counts Overview - Processed all 183 stored puzzles (61 dates × 3 difficulties) via target/ release/count_solutions, saving raw results to…
> My guess is that if I changed the way the solve functions picks the square to start with it could greatly change the time. Right now it just takes the first open square found scanning right to left and top to bottom.…
So much fun. I'm not sure if the game is more fun or writing a solver for the game is more fun... Here's my entry written in Rust from a spec in Markdown — executed as an initial AI coding experiment with Gemini,…
When I did experiments with RoR versus Haskell via FCGI, Haskell had around a two orders of magnitude performance advantage under load and only required a single OS process.
How about "dbNG" for next-generation database?
I did write the spec first — data model, algorithm, etc. That may have helped the agents get traction.
It's getting crowded down here in the rabbithole... One more to peek at: https://github.com/prb/pips-solver/blob/main/README.md
Just for grins, I ran stats on most (but not all of the puzzles): • Solution Counts Overview - Processed all 183 stored puzzles (61 dates × 3 difficulties) via target/ release/count_solutions, saving raw results to…
> My guess is that if I changed the way the solve functions picks the square to start with it could greatly change the time. Right now it just takes the first open square found scanning right to left and top to bottom.…
So much fun. I'm not sure if the game is more fun or writing a solver for the game is more fun... Here's my entry written in Rust from a spec in Markdown — executed as an initial AI coding experiment with Gemini,…
When I did experiments with RoR versus Haskell via FCGI, Haskell had around a two orders of magnitude performance advantage under load and only required a single OS process.
How about "dbNG" for next-generation database?