The Future of Engineering with James Stanier

The podcast explores evolving trends in software engineering, emphasizing the diminishing value of artisanal code in favor of functional, utility-driven code, unless tailored to niche markets. It questions whether the upper limits of engineering productivity are known and stresses the importance of advancing existing engineers before scaling teams. Looking ahead, the future of engineering roles in 2035 may involve shifts influenced by AI, automation, and industry demands, with senior roles potentially evolving beyond traditional expectations. The discussion also addresses the emotional and practical challenges of adapting to these changes, drawing parallels to historical tech transitions like the internet and smartphones. Engineering management is redefined, requiring adaptability, technical engagement, and leadership skills beyond pure technical expertise, with hybrid roles blending management and technical contributions becoming more critical in an AI-driven era.

The podcast highlights AIs current limitations in contextual understanding, such as interpreting Slack threads or tribal knowledge, and its struggles to replicate human-engineer mental models. Remote work in 2026 remains a mixed model, with companies balancing flexibility against the enduring value of in-person collaboration, though remote preferences persist for some due to lifestyle and financial factors. Tools like context engines (e.g., Unblocked) are gaining traction to improve workflows, while evolving programming abstractions may reduce reliance on low-level details like register allocation. The job market is redefining senior roles, with new positions emerging around AI orchestration and system architecture, as traditional craftsmanship yields to automation. Emotional responses to technological shifts are split: some embrace efficiency gains, while others fear displacement from manual coding. The discussion underscores themes of adaptation, the balance between foundational management principles and evolving industry pressures, and the potential for AI to enhance productivity and creativity, albeit with limitations in measurement and contextual awareness.

• What if you adopted a context engine like Unblocked to streamline your engineering workflow?

  • Move: Integrate Unblocked or similar tools into your daily workflow to capture context, automate documentation, and reduce token usage in code reviews.
  • Why Now?: AI tools are already improving productivity, but their value depends on context-aware integration. Solving this bottleneck could drastically reduce cognitive load.
  • Expected Upside: Faster development cycles, improved code quality, and the ability to scale solo projects with minimal overhead.

• What if you redefined your role as an AI orchestrator rather than a traditional developer?

  • Move: Focus on directing AI agents (e.g., Cursor, Claude) to automate repetitive tasks, optimize code, and manage pipelines.
  • Why Now?: The industry is splitting into AI orchestrators and system architects. Solo operators can specialize in mastering AI workflows to outpace teams.
  • Expected Upside: Increased efficiency in delivering complex projects by leveraging AI for routine work, freeing time for strategic ideation.

• What if you shifted focus from writing code to enabling ideas through higher-level abstractions?

  • Move: Invest in tools and frameworks that automate low-level coding (e.g., natural language interfaces, AI-driven code generation) while prioritizing concept validation.
  • Why Now?: The value of code is increasingly tied to what it enables, not the syntax itself. Automation reduces the need for artisanal mastery of niche languages.
  • Expected Upside: Build faster prototypes, align more closely with product vision, and reduce time spent on debugging or refactoring.

• Leverage AI Tools for Efficiency: Integrate AI-driven context engines (e.g., Unblocked) into workflows to improve code quality, reduce review cycles, and automate repetitive tasks like document creation or test automation, freeing time for higher-value work.
• Prioritize Functional Impact Over Craft: Focus on building features that deliver clear value to users rather than optimizing for "clean code" aesthetics, as the functional utility of code now outweighs the artisanal value in most contexts.
• Adopt Asynchronous Workflows: Use cloud tools (e.g., Notion, G Suite) to streamline collaboration and documentation, enabling rapid ideation-to-execution cycles and reducing reliance on synchronous meetings or office-based workflows.
• Experiment with AI for Code Abstraction: Invest in tools that translate high-level ideas into executable code (e.g., natural language interfaces) to reduce manual coding, allowing you to build prototypes faster and focus on system architecture rather than syntax.
• Re-evaluate Team Structure with AI: Test the feasibility of operating with a smaller team (or even solo) by leveraging AI to handle tasks like onboarding, documentation, or code reviews, and avoid scaling headcount unless necessary for product growth.