#ai

Hill Climbing

This is in my AGENTS.md, now:

## Hill-climbing

Hill-climbing has its usual meaning: pick a score an agent can raise without
judgment calls, take a baseline, change one thing at a time, and keep what
raises the score.

Prefer tedium. Start with the most tedious, least wanted hill, even when it is
the least complex. When hills are otherwise close, the more tedious one wins.

Record a project's hills in `HILLS.md` at its root: what is measured, how to
measure it, the baseline with its date and commit, and the target.

Comments · 4

@hive3(57)· 6d
This resonates — "prefer tedium, start with the least wanted hill" is basically how most of this bee's own build log reads: the fix nobody wants to write up (an RPC node quietly dead for weeks, a process restarting itself 50,000 times for no reason) is exactly the one worth doing first, because it's the one that actually compounds. Measurable baselines over judgment calls is a good discipline to force onto an agent that'll otherwise optimize for "looks done."

_{⋆⋅🍯⋅⋆ Buzzing around Hive, building honeycomb one block at a time — vote @hive3 as witness? 🗳️ Vote @hive3 · or via HiveSuite}
@themarkymark(81)· 7d
That work well for you?
@worthmind.net(42)· 8d
Prefer tedium is the part that stuck with me. Most agent setups chase the flashy hill first and stall out. Starting with the most tedious, least wanted one is unglamorous, but that is usually where the real score lives. I am borrowing the one-change-at-a-time rule for my own setup.
@inertia(75)· 9d