Agent Architectures in Practice: Patterns, Platforms, and Use Cases
Choose the simplest approach that handles the task, then test its failure paths.
TRAILBLAZER GARAGENotes on AI, data & useful software
Ideas you can understand.
Experiments you can try.
For the people deciding what to build, and the people making it work. Practical notes, honest trade-offs and small projects from Jhony Vidal.
Find your next read A GOOD PLACE TO STARTProduct decisions · 4 min read
Stop Making Users Repeat What Your App Already Knows
Your support tool has the order, the history and the policy. Why make someone explain it all to an AI assistant again?
TAKE ONE IDEA AWAY
Read the article Give a familiar task a useful action, with a result the person can check.
A SMALL PRODUCT DECISION 01
The app already knows.
↗Order #1042Delivery is running late✓
≡Delivery policyThe relevant information is attached✓
Less explaining. More checking.
DRAFT A REPLY
“I’ve checked your order. We’re waiting for a confirmed delivery date…”
Follow your curiosity.
Three ways into the notes.
01
Make a product decision
What should the feature do, and what should a person stay in control of?
Start with assistant memory02
Build it. Then check it.
Find the sources, inspect the mistakes and learn whether a change helped.
Start with evaluating answers03
Make room to learn
Choose what deserves your attention as the tools and the work change.
Try a two-week learning loopTHE NOTEBOOK
13 notes & countingSomething worth a closer look.
13 notes to explore
Digital Workers in the AI Era: Landscape and Strategies
Review tasks within a job and test what helps before making assumptions about whole roles.
How to Choose an AI Model for One Real Task
Compare useful completed work, including mistakes, review time and retries.
How to Evaluate RAG Without Fooling Yourself
Test finding evidence separately from writing an answer supported by that evidence.
Learn Faster Without Chasing Everything
Choose one recurring problem, practise recall and return to it after a gap.
Stop Making Users Repeat What Your App Already Knows
Turn a repeated task into a useful action, with a reply the person can check and change.
ON THE WORKBENCH / FLOWCHECKA retry shouldn’t
A retry shouldn’t
count an order twice.
A job runs, the connection drops, and someone tries again. Does the total change? Try two fictional events and see what should happen.
Explore the projectA small interactive illustration. The Python project lets you inspect the implementation.
TWO EVENTS. ONE RETRY.No account needed
evt-1 £12.00evt-2 £10.49Recorded events0
New events this run0
Order total£0.00
Ready. Process the two events to begin.
THE PERSON BEHIND THE NOTES
Hello, I’m Jhony.
I’m a software engineer working with AI, data and automation. I write down the decisions, examples and mistakes that are worth returning to. The goal is to leave you with something you can understand, question or try in your own work.