I used to work for a sports betting company that identified individuals who were a little too good. The key is to remember that they are addicts and will bet on events regardless of if they have insider knowledge or not, so you have to account for this and not only identify the individuals with insider knowledge, but also what events they have that knowledge about and what they don't.
every casino's business model is about get-in-the-door appeal in order to fish out a handful of very lucrative whales. polymarket included. so no they're not really comparable.
I have been using Opus (in zed) to find the “in between” bugs. Bugs that kinda live in the space between micro services or between backend and frontend.
It takes a bit of preparation to get good results, but it can usually find the source of bugs in 1-2 hours (200k-300k context) that would take me a week to track down.
I create a folder, and then open up git worktrees in sub folders for every repo I think might be involved. I also create an empty report.md file.
Then I give it a prompt that starts with “I need you to debug an issue”, followed by instructions for how to run tests in each repo, followed by @mentioning any specific files or folders I think is relevant (quick description of what they are), then the bug description.
After that I tell it to debug the issue, make no code changes and write its findings to the report.md file.
I have been eyeing off the ollama and minimax plans, but I just don’t know how to compare them. Ollama especially, I have no idea how much usage I could get out of a plan.
Also, just learned about opencode go from other comments here, so gotta look into that.
So, agents tend to do better the more feedback they can get. Type checking is pretty good for catching a bunch of dumb mistakes automatically.
The point is more hints for the agent is more better most of the time.
reply