Armand Ruiz

Director Data Science & AI Elite

VP of Product - AI Platform @IBM

As the Director of AI Engineering at IBM, I lead the watsonx team, a global group of over 1,000 AI Engineers who work on cutting-edge Generative AI solutions for various industries. With more than 12 years of experience in AI, I have a passion for democratizing practical AI skills and empowering professionals to leverage AI to transform their business.

Previously, I managed IBM's Data Science and AI Elite, delivering complex AI implementations for hundreds of clients. 

I also led the product management of IBM Watson Studio and Watson Machine Learning, an AI platform used by hundreds of customers and SaaS apps powered by AI. I hold a Master of Science in Telecommunications from Universitat Politècnica de Catalunya and speak three languages: Spanish, Catalan, French, and English.

Connect with me!

✉️ JOIN MY NEWSLETTER: Every Saturday morning, you'll get 1 actionable tip to launch and grow your AI strategies in business in less than 4 minutes. → GO HERE: https://www.nocode.ai/

📧 Email: armand@nocode.ai
X: @armand_ruiz


"It is kind of fun to do the impossible"
All opinions are my own and don't represent my employer.

Director watsonx team - Client Engineering

I am building the world's largest team of 𝐀𝐈 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 by

- Recruiting hundreds of new engineers around the globe
- Reskilling our existing talent
- Offering them top-quality training in new-generation AI

Responsible for Pre-Sales Generative AI Pilots with the new IBM watsonx.ai Platform.

I’ve been practically living in Claude Code lately. If you build with AI daily, you know that your orchestration workflow is just as important as the model itself.

Recently, Boris Cherny (the creator of Claude Code at Anthropic) shared the internal best practices and workflows his team actually uses on a daily basis. 

Someone brilliantly distilled those threads into a structured CLAUDE.md file that you can drop straight into the root of any project.

It essentially acts as a system prompt that turns Claude into a much more autonomous, rigorous engineering partner.

Here is what the file enforces:
1/ Workflow Orchestration: Mandates a "Plan Node Default" for any task over 3 steps and uses subagents liberally to keep the main context window clean.

2/ The Self-Improvement Loop: This is the real magic. After ANY correction, it updates a tasks/lessons.md file. You are building a compounding system where the mistake rate drops over time because it actively learns from your feedback.

3/ Verification Before Done: It cannot mark a task complete without proving it works (diffing behavior, running tests, checking logs). "Would a staff engineer approve this?"

4/ Autonomous Bug Fixing: Zero hand-holding. You point it at failing CI tests or error logs, and it goes to work without requiring constant context switching from you.

5/ Strict Task Management: Forces a "Plan First" approach written to a todo.md with checkable items before implementation even starts.

It forces the AI to prioritize simplicity, find root causes instead of temporary fixes, and minimize the blast radius of its changes.

If you are spending hours a day in the terminal with AI, setting up a strong .md instruction file like this will save you a massive amount of time and frustration.

It takes time and effort to set this up. If you do, you are ahead of everyone else.

If your employer isn’t providing unlimited Claude Code + secured MCPs to connect your enterprise repos, email, work-chat, meeting AI transcripts, calendar, and docs... they are likely moving at legacy speed. 

Without that context and tool access, you’re stuck in a cycle of manual copy-pasting and reinventing the wheel while the rest of the market moves in parallel workflows.

My advice? Don’t wait for the corporate roadmap to catch up. If you aren't getting these tools at work, force yourself to learn these agentic workflows on the side. 

When companies move this slowly, they eventually run into trouble and you don't want to find yourself at a disadvantage in today's market because your professional environment kept you in the past.

Stay curious and keep your skills ahead of your company's tech stack.

Everyone's talking about which LLM is best for agents. But after reading Lance Martin's deep dive into Manus's architecture, I'm convinced the real differentiator isn't the model. It's the context engineering around it.

The problem: A typical Manus task makes ~50 tool calls. Without careful management, results pile up in the context window and the LLM gets dumber the longer it runs. 

Anthropic calls it "attention budget depletion." 

Chroma calls it "context rot."

Manus solves this with three strategies:
𝟏. 𝐑𝐞𝐝𝐮𝐜𝐞: Older tool results get compacted to file path references. When that's not enough, the full trajectory gets summarized via structured schema.

𝟐. 𝐎𝐟𝐟𝐥𝐨𝐚𝐝: Fewer than 20 atomic tools bound to the LLM. Everything else runs in a sandbox via bash. The model stays lean.

𝟑. 𝐈𝐬𝐨𝐥𝐚𝐭𝐞: Sub-agents exist to give each task a clean context window, not to mimic human roles. No context bleed.

On top of that, Manus doesn't commit to one model. It routes tasks; Claude for code, Gemini for multimodal, OpenAI for math. 

Model-agnostic by design.

The takeaway: Manus has been refactored 5 times since launch. If a stronger model doesn't improve your agent, your engineering is the bottleneck.

Stop obsessing over which model to pick. Start obsessing over the implementation around it.

Full article: https://lnkd.in/gaY3rAV5

Prediction: Token budgets will soon surpass human salaries.

We are entering an era where the cost of compute for reasoning is becoming a primary line item, and the numbers are scaling fast.

I am already seeing developers consuming $100k+ a week in tokens.

It sounds astronomical, but when you look at the output, the ROI is there. They aren't just running a single chat thread; they are spinning up massive parallel processes. Swarms of agents coding, debugging, testing, and architecting simultaneously. The velocity is incredible.

But at that scale, cloud inference costs become the bottleneck.

The big unlock? Local Compute.

Putting a Mac Mini (or equivalent high-performance local hardware) on every developer's desk to run local models is the inevitable next step. We need to move the heavy lifting to the edge to make this sustainable. 

Invest $10,000 on a local computer and you have unlimited AI.

This creates a massive new need for the Enterprise: Fleet Management for Models.

Just as we manage laptops with MDM, companies will need a way to manage these distributed AI systems; securely pushing the latest Open Source models to local machines, updating weights, and orchestrating the workflow between local "thinking" and cloud "verification."

The future is hybrid, and the infrastructure to support it is being built right now.

I’m building my Personal OS to automate my mental overhead. For now, it’s simple, but the potential is already showing. I’ve moved away from "checking notifications" to a Pulse-based system.

How it works: 
1️⃣ Orchestration: Claude.md acts as the central hub, invoked by a launchd scheduler. 
2️⃣ Sequential Logic: Every "Pulse" (Morning/Midday/EOD) triggers a sequence of my agents: Scout → Horizon → Focus. 
3️⃣ Multi-Channel Delivery: I get a unified briefing via macOS notifications, an HTML digest, and my terminal.

The Agent Roster:
- Scout (/scout): Google Chat & Email monitor. It knows my VIP list and drafts replies before I even see the message. If something is important it will notify me, and even give me a call.
- Horizon (/horizon): The calendar expert. No more walking into meetings cold.
- Focus (/focus): The filter. It turns the noise into a top actionable list.

I feel spend less time "managing" my day and more time executing it. 

I also turn all the context for the day ahead into a fun podcast, and that gets me ready for the day and fully prepared.

I've been using computers in a completely different way lately. No much clicking. No browsing through tabs. No filling out forms. I describe what I want done, and agents go do it.

Many are still building software for humans. Replicating existing apps with AI. 

But that's not where this is going. The moment I stopped thinking of myself as a "user" and started thinking of myself as an orchestrator, everything changed. I set goals. I define constraints. I verify outcomes. That's it. The entire middle — the actual work — I don't touch it anymore.

And now I can't unsee it: most software we're building today is already obsolete. It's designed for humans to operate. But humans aren't going to be the operators anymore.

The new generation of software won't have dashboards. It won't have onboarding flows. It'll have APIs, state machines, and feedback loops built for AI agents, not for people.

The real question isn't "how do we develop this product/feature for humans using AI?" --> It's "if no human ever had to touch this, what would we build from scratch?"

if you are in a leadership position, you are punishing your team by keeping them busy.

If your team is too busy doing their "normal jobs" to spend hours a week experimenting with AI, you are failing them.

You are setting them up to be replaced by people who have the time to learn.

They will get disrupted, either by another department within the company or by a competitor, not because of AI, but because of your lack of urgency and understanding of the current landscape.

You have to give people the time, because integrating AI into daily workflows isn't something that happens overnight.

You have to actively remove work from their plates so they can learn the new way to work.

Because we are now all beginners again.

If you don't give them the time, they will never learn it, and your company will suffer a slow, painful decline into inefficiency.

No matter how big you are.

you need to clear your calendar and invest in AI implementation for your own productivity asap

The hardest part isn't the technology. It's making the time to actually sit down and try it.

Block 2 hours a day. Thank me later

Parallelism is the biggest unlock in AI. The real shift isn't speed; it's concurrency.

 I can now run 10 "hard things" simultaneously while I'm in meetings.

My workflow has flipped:
- Old way: Block time to do the work. Maybe use AI to do it faster.
- New way: Block time to review the results and give more context knowledge to the AIs.

We are moving from being "doers" to orchestrators. Your output is no longer limited by your hours, but by the number of parallel streams you can manage.

I get 100s of emails and chats daily. The only way to manage it is to stop everything, dive in, and manually filter the signal from the noise. It's inefficient and a total focus-killer.

So i built Mark, my Communications AI Agent. Its job is simple:
1/ Monitor Everything: It watches all my inboxes and chats 24/7.
2/ Surface What Matters: It identifies critical messages and ignores the rest.
3/ Notify Intelligently: I get a clean Terminal and Desktop notification with a summary file. No more context switching.

But that's just the start. The real magic is next → I'm connecting Mark to a shared knowledge base of all my documents, past conversations, and daily meeting notes.

Soon, it won't just notify me. It will draft context-aware replies for almost everything.

That's my way to solve this. I'm curious...have you developed something similar?

I moved from the EU to the US more than 10 years ago, and while I miss many things about Europe, I have to agree with the man of the hour 🦄 Peter Steinberger : the US is an incredible place for builders right now. 

There's an undeniable energy and enthusiasm here that's hard to find elsewhere. 

It feels like a special time to be building here.

Manus just shared why most people are still stuck in the "chat" era: the real value has shifted from conversational bots to custom superagents.

Chatbots answer questions; superagents execute workflows. 

But they aren't magic, you need to understand the underlying mechanics and put in the time to customize them for your specific needs. If you treat them like a standard search bar, you’re leaving 90% of the value on the table.

Here is how to actually get them to work for you:
1/ Move from Prompting to Engineering: Stop asking "Can you do X?" and start defining the architecture of the task.

2/ Invest in the Setup: Spend the time upfront to define personas, data sources, and specific tool-use constraints. The more "narrow" the agent's focus, the higher the quality.

3/ Iterative Refinement: A superagent is never "done." You have to monitor the execution and tune the instructions based on real-world failures.

Swipe through for the tips that actually matter for high-stakes execution.

Manus Intro

What’s the point of buying software when you can just create it on the fly?

It might take our generation a minute to adapt, but the next generation is growing up expecting to build exactly what they need. For them, the only thing that matters is the infrastructure to power it.

I’ve been building non-stop lately. I’ve never felt this empowered in my career. I can literally turn my ideas into reality in a matter of hours.

yesterday at the gym I heard someone pitching their new AI tool that helps you “do more, faster.” i feel like doing less and slower. am i the only one?

ok, so you moved from a chatbot to an AI agent. and you think you are ahead already.

but if you are still the one triggering all the actions...

if the agent isn't working autonomously for you all day long...

and if you don't have 10 of them running in parallel...

you are nowhere close to calling yourself AI-native. 

i recommend you spend the weekend learning. this is a good place to start: https://lnkd.in/eW4Sam_6

Every PM should understand evals. Not "be an expert." Not "build the eval framework yourself." Just understand them.

Here's why.

A/B testing changed product management forever. Before it, PMs guessed. After it, they measured. Evals are doing the same thing for AI products and systems but most PMs have heard the word but they don't know what they're talking about. 

An eval is how you answer one simple question: "Is my AI actually good?"

Not vibes. Not "it seems better." Not "the demo looked great." Actual, measurable, repeatable quality assessment.

Here's what you should tell tell your product leads:

1. Start with a golden set: a curated dataset where you know the right answers. This becomes your source of truth.

2. Define your graders: what does "good" look like? Accuracy? Tone? Factual correctness? Be specific.

3. Run your model against the golden set and score it. That's your baseline.

4. Every time you change something - new prompt, new model, new data — run evals again. Did it get better or worse?

5. Automate this. The speed of your eval loop determines how fast your AI improves.

That's it. That's the core.

The teams that ship reliable AI products aren't the ones with the best models. They're the ones with the best evals practice.

If you're a PM working on anything AI-related and you can't answer "how do we know it's good?"... start there.

Evals are the new A/B testing. And just like A/B testing, the PMs who get it early will have a massive advantage.

Manus Agents just launched on Telegram and it changes how you interact with AI agents entirely. I've been using this all weekend non-stop.

This isn't a chatbot bolted onto a messaging app. It's the full Manus — reasoning, multi-step task execution, tool use — running inside a conversation you already have open.

Here's what makes it different:
1/ Zero setup friction. Scan a QR code. You're connected in under a minute. No API tokens. No config files. No terminal.

2/ Full task execution from chat. Research, data processing, structured reports, PDFs — initiated and delivered without ever leaving the conversation.

3/ Multimodal by default. Send a voice message, a photo, a document. The agent transcribes, interprets, and acts. No manual file handling.

4/ It remembers how you work. Set your communication style — concise, structured, conversational — and it adapts across every interaction.

5/ You pick the model. Manus 1.6 Max for deep reasoning and creative work. Manus 1.6 Lite for fast, everyday tasks. Both go end-to-end.

But here's what got my attention even more — the cofounder just shared what's coming next:

1/ Create your own specialized agents and plug them into any group chat.

2/ WhatsApp, LINE, Slack, Discord support landing soon.

3/ Native Windows and Mac apps that let Manus operate your computer — like Browser Operator, but way more powerful.

And a lot more already in the shipping pipeline. Big updates dropping over the next 30 days.

Your AI agent shouldn't live behind a login screen on a separate platform. It should be wherever you already are — one message away, ready the moment you need it.

Learn more here: https://lnkd.in/gSuAx5UX

trust your AI overlord and... just hit accept 🤣

Recently, I stumbled across a YouTube video that completely stopped me in my tracks.

An urban explorer infiltrates the abandoned IBM center on the Côte d'Azur in La Gaude in South of France. Hearing the narrator describe it as a "vestige of Silicon Valley" and seeing that massive concrete colossus sitting empty in the middle of the forest is absolutely heartbreaking 💔 

For me, that place wasn't just a building. It was pure magic. It was where my professional life truly began and where my life completely transformed.

Early in my career, I had the chance to visit this unbelievable, high-energy campus while I was interning for IBM in Belgium. I knew immediately I belonged there, and I did absolutely everything in my power to get hired and eventually, I earned my spot.

When I look at the footage of those abandoned offices and empty reception halls, I don't see decay. I see endless, vibrant memories:

- Going from a nervous intern to earning my first full-time role.
- Working late into the night and battling those early-career nerves before major presentations.
- Learning a completely new language (French!).
- The incredible lunches, coffee breaks and walks around the campus with colleagues who became amazing, lifelong friends.
- Spending hours on the campus soccer & tennis courts, both competing in tournaments and playing with colleagues. I also learned to play la pétanque!
- And most importantly, it’s where I met my incredible wife.

That campus was the launchpad that gave me the opportunity to eventually relocate to the US. 

Looking back, I can draw a direct line from walking through those doors in France to my time as VP of AI Platform at IBM, and to do now the most exciting work in my career in Silicon Valley.

The doors might be closed, but the energy of what we experienced there is still very much alive. 

I will forever be grateful for that chapter, those people, and those memories.

Link to the video: https://lnkd.in/gA-Wja2s

Open video: INFILTRATION d’IBM, le plus gros site abandonné de la Côte D’Azur mais aussi le plus Surveillé !!!  on youtu.be

INFILTRATION d’IBM, le plus gros site abandonné de la Côte D’Azur mais aussi le plus Surveillé !!! 

I thought I was a heavy AI user. Then my usage 3x'd in the last 30 days. The pace of change is accelerating and what was cutting-edge a month ago is now the baseline. The new default is managing AI agents, not just using them.

This chart below is my AI usage (tokens)

Aishwarya Srinivasan

AI@Fireworks AI | Global Speaker(100+ talks)| EB1-A Recipient| 570k+ Followers| AI Engineer| GenAI/LLM Inference| LinkedIn Top Voice| Author-What's Your Worth?| Startup AI Advisor| Angel Investor| Ex-Google,Microsoft,IBM

𝗙𝗼𝗿 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗶𝗻𝗾𝘂𝗶𝗿𝗶𝗲𝘀, 𝗰𝗼𝗻𝘁𝗮𝗰𝘁 𝗺𝘆 𝘁𝗲𝗮𝗺 𝗮𝘁 💌 partnerships@illuminate-ai.org

I write about:
- AI engineering
- Applied machine learning
- Generative AI Applications
- LLM/ LLMOPs (Training, post-training, inferencing)
- Fundamentals of Data science/ ML/ AI
- ML roles interview tips
- Learning roadmaps (beginner to advanced)
- Importance of personal branding for career growth

**All the posts reflect my own views and do not represent my employer.**

AI Advisor || Responsible AI Advocate || LinkedIn Top Voice - Data & AI  || Top 10 AI Influencer || EB1-A Receipt


Bio: 
Aishwarya currently leads the Developer Relations - Growth at Fireworks AI. She was previously at Microsoft for Startups as a Senior AI Advisor to help Y Combinator startups build machine learning solutions, leveraging core Microsoft/ OpenAI products. Prior to this, Aishwarya was working as a Data Scientist in Google Cloud and before that an AI & ML Innovation Leader at IBM Data & AI, where she was working cross-functionally with the product team, data science team and sales to research AI use-cases for clients by conducting discovery workshops and building assets to showcase the business value of the technology. She holds a post-graduate in Data Science from Columbia University. 

Aishwarya has been awarded Trailblazer of the Year by Women in AI in 2022 and Women of Influence by Business Journal in 2022. She was awarded EB1A - extraordinary ability visa for her contributions in the AI field.

She is an advocate for open-source technologies, and was an open source Developer Advocate for Deepchecks and Lightning AI, and a contributor to Scikit Learn. 


She holds a Patent Award (2018) for developing a Reinforcement Learning model for Machine Trading.

She has over 500,000+ follower base on LinkedIn and actively organizes events and conferences to inspire budding data scientists. She has been spotlighted as a LinkedIn Top Voice 2020 for Data Science and AI, which features Top 10 Machine Learning influencers across the world. 

She is an ardent reader and has contributed to the scholastic community. To spread her knowledge in the space of data science, and to inspire budding Data Scientists, she actively writes blogs related to machine learning on LinkedIn and Instagram: www.instagram.com/the.datascience.gal

Besides being a data junkie, she is a fitness fanatic who is into martial arts (Krav Maga) and yoga.

Senior AI Advisor

As an AI engineer, LLM Twin is an important architecture to understand.

An LLM Twin refers to a system where a language model is designed to represent the knowledge, writing patterns, and decision logic of a specific person, team, or organization. The goal is consistency and reliability, not novelty.

At its core, an LLM Twin is built around how information flows. Think of it as 4 steps:

1️⃣ First, content is collected from real sources: blogs, internal documents, posts, code repositories, or knowledge bases. This data reflects how the person or organization actually thinks and communicates.

2️⃣ Next, the data is structured for two purposes.
One path prepares instruction-style examples that help the model learn how to respond.
Another path prepares retrieval data so the system can pull relevant context at inference time. This ensures responses stay grounded in real material.

3️⃣ Then comes training and evaluation. Models are fine-tuned where appropriate, tested against clear criteria, and versioned before deployment. This step looks very similar to traditional ML workflows, just adapted for language models.

4️⃣ Finally, at inference time, user requests are combined with retrieved context and passed through the deployed model. Monitoring is critical here: quality, latency, and cost all need to be observed continuously.

Where is this used in practice?

✦ Personal or creator assistants that help scale writing and communication
✦ Company-wide assistants that maintain a consistent product or brand voice
✦ Internal tools that answer questions based on code, docs, or prior decisions
✦ Support systems that reflect how experienced engineers respond to issues

Why should AI Engineers understand this?
This architecture reflects how GenAI systems are actually built and maintained. It forces you to think beyond prompts and focus on data quality, retrieval design, evaluation, and long-term system behavior.

My 2 cents 🤌
This is a GREAT topic to build a portfolio project around!! 

Credit: LLM Engineer’s Handbook by Paul Iusztin  and Maxime Labonne. I really like how this book breaks down AI engineering clearly and goes deep into different GenAI system architectures without hand-waving.

Over the past few months, Arvind and I've delivered seven deep technical workshops across agentic AI, RAG, context engineering, AI evals, MCP, vibe coding, and more.

One theme kept coming up: you want something more structured. Not just standalone sessions, but a clear end-to-end roadmap from A to Z.

So that’s what we’re building.

A structured, comprehensive course for:
- Hands-on builders: software, AI, and ML engineers
- AI product managers
- Tech leaders and CXOs looking to upskill meaningfully

Before we finalize it, I’d love your input. I’ve created a short survey to understand where you are, what you want to learn, and your career goals.

It takes under 10 minutes.

As a thank you, you’ll receive an additional 10% discount when we launch the course soon 🫶

Survey: https://lnkd.in/gQYeBCRP

No alternative text description for this image

Here’s my honest pattern with almost every AI tool I try.

I end up using a lot of tools, usually early access. After repeating this cycle enough times, I realized my reactions are almost predictable.

👉First hour
There’s real excitement.
I’m clicking around, testing odd prompts, trying things that used to fail. No strategy yet, just my curiosity and momentum.

👉Next few hours
I start comparing.
Where would this actually fit in my work?
What would I stop using if I kept this?
Is this clearly better, or just new?

👉Later that day
I experiment without guidance.
I skip the docs and examples on purpose. I try incomplete ideas, messy workflows, prompts I would never put in a demo. This tells me more than any tutorial ever could.

👉Day two
Then I look at the examples the team shared.
They usually work smoothly. They’re polished. They show the tool at its best, which is exactly what they’re meant to do.

👉After a few days
This is where the real understanding kicks in.
I start tweaking those examples. Changing assumptions. Using it in ways that feel realistic, not ideal. That’s when the boundaries show up. Not frustration. Just clarity.

Here’s the takeaway I’ve learned the hard way:
If you haven’t noticed limitations yet, you probably haven’t pushed the tool very far.

And honestly, if I use something consistently for three days and still can’t find a meaningful flaw, that’s rare. That earns real respect.
I haven’t experienced that yet.

Curious how others see this.
Are there tools you’ve used deeply where the limits still haven’t shown up?

Just a couple of weeks ago, Arvind and I hosted an in-person AI meetup with The Hub Bengaluru.

Over 300 people showed up in person.

Every single one of them was either already working in AI or actively trying to break into the space. The energy in the room was unreal. It genuinely felt like a room full of builders, practitioners, and people who are curious enough to go deep.

During the event, we rolled out a small challenge. We asked attendees to share a recap of what they learned, and we said we would pick one winner.

Really excited to share that Suraj V is that lucky winner 🎉
Suraj gets free access to all the The Gen Academy workshops we have hosted so far.

Huge congratulations, Suraj V!! 

Building The Gen Academy has always come from a very real observation that Arvind and I see every single day in our work. The adoption of generative AI and LLMs is moving incredibly fast, but the depth of AI engineering skills needed to build reliable systems is not keeping up.

There is a very real skill gap in AI engineering right now! There are so many curious souls who want to become AI engineers- but they aren't able to get those opportunities; and there are so many companies out there who  want to hire, but aren't finding the right talent. 

Our mission is to bridge that skill-gap!

As people who are deeply involved in this space, we felt a responsibility to help bridge that gap. Not just for people who are already experienced, but also for entry-level folks who want to build strong foundations the right way.

That is why our workshops are intentionally designed to be both intuitive and practical. We focus on theory that actually helps you reason about systems, and we pair that with hands-on demos where you build real things using modern toolkits and frameworks.

So far, we have hosted 6 workshops, and the response has been incredibly encouraging. We have trained 1500+ people already ❤️ 

Our next workshop is coming up on February 15th, and it will be focused on AI evaluations (link in comments)

Do follow The Gen Academy to stay updated on all our upcoming workshops.

Six months ago, Arvind and I started The Gen Academy with one simple goal- to create workshops that are deeply-technical, practical, cuts through the ton of noise out there, and that provides people clarity on building productive-grade AI systems.

So far we have trained 2100+ people. We’ve hosted 7 workshops, and consistently we’ve had 300–400 builders join us live.

The audience has been incredible.
- Software engineers moving into AI.
- AI engineers building LLM systems in production.
- Product leads thinking about reliability and evaluation.
- Directors and VPs from top tech and Fortune 500 companies who want to truly understand what’s under the hood.
- Even people from non-tech background who wanted to strengthen their technical fundamentals 

Recently, we hosted a workshop on AI Evaluations.

And this one felt especially important.

Because evaluating non-deterministic generative systems is fundamentally different from traditional ML evaluation.

We covered:

✦ How to evaluate non-deterministic generative AI systems
✦ How to think about benchmarks and what they actually tell you
✦ How to design your own evaluation dataset
✦ How to choose the right metrics for qualitative and system-level evaluation
✦ How to combine human evals, code-based evals, and LLM-as-a-judge
✦ A hands-on walkthrough so this isn’t just theory

If you’re building LLM applications, RAG pipelines, or agentic systems, evaluation is not optional. It is the difference between a demo and a reliable product.

If you missed the live session, we’ve shared the recording here: https://lnkd.in/gzMdbfWH

We’ll continue building these workshops for engineers who want to go beyond experimentation and into production.

More coming soon, so do follow us & The Gen Academy to get updates on our next workshops.

5 days to go! 
Arvind and I are super excited to be hosting an AI evals hands-on workshop on February 15.

It’s a 90-minute session where we’ll cover the fundamentals of AI evaluations and then actually do it together. You’ll walk away having built and reasoned through real evals yourself. 

If you’re aspiring to be an AI engineer or planning to upskill for AI roles in 2026, understanding how to evaluate LLM applications is critical.

Building an LLM app is often the easy part. Knowing whether it truly works in production is where most teams struggle.

LLM evaluation is not just about correctness anymore. You are judging usefulness, safety, faithfulness to sources, consistency across runs, cost, latency, and real user outcomes across prompts, RAG pipelines, tools, and agentic workflows.

Because this is hard, many teams fall back to vibe-evals. If a few outputs look good, they ship. That approach breaks quickly when models change, prompts regress, retrieval fails, or user behavior shifts. Without evals, problems surface only after users complain.

Why learning evals matters:
✦ Evals turn LLM development from guesswork into engineering
✦ They help catch regressions as models, prompts, or tools evolve
✦ They are essential for scaling RAG systems and agentic workflows
✦ In 2026, strong teams use hybrid evals combining automated metrics, LLM-as-a-judge, and targeted human review

Evals are no longer optional. They are a core AI skill.

In this workshop, Arvind and I will walk through how AI evals are done in real systems, with hands-on exercises so you build intuition.

This is designed for AI engineers and tech leads building systems, and even business leaders who want intuition for what “good” really means in production. Even if you are a beginner, don't worry, we will give you the foundations for you to understand everything comprehensively, and enough resources that you can review at your own pace.

If you want to level up your AI skills for 2026, register here:
https://lnkd.in/dQSR7yhU

Evaluation Resources

Fine-tuning is going to be one of the biggest focus areas for AI engineering teams this year.

We’re past the stage where calling an API is enough. The teams creating real leverage are the ones adapting models to their own data, workflows, and edge cases. Out-of-the-box models are powerful, but they are generic. Fine-tuning is where enterprises unlock meaningful efficiency gains and build real differentiation.

If you want to upskill in AI engineering, this is a topic you cannot skip.
Arvind and I are hosting a deep, hands-on workshop on Fine-Tuning LLMs.

In 90 minutes, you’ll learn:
✦ When fine-tuning makes sense and when it does not
✦ How SFT, RLHF, and DPO fit into real-world pipelines
✦ An end-to-end, code-based demo from raw data to a specialized model
✦ How to evaluate true performance improvements and avoid production pitfalls

This session is designed for software engineers, AI engineers, and data scientists, and it is equally valuable for product managers, solutions architects, tech leads, and executives working closely with model ecosystems.

If you want to move from using LLMs to actually optimizing them, this workshop will give you a practical framework to do it: https://lnkd.in/g-5gHrsY

In 2026, AI isn’t judged by a wow factor anymore.
It’s judged by whether it actually improves your workflows.

One of the most common questions I get from founders and teams I advise is how to automate go-to-market and sales properly. Real GTM automation needs deep ICP research, clear definitions, personalized messaging, and credible sources. This isn’t a one-prompt problem.

Normally, building a solid GTM or sales report would take me several hours, even with existing AI tools helping with research.

I recently got early access to Airtable’s new Superagent, and what impressed me was the approach. It didn’t treat my request as a single task. It broke it into ~16 steps, ran multiple agents in parallel, did deep research per subtask, cited sources, and stitched everything together into one structured output called a Super Report.

I used it to build a technical, informational report on AI for GTM/Sales in minutes. No fluff. No hallucinations. Just deeply researched content I could actually use with business leaders.

If your work involves building reports, decks, or MVP websites that need accuracy and depth, this feels less like “AI that makes things pretty” and more like AI that does real work.

Do check it out here: https://lnkd.in/gDkfSSG2

PS: You can get 2 months free for @Superagent, using code: AISH2FREE

#SuperagentPartner, #ad, #SuperagentbyAirtable

taplio

The Battle

Armand Ruiz

Aishwarya Srinivasan

Followers

Posts

Engagements

Likes

Performance ScoreArmand Ruiz's LinkedIn Performance

Performance ScoreAishwarya Srinivasan's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Armand Ruiz

Aishwarya Srinivasan

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Armand Ruiz's LinkedIn Performance

Performance ScoreAishwarya Srinivasan's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreArmand Ruiz's LinkedIn Performance