Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More

Owned by Duy

💰 Build toward $20k+/month with AI services clients keep paying for. Explore: https://www.orchestero.com

56 contributions to The AI Advantage
One AI habit worth keeping: ask "where did that come from?"
AI answers sound confident whether they're right or wrong. That's the thing I think everyone should keep in mind, especially for anything involving money, health, law or numbers. A simple habit: when an answer matters, follow up with "Where did that come from? Give me the source, and tell me which parts you're unsure about." Two things happen. Sometimes it points to a real source you can check in a minute. And sometimes it admits that part of the answer was a guess, which is exactly what you needed to know. It doesn't make AI less useful. It makes it more useful, because you know which parts to trust and which parts to double-check before acting on them. Has an AI answer ever sounded right but turned out to be wrong for you?
Ask AI to interview you instead of writing for you
If you've ever asked AI to write something and it came out sounding like… AI, try flipping it around. Instead of "write a LinkedIn post about my business", say: "Interview me about my business, one question at a time. Ask follow-up questions when my answers are vague. After 8 questions, summarize the three most interesting things I said." The questions pull out real stories, numbers and opinions that a generic prompt would never know. Then you write from that summary, or ask it to draft using only what you said. It works for bios, sales pages, reflection, even planning your week. The best material was already in your head. You just needed someone to ask. What would you want AI to interview you about?
1 like • 20h
@Michal Vavak Great addition. A rejected sentence with a reason teaches more than "sound natural" ever will, and keeping those rules beside the interview answers means the draft gets both your material and your voice.
0 likes • 4h
@Henrietta crystal Spady Yes, I'd add that question. Asking what it might have misunderstood before it drafts catches wrong assumptions while they're still cheap to fix, and your rule about separating exact statements from interpretation fits right next to it.
An export matters when you want to leave
For this Hermes Agent example, sample input: A sample service stores valuable work but offers no usable bulk export. Include exit requirements in the comparison before the team becomes dependent on it. What would you need to recover if you changed tools next year?
0 likes • 3d
@AI Advantage Team Thanks, Erika. The first thing I would want is the history behind the work, not just the final files: who changed what, when, and what was approved. Next would be the settings and templates that took time to tune. If an export keeps the content but loses those links and decisions, rebuilding them is usually the expensive part.
2 likes • 2d
@Henrietta crystal Spady That is the test I would run too. Pick one finished project and try to rebuild it in a different tool from the export alone: the files, the prompts, the attachments, and which approval covered which version. Any point where someone has to log back into the original service to fill a gap shows exactly what the export is missing.
The integration exists but cannot perform the needed action
When evaluating Hermes Agent, a fictional connector can read contacts but cannot update their status. The decision I would test: check the required operation, not merely the name of the integration. Which read-versus-write distinction has surprised your team?
3 likes • 4d
@Henrietta crystal Spady Yes, that is a distinction I would include in the proposed evaluation: operation absent, operation available but permission denied, and operation attempted but not saved. Each needs a different explanation and handoff. None should be reported as a completed update without reading back the intended saved state.
1 like • 3d
@Henrietta crystal Spady Agreed. Inspecting the record before any retry is what stops an uncertain save from being applied twice. Your three-part failure message is a good standard too: what was attempted, what is confirmed, and what still needs a decision.
A tool demo uses cleaner data than your team has
For a proposed Hermes Agent workflow, what imperfect input would you bring to a vendor evaluation? A sample demonstration uses complete spreadsheets while the proposed client data has missing rows. Test a representative imperfect input before treating the demo as evidence of fit.
2 likes • 5d
@AI Advantage Team I would start with a redacted enquiry export containing missing quantities, duplicate rows, and two versions of the same product code. Before running the proposed flow, I would label which records are safe to process and which need a question back to the customer. Then I would check whether it preserves those distinctions instead of filling the gaps with plausible values.
1 like • 4d
@Henrietta crystal Spady Yes, if an invented quantity is presented as a source fact or used in an order, I would fail that test even if every easy row passes. A separately labelled estimate requested by the user is a different case. For this evaluation, missing quantities should remain missing and appear in the exception report; completing the sheet is not the success criterion.
1-10 of 56
Duy Bui
6
1,341 points to level up
@duy-bui-6828
I help AI automation builders land their first client and deliver reliable systems. Explore: https://www.orchestero.com

Active 3h ago
Joined Dec 29, 2025
Ho Chi Minh City
Powered by