prb

3 ms·

1. 1.▲
   by prb 1y ago

   I did write the spec first — data model, algorithm, etc. That may have helped the agents get traction.
2. 2.▲
   by prb 1y ago

   It's getting crowded down here in the rabbithole... One more to peek at: https://github.com/prb/pips-solver/blob/main/README.md
3. 3.▲
   by prb 1y ago

   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 gpt_5_c
4. 4.▲
   by prb 1y ago

   > 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. Maybe something li
5. 5.▲
   by prb 1y ago

   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, Claude, and Cod
6. 6.▲
   by prb 16y ago

   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.
7. 7.▲
   by prb 17y ago

   How about "dbNG" for next-generation database?