Posts Tagged ‘DeveloperProductivity’
[VoxxedDaysAmsterdam2026] Coding Fast and Slow: Managing Mental Energy for Sustainable Software Development
Lecturer
Baruch Sadogursky is a Developer Advocate at Tessl, focusing on package management for AI agent skills. A Java Champion with extensive experience in DevOps and software engineering, Baruch explores the intersection of behavioral psychology and programming practices to improve developer effectiveness and well-being.
Abstract
Software development demands significant cognitive resources, yet the mental costs of context switching, interruptions, and decision fatigue are frequently overlooked. Baruch Sadogursky applies insights from behavioral psychology, particularly Daniel Kahneman’s framework of fast and slow thinking, to examine how developers can manage mental energy more effectively. The presentation analyzes the biological and psychological mechanisms underlying attention, fatigue, and intuition, while offering practical strategies for preserving cognitive capacity throughout the workday. Topics include reducing unnecessary context switches, implementing deliberate work patterns, and leveraging AI tools with appropriate context engineering. These approaches enable developers to maintain high-quality output while avoiding burnout and sustaining long-term productivity.
The Dual Systems of Human Cognition in Programming
Human decision-making operates through two distinct cognitive modes. System one functions automatically, emotionally, and with minimal effort. It excels at pattern recognition and rapid responses but can lead to errors when complex analysis is required. System two engages deliberate, logical, and effortful thinking. It handles complex problem-solving and critical evaluation but consumes significant mental energy and operates more slowly.
In software development, system one drives much of routine coding activity. Experienced developers intuitively navigate familiar codebases, recognize common patterns, and make quick implementation decisions. This efficiency feels productive and satisfying. However, system one also introduces risks. Code that “looks okay” may contain subtle flaws that system two would identify through careful review. When mental resources are depleted, developers default to system one even for tasks requiring deeper analysis, resulting in overlooked issues and technical debt.
System two becomes essential for architectural decisions, debugging complex interactions, code reviews, and learning new technologies. The challenge lies in preserving sufficient system two capacity for these critical activities rather than exhausting it on routine interruptions and low-value tasks.
The Hidden Costs of Context Switching and Interruptions
Modern work environments are engineered to fragment attention. Email notifications, messaging platforms, meetings, and status updates create frequent context switches throughout the day. Each interruption forces the brain to reload relevant information, reestablish mental models, and regain focus. This process is metabolically expensive and significantly reduces overall effectiveness.
Research demonstrates that developers check email approximately 77 times daily on average. Attention spans on digital interfaces average just 47 seconds before shifting to another task. Returning to deep work after an interruption requires substantially more time than most people realize. The cumulative effect is reduced code quality, increased errors, and diminished creative problem-solving capacity.
Critically, developers often fail to recognize when their cognitive performance has declined. Similar to how tired individuals overestimate their driving ability, programmers working on system one may believe their code quality remains high. This self-assessment bias makes proactive management of mental energy essential rather than reactive.
Strategies for Preserving and Replenishing Cognitive Resources
Effective mental energy management requires both prevention of depletion and strategic restoration. Time blocking dedicates specific periods to focused work without interruptions. The Pomodoro technique, originally using 25-minute intervals, establishes minimum focused periods while allowing flexibility for natural flow states. When developers enter deep concentration, they should continue beyond the timer rather than forcing artificial breaks.
Task batching groups similar activities to minimize context switches. Responding to all messages during designated periods rather than reacting immediately preserves cognitive continuity for primary development work. Physical exercise, adequate sleep, and mindfulness practices support overall cognitive resilience. Sleep in particular serves as the primary mechanism for restoring system two capacity, making consistent rest non-negotiable for sustained performance.
Workspace organization and notification management reduce environmental triggers for attention shifts. Tools that intelligently manage calendars and protect focus time help implement these practices at scale. Delegation of routine tasks to appropriate automation or AI assistance frees cognitive resources for higher-value activities.
Engineering Context for Human and Machine Systems
Context engineering addresses both human and artificial intelligence systems. For developers, clear documentation, consistent coding standards, and well-structured codebases reduce the mental effort required to understand and modify systems. When context is preserved, system two can focus on creative problem-solving rather than basic comprehension.
Artificial intelligence systems similarly require rich context to perform effectively. Large language models benefit from detailed prompts, relevant examples, and domain-specific knowledge. The same principles that help human developers maintain context—clear boundaries, explicit documentation, and systematic organization—enhance AI performance when integrated thoughtfully.
Modern AI coding assistants represent both opportunity and responsibility. When used with appropriate context, they augment human capabilities without replacing critical thinking. However, over-reliance on AI without sufficient system two engagement can lead to acceptance of suboptimal code that appears functional but lacks deeper quality. Balancing AI assistance with human judgment remains essential for maintaining code integrity.
Building Sustainable Development Practices
Organizations can support cognitive sustainability through intentional practices. Protected focus time, reduced meeting loads during deep work periods, and recognition of the costs of context switching contribute to better outcomes. Engineering workflows that minimize unnecessary interruptions while maintaining necessary collaboration create environments where developers can consistently access their full cognitive capabilities.
Individual developers benefit from self-awareness of their energy patterns and implementation of personal systems for protection and restoration. Regular reflection on work patterns, experimentation with different techniques, and honest assessment of code quality under varying conditions build more effective personal practices.
The goal extends beyond short-term productivity to sustainable careers in software development. By treating mental energy as a finite and valuable resource, developers and organizations can achieve higher quality outcomes while reducing burnout and turnover.
Technology continues to evolve, with AI assuming more routine tasks and shifting human roles toward system-level thinking and creative problem framing. The ability to manage cognitive resources effectively becomes increasingly valuable in this landscape. Developers who master these skills will maintain their effectiveness and competitive advantage regardless of technological changes.
Conclusion: Toward More Conscious Software Creation
Software development is fundamentally a cognitive activity requiring sustained mental effort and clear thinking. Understanding the mechanisms of attention, fatigue, and decision-making empowers developers to work more effectively. By applying principles from behavioral psychology to daily practices, teams can reduce unnecessary cognitive costs and preserve capacity for the most valuable aspects of their work.
The combination of thoughtful process design, appropriate tool usage, and individual self-management creates conditions where developers can consistently produce high-quality work while maintaining their well-being. In an industry characterized by rapid change and high demands, these skills become essential for long-term success and satisfaction.
Conscious management of mental energy transforms software development from a reactive, exhausting process into a sustainable, engaging craft. The investment in understanding and optimizing cognitive performance yields returns in code quality, innovation, and professional fulfillment.
Links:
[AWSReInvent2025] Scaling Customer Support, Compliance, and Productivity with Conversational AI at Coinbase
Lecturer
Joshua Smith is a Senior Solutions Architect at Amazon Web Services (AWS), specializing in financial services. He collaborates closely with major institutions to design scalable, secure cloud architectures.
Vara Maharivan serves as Director of Machine Learning and Artificial Intelligence at Coinbase, leading the company’s efforts to integrate advanced AI and machine learning capabilities across its cryptocurrency platform.
Abstract
This session examines how Coinbase, a leading cryptocurrency exchange, has deployed a unified generative AI platform built on Amazon Bedrock to transform three critical operational domains: customer support, regulatory compliance, and internal developer productivity. The presentation details the architectural approach, key AWS services leveraged, real-world performance metrics, and the strategic roadmap ahead. By combining retrieval-augmented generation (RAG), tool execution, and domain-specific agents, Coinbase has achieved substantial automation, cost efficiencies, and enhanced user experiences while maintaining rigorous security and compliance standards.
The Evolution of Generative AI in Financial Services
Joshua Smith opened the discussion by contextualizing the rapid maturation of generative AI within financial services. In 2023, early adoption centered on foundational concerns such as data trust and secure retrieval mechanisms. By 2024, the introduction of Amazon Bedrock enabled broader experimentation in areas like customer support, with focus shifting toward scalability, granular access controls, and integration with existing enterprise tools. Entering 2025, the landscape has progressed toward fully agentic, multi-agent systems capable of autonomously orchestrating complex workflows.
Smith emphasized that the primary challenge is no longer prototyping conversational interfaces but rather re-engineering entire business processes to deliver measurable impact on key performance indicators. This shift demands robust infrastructure, advanced security primitives, and operational frameworks tailored for agentic workloads.
AWS Services Enabling Production-Grade Agentic AI
Central to the discussion was Amazon Bedrock, a fully managed service providing access to leading foundation models through a unified API. Bedrock supports private model customization, guardrails for safety, cost-latency optimization, and, notably, Agent Core—a suite of capabilities designed to operationalize agents at scale.
Agent Core addresses critical production gaps: a serverless runtime supporting long-running multimodal agents (up to eight hours), checkpointing and recovery, identity management compatible with existing providers, secure token vaults, shared and private memory, tool discovery with fine-grained controls, and centralized observability combining logs, traces, and metrics. These components collectively mitigate risks highlighted in industry reports, such as escalating costs, unclear value, and insufficient security, which threaten the viability of agentic initiatives.
Coinbase’s Strategic Vision for AI Integration
Vara Maharivan outlined Coinbase’s mission to increase economic freedom through a trusted global cryptocurrency platform. The company rests on three pillars: building trust via top-tier security, enhancing accessibility through intuitive experiences, and scaling operations efficiently across more than 100 countries.
AI and machine learning have long underpinned fraud detection, risk assessment, personalization, and infrastructure scaling at Coinbase. Recent innovations include graph neural network-based risk scoring for blockchain addresses, ERC-20 scam token detection combining smart contract auditing with ML, and predictive scaling models to handle market volatility.
With the advent of large language models, Coinbase identified three high-impact generative AI domains: customer support automation, compliance process acceleration, and developer productivity enhancement.
Transforming Customer Support with Agentic Workflows
Crypto markets exhibit extreme volatility, driving unpredictable spikes in user inquiries that challenge traditional human-staffed support models. Coinbase addressed this through a unified generative AI platform granting fluid access to models and internal data via standardized interfaces.
The architecture features a virtual assistant handling routine interactions autonomously and an agent-assist tool empowering human representatives. The virtual assistant resolves straightforward cases end-to-end, while the assistive tool synthesizes real-time information from knowledge bases and tools, providing agents with contextual summaries, suggested responses, and multilingual capabilities.
Results demonstrate significant impact: approximately 65% of customer contacts are now automated, yielding nearly five million annualized employee-hour savings. Automated cases resolve in under ten minutes—contrasting sharply with up to forty minutes for human-handled escalations—dramatically improving customer satisfaction and operational efficiency.
Streamlining Compliance through AI-Augmented Investigations
Regulatory compliance in financial services demands rigorous processes such as KYC, KYB, and transaction monitoring. These workflows are labor-intensive, require exhaustive explainability, and must adapt to diverse jurisdictional requirements.
Coinbase augmented traditional ML-based risk detection models (deployed via Anyscale on AWS EKS) with generative AI. A compliance-assist tool aggregates data from internal systems and open-source intelligence, producing narrative summaries and risk signals for human reviewers.
At the core lies an autoresolution engine orchestrating holistic reviews. Upon a high-risk alert, the engine coordinates data synthesis, automated actions, human-in-the-loop feedback, and customer information requests. Final decisions—such as filing Suspicious Activity Reports—remain with human compliance officers, preserving accountability while accelerating throughput and consistency.
Boosting Developer Productivity across the SDLC
Developer efficiency emerged as another strategic priority. Coinbase provides multiple best-in-class coding assistants (e.g., Claude Code, Cursor) powered by Anthropic models via Bedrock, allowing engineers to select preferred tools.
A custom GitHub Action automates pull-request reviews: summarizing changes, generating natural-language comments, enforcing conventions, identifying testing gaps, and offering debugging guidance for CI failures. This shifts human review toward higher-value architectural concerns.
For quality assurance, an in-house UI testing tool translates natural-language test descriptions into autonomous browser actions across form factors, achieving parity with human accuracy, triple the bug-detection rate, and 86% cost reduction versus manual testing.
Quantifiable outcomes include nearly 40% of daily code being AI-generated or influenced (targeting 50%), 75,000 annual hours saved via automated PR reviews, and dramatically faster test introduction.
Future Directions and Platform Modernization
Coinbase aims to democratize agentic AI across the organization, enabling every employee to experiment and innovate. Ongoing efforts focus on modernizing existing tools and scaling enterprise-wide impact.
Agent Core features—secure deployment, robust identity management, advanced memory, and interoperability—are viewed as pivotal for the next phase of expansion.
Conclusion
The Coinbase case illustrates a mature approach to generative AI deployment: leveraging a unified platform on Amazon Bedrock to address volatility-driven operational challenges while upholding security and regulatory standards. By combining autonomous agents, human augmentation, and rigorous evaluation, the company has realized substantial automation, cost savings, and quality improvements across support, compliance, and engineering functions. As agentic systems evolve, such integrated architectures offer a blueprint for financial institutions seeking transformative efficiency without compromising trust.
Links:
[DevoxxUK2025] Platform Engineering: Shaping the Future of Software Delivery
Paula Kennedy, co-founder and COO of Cintaso, delivered a compelling lightning talk at DevoxxUK2025, tracing the evolution of platform engineering and its impact on software delivery. Drawing from over a decade of experience, Paula explored how platforms have shifted from siloed operations to force multipliers for developer productivity. Referencing the journey from DevOps to PaaS to Kubernetes, she highlighted current trends like inner sourcing and offered practical strategies for assessing platform maturity. Her narrative, infused with lessons from the past and present, underscored the importance of a user-centered approach to avoid the pitfalls of hype and ensure platforms drive innovation.
The Evolution of Platforms
Paula began by framing platforms as foundations that elevate development, drawing on Gregor Hohpe’s analogy of a Volkswagen chassis enabling diverse car models. She recounted her career, starting in 2002 at Acturus, a SaaS provider with rigid silos between developers and operations. The DevOps movement, sparked in 2009, sought to bridge these divides, but its “you build it, you run it” mantra often overwhelmed teams. The rise of Platform-as-a-Service (PaaS), exemplified by Cloud Foundry, simplified infrastructure management, allowing developers to focus on code. However, Paula noted, the complexity of Kubernetes led organizations to build custom internal platforms, sometimes losing sight of the original value proposition.
Current Trends and Challenges
Today, platform engineering is at a crossroads, with Gartner predicting that by 2026, 80% of large organizations will have dedicated teams. Paula highlighted principles like self-service APIs, internal developer portals (e.g., Backstage), and golden paths that guide developers to best practices. She emphasized treating platforms as products, applying product management practices to align with user needs. However, the 2024 DORA report reveals challenges: while platforms boost organizational performance, they often fail to improve software reliability or delivery throughput. Paula attributed this to automation complacency and “platform complacency,” where trust in internal platforms leads to reduced scrutiny, urging teams to prioritize observability and guardrails.
Links:
[DevoxxUK2024] Productivity is Messing Around and Having Fun by Trisha Gee & Holly Cummins
In their DevoxxUK2024 talk, Trisha Gee (Gradle) and Holly Cummins (Red Hat, Quarkus) explore developer productivity through the lens of joy and play, challenging conventional metrics like lines of code. They argue that developer satisfaction drives business success, drawing on Fred Brooks’ The Mythical Man-Month to highlight why programmers enjoy crafting, solving puzzles, and learning. However, they note that developers spend only ~32% of their time coding, with the rest consumed by toil (e.g., waiting for builds, context-switching).
The speakers critique metrics like lines of code, citing examples where incentivizing code volume led to bloated, unmaintainable codebases (e.g., ASCII art comments). They warn against AI tools like Copilot generating verbose, unnecessary code (e.g., redundant getters/setters in Quarkus), which increases technical debt. Instead, they advocate for frameworks like Quarkus that reduce boilerplate through build-time bytecode inspection, enabling concise, expressive code.
Trisha and Holly introduce the SPACE framework (Satisfaction, Performance, Activity, Communication, Efficiency) as a holistic approach to measuring productivity, emphasizing developer well-being and flow over raw output. They highlight the importance of mental space for creativity, citing the brain’s default mode network, activated during low-stimulation activities like showering, running, or knitting. They encourage embracing “boredom” and play, supported by research showing happier developers are more productive. The talk critiques flawed metrics (e.g., McKinsey’s) and warns against management misconceptions, like assuming developers are replaceable by AI.