Suggestions
Nader Dabit
Director of Developer Relations at Avara
Nader Dabit is a Developer Relations Engineer at Edge & Node, where he focuses on building relationships within the developer community, particularly in the Web3 space. With over a decade of experience in software development, he transitioned to the blockchain sector in 2021, bringing a wealth of knowledge from his previous roles, including a significant tenure at Amazon Web Services (AWS) where he led developer advocacy for front-end web and mobile technologies.
Dabit has been involved in various projects related to Web3, emphasizing the importance of developer education and engagement in this evolving field. He has contributed to discussions on the "Web3-ification" of applications and has shared insights on the Web3 technology stack, helping developers navigate the complexities of building decentralized applications.13
In addition to his role at Edge & Node, Dabit has held positions such as Director of Developer Relations at Aave and has been active in promoting developer resources and community engagement in the blockchain ecosystem.24
Highlights
Agent infrastructure vs agent tools
- local agents are a tool for individuals
- cloud agents are more capacity for the org
- most companies treat them as a tool purchase, it's actually closer to hiring
- anyone can trigger workflows, so the codebase opens up beyond the eng team to the entire company
- cloud agents work across every codebase via a single interface
- agents become your interface to Slack, Jira, Sentry, databases, CI/CD, a universal interface to your entire eng stack
- backlog becomes parallel workstreams
- as you generate more PRs, review becomes the bottleneck
- review agents catch bugs, organize diffs, let you ask questions with full context
- it's not tool adoption, it's capacity deployment
Local agents are great for solo work, but remote / cloud agents scale to entire teams and across all devices.
Anyone can tag an agent in a chat or ticket and ship a change without touching a terminal, or even knowing how to operate one.
Also, one interface across every repo so you don't need a separate terminal tab per project, or a separate local checkout, or even a separate environment.
Conversations are tranparent and flow across multiple interfaces - Slack, Linear, Github, the @DevinAI web app...
Accessible from any device or phone, so you don't need your laptop, make updates via your mobile device or even voice.
Just tag the agent in a group chat to fix some outdated docs or pastes in a feature request from @x (see screenshot) or calls out a bug, and a PR shows up few minutes later.
This is the future of coding agents and is also how we use @DevinAI to build @DevinAI - a more in-depth writeup coming Monday!


