Building Agentic Solutions with AI: A Marathon, Not a Sprint

View profile for Sivas Subramaniyan

Designing Enterprise AI solutions

Building Agentic solutions that rely on a Language Model are wrappers offer no value add. An Agentic Architecture will have to be designed and engineered! Devising an architecture requires both an in depth understanding of the business goals and a deeper understanding of AI tools and the landscape. Making it both engineering and art. 1/ A good agentic design should be model agnostic and use case specific. Knowing to leverage Small Language models in orchestrating workflows is a breakthrough in managing costs, and latency. The NVIDIA paper Small Language Models are the Future of Agentic AI is a dialectical account of this -  https://lnkd.in/ghVhu9ur 2/ If you are thinking of knowledge management to models, think Context Engineering and not RAG. Actively & continuously structuring the inputs into an LLM’s context window is key to unlocking accuracy and minimizing hallucinations. This post by SRK summarises everything about Context Engineering - https://lnkd.in/g4ywnGdn 3/ Knowing how LLMs function involves making sense of the LLM’s Semantic layer ( can be called vibing !?). Being able to map business, technical, context data into a semantic structure that the LLM gets is a very practical and lived experience. Read this post by Zaher Alhaj https://lnkd.in/gkQhAn6A 4/ Planning of LLMs – Agentic Layers requires to plan at each step using inference time reasoning. Getting to know the right inference time reasoning techniques to use such that cost per task, latency, steps per task, context adherence are all optimized for is a skill. Knowing about all the planning techniques in a single place is here - https://lnkd.in/g4ZgAakD 5/ Agentic applications go from a POC to Production only using Evals. Evals enable to devise a structured approach to Test, Verify, Iterate to build Agentic applications. Evals is turning out to be the most fundamental value add for production ready systems. Hamel H. has been harking about it for more than a year see his FAQs for Evals here - https://lnkd.in/gPjMvNTt Beyond the hype that AI solutions can do magic and are transforming in breakneck speed. For Agentic AI to become a ‘normal technology’ is a marathon – steady in its own pace. Maturity in technology is the virtuous cycle Innovation -> Adoption -> Diffusion. https://lnkd.in/giaRmtPQ Lastly, an area that I personally believe will re define agent development is Post Training Language Models [PoLM]. There is a lot to learn and experiment here. Here is an encyclopaedia of it - https://lnkd.in/gk_TZ3B4 Keep it going AI PMs, AI Architects and AI Engineers !

Aravind G

Building NetoAI | Strategy, Product, Ops Leader | IIM-L | NIT-T

1mo

Sivas Subramaniyan Sharp post - appreciate the balance of engineering rigor and product realism. Model-agnostic design, context engineering (not just RAG), and disciplined evals are exactly how agentic apps move from POC to production. Exactly what PMs, architects, and engineers need, to explore real AI solutions - highly recommended.

To view or add a comment, sign in

Explore content categories