Hey @X algorithm
Show this to people who are actually building:
β’ AI agents
β’ Production systems
β’ LangGraph / FastAPI
β’ Real AI employees
Drop what youβre working on π
Letβs connect.
On a regular SIM call, your mobile network may tell you through a voice announcement when someone is busy or unavailable.
What if WhatsApp offered something similar?
Imagine choosing your preferred language in settings and hearing a short spoken explanation when a call fails.
For example:
- Recipient busy: a spoken busy announcement, if the app can confirm and disclose that status.
- Connection timeout: "The call couldn't connect."
- Unknown reason: don't guess.
Keep it optional, short, and available as text too.
The app should only explain what it actually knows and is allowed to disclose.
A small product UX idea inspired by traditional phone networks.
Would you use it?
This is an idea, not a feature I've built.
Testing Velix against different data structures exposed cases the existing approach could not handle.
I designed an improvement workflow and tested it end to end in development.
That validates the workflow in those tested cases. It does not establish support for every unfamiliar structure.
My takeaway: revisit the failing case after the change, rather than only demonstrating examples that already work.
Velix is a ProveinTech product in development/testing.
Alhamdulillah! Passed with 733/1000!
My journey preparing for the Claude Certified Associate Foundations certification:
1st attempt: 283 (unprepared)
2nd: 450
3rd: 683
4th: 600
5th: 733 PASSED!
Covered AI fundamentals, prompting, agentic workflows, Skills, Connectors, evaluation, workflow design, governance, security, and human oversight.
Five attempts. Countless lessons. One milestone.
Never give up. Alhamdulillah! π€
#AgenticAI #AIEngineering
Building Velix has reinforced an integration lesson:
The same business operation can sit on very different database structures.
I chose to work toward adapting the application to existing systems, rather than asking businesses to restructure their databases around it.
Testing exposed unsupported cases.
One working example does not establish broad compatibility.
Velix is a ProveinTech product in development/testing. Compatibility is still being evaluated.
A CMS publish succeeded, but refreshing the public site briefly showed older content while its configuration API request was pending.
I chose server-side rendering for the initial page so configuration could be fetched before the page was rendered.
That addressed the old-content flash I observed.
Trade-off: configuration fetching becomes part of the initial response path.
This was a rendering fix, not a universal cache-freshness solution.
A CMS snapshot bug I caught during verification:
Frontend logic inside a closure decided whether an update should create a snapshot.
Sometimes it did. Sometimes it did not.
I removed that decision from the frontend, moved it to the backend and verified the corrected snapshot behavior.
The issue was not closures themselves. It was letting frontend logic decide whether required version history was preserved.
I reviewed and fixed the existing implementation; I did not build the original feature.
Velix's intended fulfillment notification rule:
Owner marks an order fulfilled through a natural-language prompt β email the order's category manager.
Category manager does it β email the owner.
The initiating role determines the recipient.
End-to-end testing is pending. This describes the workflow design, not verified email delivery.
Next check: both role paths, the resulting order state and receipt by the intended person.
Velix is a ProveinTech product in development/testing.
@rwspatin Yes sure right now I'm doing multiple things like preparing for exam and different things but I building with these all https://t.co/YV2LOeEYw2 currently is in testing and developing phase by the way what are you building?