Doug Finke Profile picture
Jun 5 7 tweets 2 min read Read on X
I just completed three Microsoft AI Agent modules:

• Memory, State, and Evaluation
• Multi-Agent Systems and Orchestration
• Governance, Guardrails, and Operations

One thing stood out.

We've spent years talking about prompts.

The real challenge is systems.

🧵 Image
Memory = what the agent knows.

State = where the agent is.

Evaluation = how you know it succeeded.

A smart model without these is often just an impressive demo.
Then comes orchestration.

One giant agent is not always the answer.

Specialized agents working together can outperform a single agent trying to do everything.

Coordination becomes a first-class concern.
And then reality shows up.

Governance.
Guardrails.
Monitoring.
Auditability.

Building an agent is easy.

Operating one responsibly at scale is the hard part.
The industry spent years focused on:

"How do I write a better prompt?"

The next phase looks more like:

"How do I engineer a reliable AI system?"

Different problem.
Different skill set.
My takeaway:

We're moving from prompt engineering to system engineering.

Memory.
State.
Orchestration.
Governance.
Evaluation.

That's where things start getting interesting.
Modules:

Memory, State, and Evaluation
learn.microsoft.com/en-us/training…

Multi-Agent Systems and Orchestration
learn.microsoft.com/en-us/training…

Governance, Guardrails, and Operations
learn.microsoft.com/en-us/training…

#AI #Agents #AgenticAI #MCP #Copilot #MicrosoftLearn

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Doug Finke

Doug Finke Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @dfinke

Apr 3
The End of the Software Gestation Table 🧵

In "Software 2.0," we were agriculturalists. We’d get a task—a refactor, a new UI—and instinctively size up the Gestation Period.

Every project had its "Appointed Hour" before it could be born into the world.
We sized our work by a biological clock:

🐣 Chicken (21 days): A bug fix.
🐑 Lamb (5 mos): A new feature.
👶 Human (9 mos): A product launch.
🐘 Elephant (2 yrs): That legacy migration everyone fears.

We accepted the delay as the natural order of things.
As devs, we "lived in the end" of a working solution, but the "Bridge" to get there was a slow, rhythmic grind of syntax and manual debugging.

The struggle was the proof of the work. If it didn't take "Human" or "Elephant" time, it wasn't considered "real" engineering.
Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(