This article explains how Codex differs from typical AI chat by acting as an autonomous coding agent that can read files, modify code, run commands, and execute tests within a repository, detailing which developers benefit most and the practical limits of its capabilities.
A developer shares practical workflow for using OpenAI's Codex CLI, emphasizing starting with small well-defined tasks, keeping human in the loop, reviewing diffs, and automating repetitive work after stabilizing interactive flows.
By 2026, AI coding assistants will shift from toys to production tools, and this guide outlines an engineered workflow—starting with detailed specifications, breaking tasks into small steps, providing rich context, selecting appropriate models, integrating automation and testing, and maintaining human oversight—to treat LLMs as trustworthy pair programmers.
This article systematically explores how AI‑augmented pair programming can be applied across the entire software development process, using the PDCA (Plan‑Do‑Check‑Act) loop, and provides practical guidance on prompt engineering, context engineering, and three typical scenarios—production delivery, rapid validation, and experimental exploration—while sharing personal insights and future outlooks.
This article explains the concept of pair programming, outlines its benefits such as higher code quality and knowledge sharing, examines challenges like increased cost and personality clashes, and discusses its practical applications and alignment with agile development practices.
Recent research and industry observations reveal that developers allocate roughly 58% of their work time to comprehending existing codebases and system architecture, a trend unchanged over four decades, highlighting the critical need for better program‑understanding strategies and collaborative practices.
A senior Alibaba engineer reflects on a decade of experience, highlighting the power of teamwork, the importance of pausing to think, and the role of learning methods, pair programming, and critical thinking in becoming a better software professional.
This article shares personal insights from a decade at Alibaba, highlighting how teamwork, pair programming, reflective thinking, and disciplined learning methods can transform engineers' productivity and career development.
This article explores how developers can improve their coding by mastering collaboration skills such as pair programming and code reviews, cultivating patience and humility, and adopting solid fundamentals like reading code, design patterns, test‑driven development, and disciplined refactoring to produce cleaner, more maintainable software.
The article uses the hammer metaphor to critique treating agile methods as a one‑size‑fits‑all tool, illustrating common misunderstandings through dialogues about user stories, estimation, TDD, pair programming, Kanban, Scrum, SAFe, and continuous delivery, and urging thoughtful adoption.
This article outlines twelve practical techniques—including TDD, ATDD, CI, pair programming, code reviews, static analysis, coding standards, automation, refactoring, early demos, user testing, and team cohesion—that collectively raise software quality while reducing bugs and development costs.
The article argues that software architects must stay hands‑on—coding, pairing, reviewing, and rotating with delivery teams—to gather timely feedback, exercise effective technical leadership, and avoid the isolated "ivory tower" that hampers agile, high‑quality system development.
This article examines the common obstacles that prevent teams from adopting pair programming, outlines the substantial benefits such as higher code quality and team cohesion, and provides practical strategies and step‑by‑step methods for introducing pair programming in both co‑located and distributed software development teams.
