Jafari Sharib

Building agentic AI workflows and multi-agent systems. Full-stack engineer. Java craftsman. Based in Berlin.

[Jafari Sharib @SharibJafari]

There's no such thing as a decision without a downside. You're always picking the least bad tradeoff you can live with. So here's the test I run on every ADR I review: if the "Consequences" section reads like nothing could go wrong, it isn't finished yet.

[Jafari Sharib @SharibJafari]

ADRs get a bad rep.

I've written and championed them for years, so I'll say it plainly: that reputation is earned by ADRs done badly. It isn't a problem with ADRs.

[Jafari Sharib @SharibJafari]

Can we detect it earlier? Do we put a guardrail around it? Or do we look at it and decide it's a risk we can live with? Any of those is a fine answer. Inheriting the failure quietly, because nobody wrote it down, is not.

[Jafari Sharib @SharibJafari]

If you're running a multi-agent pipeline, this is probably its weakest link: nothing checks whether the agents reasoned correctly, only whether they produced output. Add a skeptic and don't let it see the code, so it has to judge the argument rather than redo the work.

[Jafari Sharib @SharibJafari]

I built a multi-agent code review pipeline, and deliberately barred one agent from seeing the code.

It's a critic. Its job isn't to find bugs. It's to judge whether the other agents reasoned well: did they back their claims, or just wave their hands?

[Jafari Sharib @SharibJafari]

The critic sees only the aggregated report. No diff, no source. That sounds like a handicap, but it isn't.
Give the critic source access, and it stops critiquing and starts reviewing. Keeping the code away from it forces it to interrogate the reasoning.

[Jafari Sharib @SharibJafari]

Once the scope is at the top, the rest falls out of it. How hard you escalate depends on it; how carefully you assess depends on it. Background goes last, because at 3 am, nobody reads the architecture section first.

What's the one line you wish every runbook opened with?

[Jafari Sharib @SharibJafari]

Most runbooks are written to be complete, not to be read during a 3 am panic.

That's understandable. There's no agreed-upon standard for how to structure one, so people optimise for what they can measure, and end up with a thorough document that nobody can actually navigate.

[Jafari Sharib @SharibJafari]

The first beat is the one everyone skips: scope. Before a single step, tell me the blast radius, and put it in numbers. Not "this could affect performance." How many replicas are in play, how much concurrency, whether this is one customer or the whole fleet.

[Jafari Sharib @SharibJafari]

It was amazing to see how the students were grasping each concept and highlighting the limitations and trade-offs that a framework usually abstracts away.

If you want to truly understand AI agents, build one without the abstractions.

#AIAgents #HandsOn #42Berlin #SAP #Java

[Jafari Sharib @SharibJafari]

Why I taught AI agents without using any framework:

Last week, I spent 3 hours at 42 Berlin. 20 students built an AI agent from scratch with me.

We used raw Java. No LangChain. No orchestration libraries. No frameworks. No SDKs.

[Jafari Sharib @SharibJafari]

The point was not to rebuild what already exists but to show what an agent actually does when it runs:
→ How it parses prompts and responses.
→ How it manages context.
→ How it calls tools.
→ How it decides the next step.

[Jafari Sharib @SharibJafari]

Ever lose track of time while coding for hours? 🙈
Long stretches aren’t always productive. I’ve found that 25 minutes of focused work + a short break keeps me balanced and sharp.
Try Pomodoro if you’re in a coding trance. It might just boost your focus!

#Productivity #WorkSmart

[Jafari Sharib @SharibJafari]

During a recent interview, I saw firsthand how discrepancies between a team’s language and the codebase can cause confusion. 🤔

Shape a language that keeps your code aligned with the business reality. Your team will thank you for it. 📚

#DevLife #UbiquitousLanguage #CodeClarity

[Jafari Sharib @SharibJafari]

As developers, we work on multiple levels: Personal, Team, and Product.

Let’s strive to be developers who think beyond our immediate scope and contribute to building products that matter.

Align with the bigger picture! 🏆

#DevLife #TechLeadership #ProductMindset

[Jafari Sharib @SharibJafari]

Simplicity in code is underrated. It's easy to write complex solutions, but it takes real skill to simplify. Clean, understandable code is easier to maintain and scale. ✨
#CleanCode #Java #SoftwareCraftsmanship

[Jafari Sharib @SharibJafari]

No one writes perfect code in isolation. Collaboration is key to building great software. Whether it’s pair programming or peer reviews, multiple perspectives make the code stronger. 🤝
#Teamwork #CodeReview #JavaDev