29d • 💬 General discussion
The AI Bias problem...
A model optimises for the route you named, not the best route available. It will find the
least-friction path to the outcome you described, and it will almost never tell you that
outcome could be reached a completely different way.
Compliance over correction - it answers the question asked, not the better question sitting
next to it.
No metacognition layer - it does not step out of the workflow to ask whether the workflow
itself is right.
The frame sticks - once you have named five steps, every answer after that is about those
five steps.
The version I hit: I was mid-build on something chaining five separate services together, and
every time I asked what the next step was I got the next step in that chain. Every answer was correct. What never came back was that an MCP had since been built that collapsed the whole
thing into one connection.
Ifound it by opening a cold chat with no context and asking, flat, what the shortest route to that outcome was. Same model, different question, completely
different answer. Nothing was wrong with the responses. The frame was set by my first message and everything
after inherited it.
So the guard I run now is that cold chat, deliberately, at the point where a build is going
well. No context from the work in progress, no description of my plan, just the outcome and a
request for the shortest way to it. Handing it the plan does not work - it reviews the plan,
and reviewing the plan means staying inside it.
A domain expert interrupts you. The model will not, so that interruption is a step you schedule
for yourself...
15
24 comments
The AI Bias problem...
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+757
2
+731
3
+528
4
+480
5
+463
Powered by