bugrasa (@bugrasa) header
bugrasa (@bugrasa) profile picture

Founder of @evaonlineai. One prompt, four AI models, side by side. Sharing what I learn building it in public.

Joined August 2010
In this test, four AI models agreed on the facts. They differed in tone and in what they added. One line, three readers. Claude and Gemini added a retention angle nobody asked for. Gemini also went with "supercharged". GPT-6 Astra kept each line to one sentence. Compare them before you trust one: evaonline.ai
43
Qwen4 Max picked the available GPU in our fictional inventory test, then said its fit for the workload wasn't documented. That's the line I care about. Add an explicit unknown to your next test, and check whether the recommendation keeps it unknown.
32
Replying to @darekgusto
pagodas, with a camera orbit. I'd love to see whether the roof geometry holds up from the back too
1
1
6
Replying to @jonson_coder
Ship the same acceptance test with each output so readers can compare working behavior alongside time and cost.
7
Replying to @Angaisb_
Were both models given the original SVG source or only a screenshot of the demo?
1
247
What changed most when you removed the coordination rules: task completion or how often agents repeated each other's work?
6
Gemini 4 Hydrogen's retry function rejected True as an attempt count. The independent local checks passed. That's a detail I want in a coding test: a value that looks like a valid integer in Python but shouldn't be accepted here. Put it in the prompt and test it.
6
Replying to @JamesMalsawm
What kind of coding are you comparing, building from scratch or fixing bugs in an existing repo?
1
34
Replying to @Shivanshu_360
I'd start with Claude for a bug fix with the failing test in the prompt rather than just the error message.
1
1
23
How do you attribute merged PRs when engineers use multiple coding tools on the same change?
12
"Don't promise a recovery time" belongs in the prompt for an outage reply. I care more about a clear next step than a reassuring guess. Give the model the confirmed facts, ask it not to infer a cause, and request a diagnostic step you can undo.
4
Which model would you choose to check another model's answer for factual errors?
0%GPT-6.1 Sol
0%Claude Opus 5.5
0%Gemini 4 Argon
0 votes • Final results
4
Replying to @a_shimanski
What connection between chats surprised you most once the agent linked them?
1
1
9
Replying to @kmeanskaran
Where does human approval sit before the model endpoint goes live?
Correct JSON wasn't enough to pick a CSV converter. All three models got our Nov 16 EVA sample right. Only Opus named Python's csv module as an alternative. I want that warning before reusing the code. Next test: a newline inside a quoted field.
10
The chart test tied on accuracy. GPT-6.1 Sol, Claude Opus 5.5 and Gemini 4 Argon kept the supplied values and labeled the axis. I'd check bar heights against the data before picking the chart I like looking at.
1
18
Replying to @vineerpasam
exactly. "no new dependencies" is a much more useful starting point than "pick the best stack."
2
Ran 7 everyday tasks through four models. The lesson I keep: asked for a 15-word LinkedIn hook, two models invented a lost deal with a dollar amount. To me, those were the tempting hooks to post. They were also deals that never happened.
2
Gemini 4 Carbon is selectable in EVA's Multi Chat. I wouldn't pick a default from the menu. Give it a finished task and decide what would make you keep its answer before running it.
17
A restored service doesn't explain the outage. In our Nov 7 test with fictional notes, GPT-6.1 Sol reported the recovery but kept the cause unconfirmed. Each sentence cited its source lines. I'd check those lines before sending, especially the sentence about the cause.
5
The sales summary got the increase right and left the cause alone. GPT-6.1 Sol cited the source rows in our fictional CSV test. My review would still start with the arithmetic. Then I'd delete any explanation the data can't support.
14