David Grizzanti

Early in my career everything was about building large scale homogeneous systems. What’s been more interesting over the last 5y has been heterogeneous multi cloud systems. The tradeoffs are more complex to build simple (irreducible complexity) and elegant systems in that space.

41

2 Comments

An agent has no consistent definition. You can think of an agent as an autonomous or semi-autonomous system that can take actions on behalf of the user in a given environment, state, and make decisions or take actions that can accomplish certain tasks along a given time-frame, either by calling tools, dynamically selecting the next action to take or use a deterministic "workflow" (systems where LLMs and tools are orchestrated through predefined code paths). Using an Agent framework that gives you the ability to built systems in both, a reliable and a dynamic way can accelerate your agent development journey using agent abstractions. This means building Agentic systems that can reliably call tools, store memory (episodic/semantic/procedural), have comprehensive logging and observability, human in the loop workflows and the ability to build various multi-agent patterns flexibly based on your use case. A successful Agentic system in production is usually a combination of both, dynamic and predictable/reliable multi-agent systems. Strands Agents SDK gives you exactly these capabilities by treating each “agent” as a combination of a foundation model plus a suite of tools. You define a prompt and register your tools (decorated functions) in code, then Strands handles reasoning→planning→tool-execution cycles, local testing, and cloud deployment (ECS, Fargate, Lambda, EC2), along with support for all other agent abstractions provided above. Excited to share a hedge-fund analyst multi agent system: This uses the newest Anthropic's Claude 4 Sonnet/Opus that powers the Lead Analyst Agent, routing incoming queries to specialized sub-agents for fundamental, technical, and market analyses. Each specialist is wrapped as a callable tool (using the “agents-as-tools” multi-agent pattern), so the orchestrator never has to implement domain logic itself and can handoff the task to an agent as a tool. For sensitive operations (insider lookups), we utilize a HITL approval step that halts execution until a human grants consent. We also use meta-tooling that enables the Lead Analyst to generate, load, and invoke new custom tools at runtime—whether it’s a portfolio beta calculator or a pricer—without redeployment. Strands also embeds observability (Langfuse) and OpenTelemetry tracing so you can trace reasoning events, tool invocations, errors, and end-to-end workflows in real time. View more information on the code implementation here: https://lnkd.in/gJmwVyGi Code implementation: https://lnkd.in/gzTtJvJq Thanks to 🏄‍♂️ Cagatay Cali for being a reviewer/collaborator on this! Feel free to try it out and reach out with any questions/ideas. #aws #agenticAI #strands #agents #generativeAI

60

6 Comments

Minimizing the dependencies of distributed systems, especially the fundamental building blocks, is one of the hardest but most crucial aspects of system design. It’s too easy to end up with cycles, typically transitive dependencies three or more nodes deep.

4

1 Comment

Most engineers think there's one way to be a Staff Engineer. There isn't. Will Larson identified four archetypes: Tech Lead — drives a single team's technical direction and execution Architect — owns technical vision across a broader domain Solver — drops into the hardest, most ambiguous problems wherever they are Right Hand — extends a senior leader's reach into areas they can't personally cover Most engineers default to chasing "Solver" because it scratches the itch that got them into programming in the first place. But your fastest path to Staff is the archetype that matches your strengths AND your org's needs. If your company is scaling fast, they need Tech Leads. If they're drowning in cross-cutting technical debt, they need a Solver. If a VP is stretched too thin, they need a Right Hand. Match the archetype to the opportunity. Don't force the one that sounds best on paper. More about navigating the path to Staff at https://www.evalx.dev

18

A lot shifted in 2025. AI made some things easier and other things more complicated, and it pushed teams to focus more on resilience. The 2025 State of the Internet Year in Review breaks down what stood out most this year. https://lnkd.in/eh2eZXfA

14