Voices

What people wrote about my work, in their own words, on the platform where they wrote it.

10 voices about General on LinkedIn · Show all

Enrique Barclay

Inside Sales Engineer @ Commvault | Ex-Founder, Digital...

On LinkedIn

The honest part is what makes this credible: the dark green Saturdays were debugging, not heroism, and agents deploying to the wrong project is the real texture of building this way. Your orchestration point is the whole thing. Knowing when to checkpoint, when context is rotting, when to kill a session, that is judgment, and it never shows up in a commit graph. I have felt the same shift: the code stopped being the constraint, and deciding what is worth building (then verifying it is actually real) became the job. How do you catch a session that has gone bad before it costs you, a smell test, or hard signals?

Marius Jost

SEO Services | ex-Burson-Marsteller | Connecting ...

On LinkedIn

OK, this opened my eyes. We will try this here as well now. I have heard from this approach and it does make sense. It had always been obvious to me that for certain tasks, the flagships are overkill (and you overpay). Thanks!!

VTI

Company page

On LinkedIn

Only 9 MCPs? That's practically a full dev team in disguise, Tali! It's impressive how far this approach can go before hitting the complexity ceiling.

Drish Mali

ML Engineer

On LinkedIn

Dr. Tali Režun Great insights! My 'AHA' moment was finally understanding that Phase 1 is the most important step. I used to spend all my energy on the build (Phase 2), but your framework helped me realize that rich, structured context is what actually allows agents to perform. Moving from a developer mindset to a product architect mindset changes everything. Thanks for sharing the playbook!

Carlos T.

Chef Projet, Msc (Santé publique en Controle des ...

On LinkedIn

For me, as a young entrepreneur/student and a novice in the use of AI, reading your articles has made me realise very quickly that AI is no longer a simple tool to be used as a mere 'shortcut'. It is a 'shortcut' system that I must fully master; I must integrate it; it is a guiding thread to boost my efforts and always go further and higher. To this end, I must research and adapt my documentation to the aim, objectives, and expected results, and above all, always remember to update my documentation.

For example, as a biologist and public health specialist, AI needs to be intelligently integrated into my daily workflow... Quality of results; client satisfaction; expanding my client base; selecting my community health studies; analysis, monitoring, and evaluation, etc....

Written in French

Johan Landman

CSGI

On LinkedIn

The articles reinforced for me that the real challenge with AI isn't technical adoption, but leadership readiness. As AI becomes embedded in day-to-day operations, leaders must understand the AI environment — its constructs, functionality, and solution boundaries — well enough to set the right guidance,… more

Carlos T.

Chef Projet, Msc (Santé publique en Controle des ...

On LinkedIn

Although I am no expert in all things IT and AI, I have read the various articles very carefully. My thanks to Dr TALI, as these articles are far from being mere academic papers; they also serve as a guide and a catalyst for our successful experiences with AI, and even for our activities unrelated to AI.
The driving force behind everything we do remains: our documentation. What do we want to achieve? Where will we find our information? When and how will we put it to good use? And above all, why use one form of documentation rather than another? Our documentation remains our cornerstone, for if it is used effectively and tailored appropriately, it will pave the way and facilitate the rest of our work. And the same applies to the use of everything surrounding AI to improve our daily lives.

Nouman Nawaz

Helping AI startups build investor-ready MVPs and naviga...

On LinkedIn

The 6-senior-devs estimate is the fork in the road for most non-technical founders. A few outsource it, a few kill the idea, and most end up with something built that was never quite what they meant.

What strikes me in your case study is the decision layer: 300+ orchestrator sessions, and you were the one deciding what should exist, not what should compile. That's the part nobody talks about. The orchestration tooling is getting good. The bottleneck is still the person who can hold the product vision clearly enough for 400 agents to stay aligned for 8 weeks.

Working with non-technical founders on their AI builds, that's where we spend the most time. Not on the models. On the brief.

Mislav Bašić

CEO at 4uHa

On LinkedIn

Dr. Tali Režun I've had some really inspiring chats this year with Drazen Kapusta and you. They helped me shape my goals for the year ahead. Cheers, and looking forward to seeing you again soon!

Marko Hodak

Freight, Logistics & Supply Chain Advisor | 15+ Years at DHL, ...

On LinkedIn

The level you reached and the amount of details on your hub is "out of this world". You are like a living database. There is nothing left to say, just to admire your work, and try to learn as much as possible from you. 👏