u/nbortolotti — reddlx

Why running at 100% capacity leaves 0% room for engineering improvement

Early in my technical leadership journey, I managed a team of exceptional individual contributors building complex, highly-distributed architectures. We were delivering features, but every sprint felt like a grind. We had hit a plateau — shipping code, but not evolving our systems. We were running fast, but we weren’t getting better. It wasn’t until we consciously shifted our focus from raw feature velocity to continuous team learning that our trajectory changed. This mirrors the cultural shift seen in high-performing engineering organizations that abandon the feature factory model, prioritizing long-term system adaptability and continuous learning over instant, unsustainable output .

Here some experinces about it: https://medium.com/@nickbortolotti/the-end-of-hero-engineering-building-teams-that-scale-beyond-individuals-64a72ef3df35?sharedUserId=nickbortolotti

Happy to get your thoutghs

u/nbortolotti — 1 day ago

▲ 4 r/agentdevelopmentkit

Beyond the Tutorial: Mastering Git with Agentic Workflow Graphs - ADK2

The Power of ADK Workflow Graphs in Technical Mentorship 🚀

How do we scale engineering mentorship effectively? Not with generic chat assistants, but with state-aware, execution-driven architectures.

In this article I break down how to use Google's Agent Development Kit (ADK 2) to build an Agentic mentor that connects directly with a developer's live workspace.

🛠️ The Architecture: Logic Meets Execution
Instead of only prompting, the system splits the responsibility using an ADK Workflow Graph:

The Cognitive Engine: Focuses on pedagogy and conceptual guidance (The "Why").
The Execution Engine: Validates real terminal and file system states deterministically (The "How").

💡 True Learning in the Flow
By mapping the learning journey as a graph with conditional routing, the developer never leaves their IDE. If they make an error in their local terminal, the workflow graph instantly intercepts it, validates the state, and serves a precise nano-learning moment right when it matters most.

If you are exploring agentic architectures, developer onboarding, or modern training frameworks, check out the full breakdown.

medium.com

u/nbortolotti — 3 months ago

▲ 1 r/AgentSkills+1 crossposts

Autonomous Efficiency Through Google Antigravity Skills

Are you interested in optimizing token usage?

https://medium.com/@nickbortolotti/the-agentic-shift-architecting-autonomous-efficiency-through-google-antigravity-skills-f2d213567fbe

By shifting from stateless prompts to a decentralized, autonomous agent workspace—using localized files like .agents/skills/workspace-rules.md and a root context.md—we recorded some staggering empirical data using gemini-2.5-flash:

📉 A 90% Collapse in Total Token Velocity:
* Without Autonomous Context: Simple tasks caused an open-ended cognitive loop, burning 1,217 reasoning tokens and producing bloated, expensive responses (~1,878 tokens total).
* With Autonomous Context: By establishing strict, discoverable local guardrails, speculative reasoning was entirely eliminated. Internal reasoning dropped to under 71 tokens, compressing total transaction costs to a mere ~200 tokens.

This isn’t just about cost reduction; it’s about deterministic execution at scale.

True AI agency isn't achieved by giving a model infinite freedom; it is achieved by engineering structured, self-documenting boundaries.

If you are architecting production-grade enterprise AI workflows for now, this structural shift is no longer optional—it is the blueprint for operational efficiency.

reddit.com

u/nbortolotti — 3 months ago