The article warns that while coding agents accelerate development, they erase accumulated experience, causing repeated mistakes across team members—especially in large teams—so rejecting database agentization means refusing to turn knowledge into a lasting asset.
The author argues that a technical manager should devote about 80% of their time to coding and only 20% to management, warning that abandoning hands‑on development erodes technical judgment, team trust, and long‑term career competitiveness.
Boris Cherny outlines 13 concrete engineering practices—spanning standardization, automated verification, workflow acceleration, and feedback loops—that transform Claude Code from a clever code generator into a reliable, cost‑effective productivity tool for software teams, complete with real‑world metrics and step‑by‑step guidance.
Although AI can generate code at lightning speed, many software teams see little improvement in delivery time because the bottlenecks shift to testing, review, approvals, and deployment, requiring a holistic process overhaul rather than just faster coding.
The article explains that truly great technical leaders appear less busy because they focus on anticipating future failure points and controlling system complexity, rather than merely reacting to immediate issues, which leads to more stable systems, smoother teams, and faster project delivery.
The article analyses the rise of Vibe Coding, its hidden entropy costs for teams, and proposes Spec‑Driven Development (SDD) as a deterministic, context‑engineered alternative, detailing its philosophy, lifecycle, tooling ecosystem, practical adoption steps, and metrics for measuring engineering productivity.
A team used Codex‑style AI coding tools to build a customer‑service agent system, launched it quickly, but the AI‑generated code created tangled architecture, performance bottlenecks, and maintenance chaos, highlighting the need for human oversight and solid engineering practices.
The article examines a curated list of 25 AI‑driven Skills, showing how they can be transformed from simple prompt templates into repeatable, governed workflow assets that boost team productivity, preserve institutional knowledge, and enable scalable process automation across learning, documentation, and decision‑making tasks.
The article analyzes how Xiaomi’s AI coding initiative boosted individual developer speed but exposed organizational bottlenecks, and describes a three‑layer engineering solution—Unified Workflow (VAF), Code Knowledge Index (VKF), and Collaborative Workbench (eight‑claw)—that lowers entry barriers, builds searchable code knowledge, enables parallel task execution, and preserves team‑wide knowledge for sustainable productivity gains.
The article argues that in 2026 code has become a cheap commodity and the true value of technology teams lies in amplifying individual, non‑technical, and organizational capabilities through AI agents, platform engineering, and observability, outlining concrete examples, architecture layers, and a three‑stage adoption path.
The article examines how, by 2026, AI‑assisted developers using tools such as Claude Code, Cursor, and the Anthropic MCP protocol can enable a ten‑person team to match or exceed the output of a hundred‑person traditional department, detailing role reallocation, AI‑driven toolchains, a step‑by‑step migration roadmap, and associated risks.
The article argues that AI‑generated code speeds up output but exposes teams to engineering limits, causing cognitive debt, inconsistent quality, and hidden risks, and offers concrete guidelines for backend teams to harness AI safely while preserving long‑term system reliability.
The article examines design patterns as a mid‑level code standard, explores why they often feel out of place in everyday business development, analyzes performance, class‑explosion, team skill, project environment, agile timing, and turnover issues, and offers concrete steps to maintain sustainable code quality.
After burning our Agile rulebook and abandoning story points, sprints, and endless meetings, a senior engineering team switched to a simple Kanban flow with WIP limits, focused on cycle time, and replaced daily stand‑ups with continuous Slack communication, resulting in dramatically higher output, quality, and morale.
This article explains what technical debt is, why it is a business problem, how to measure its cost using unplanned work, provides formulas and examples for calculating wasted capacity, and outlines practical steps to prioritize code quality, architecture alignment, and process improvements for higher team productivity.
The article outlines seven common behaviors—such as massive one‑off commits, messy code, multitasking without planning, arrogance, ignoring feedback, handling personal matters at work, and chasing every new tech trend—that reveal a developer’s lack of experience, and offers concrete actions to overcome each pitfall.
The article explores why many developers get stuck at the competent level, argues that digging into the true business need is essential, and presents Elon Musk’s five‑step lean workflow—question, delete, simplify, accelerate, automate—to help teams work smarter and deliver real value.
A joint study by researchers from Brazil and Canada analyzed 56 GitHub projects, mapping issues and pull requests as graph nodes to uncover eight distinct workflow patterns—including competitive PRs and duplicate issues—offering actionable insights for improving team collaboration and code review practices.
Bad managers are created when seniority replaces merit, they fill their days with unnecessary meetings and micromanage tasks that add no value, but they can be avoided by converting expertise into results, designing efficient processes, delegating responsibly, evaluating performance fairly, and fostering a culture that rewards genuine contribution over tenure.
NetEase Cloud Music’s mid‑platform frontend team tackled fragmented product lines and low throughput by standardizing metadata, revamping cross‑team workflows, introducing bi‑weekly reviews, adopting a hybrid micro‑frontend architecture, and building reusable low‑code components and backend code‑generation tools, which doubled demand throughput while highlighting template benefits and remaining asset gaps.
This article examines how managerial habits such as unnecessary meetings, early‑stage over‑staffing, and fragmented work schedules waste valuable human capital, and it argues that respecting employees' time is essential for efficient project and team management.
The article analyzes how unnecessary meetings, early-stage overstaffing, and fragmented work schedules waste valuable human capital, explaining the underlying motivations, consequences for team productivity, and offering insights on more efficient project and time management practices.
The article advises teams to adopt OKR gradually with minimal friction, using simple, phase‑appropriate tools instead of heavyweight solutions, while steering clear of tool‑centric traps, bureaucratic formalism, and short‑termism, and focusing on transparent formulation, regular tracking, and reflective review to embed OKR habitually.
This article explains how applying the Four F principles—Fast, Function, Form, and Fabrication—helps engineering leaders choose the right technologies at the right time, boosting product performance, delivery speed, user experience, and overall business efficiency.
The article reflects on a team sharing session about design patterns, examining why they often aren’t applied in complex business scenarios, discussing performance, class explosion, team skill gaps, project constraints, and offering practical recommendations to balance code standards with real‑world development pressures.
This article examines how a software team transformed its daily stand‑ups by introducing physical Scrum and Lean Kanban boards, detailing the observed problems, step‑by‑step improvements, measurable outcomes, and future refinements to enhance transparency, focus, and value‑flow.
The article shares ten practical principles—owner mindset, time awareness, start with the end, closed‑loop thinking, respect for standards, avoiding repeated mistakes, design first, balancing output and capacity, asking good questions, and maintaining an empty‑cup mindset—to help engineers improve personal growth, team efficiency, and overall work quality.
This article shares ten practical principles—ranging from ownership and time management to continuous learning and balanced output—that help engineers avoid common pitfalls, improve team efficiency, and foster personal and professional growth.
The article explains how Silicon Valley software companies enhance their teams' engineering capability by defining the concept, distinguishing short‑term and sustainable approaches, and applying four practices—small batch, standardization, simplification, and automation—to achieve higher productivity and quality.
This article shares ten common behaviors that indicate a seasoned programmer may lack real skill, explains why these habits hurt teams, and offers practical advice on how to recognize and help such developers become more effective contributors.
This comprehensive guide explains why code reviews are essential, outlines their benefits and challenges, describes review formats, participants, focus areas, step‑by‑step processes, key operations, principles, and common pitfalls, providing practical advice and examples to help teams improve code quality and collaboration.
This article examines the concept of R&D efficiency, why many enterprises struggle to improve it, the common pitfalls such as siloed tools and metric obsession, and offers practical practices—from unified platforms to DevSecOps—to help slow its degradation and sustain productivity.
This comprehensive guide explains the importance of code reviews, outlines their benefits, addresses common challenges, and provides practical steps, formats, participants, focus areas, processes, principles, and code examples to help teams implement effective review practices.
This article introduces the first rule of the "101 R&D Management Rules" series, explaining how a disciplined two‑week iteration cycle builds rhythm, culture, and productivity in a large development team while aligning with OKR goals and leveraging the PingCode tool.
This article explores how to define and measure delivery value, development cost, and lead time for technical teams, highlighting common misconceptions, detailed metric breakdowns, and practical insights for turning raw numbers into meaningful performance improvements.
The article examines the causes and consequences of workplace involution and the 996 work model, shares personal experiences, and offers practical advice for engineers to build solid fundamentals and for managers to foster sustainable, non‑involuted teams while emphasizing cloud, open‑source, and thoughtful career choices.
This article explains what micromanagement is, why it harms both on‑site and remote teams by reducing trust, morale, and productivity, and offers practical strategies such as delegating responsibility, using project‑management tools, adopting RACI, and embracing asynchronous communication to break the habit.
This article introduces the “Monkey Theory” metaphor for task ownership, explains why un‑fed “monkeys” cause project delays, outlines five levels of monkey responsibility, and provides six practical principles for leaders to feed, supervise, and eliminate ineffective tasks.
This article explains how adopting a structured thinking framework—building a central goal, decomposing it, and applying methods like SWOT and AHP—helps professionals communicate value, prioritize work, and drive personal and team growth in fast‑moving development environments.
This article explores the Monkey Theory—a management framework that defines how tasks (the “monkeys”) should be assigned, fed, or eliminated—to help leaders prevent bottlenecks, empower employees, and boost project delivery through clear delegation, five task‑level classifications, and six practical feeding principles.
This article shares practical insights on the three typical misconceptions faced by technical R&D leaders, explains why they hinder team productivity, and offers concrete strategies—including balanced time allocation, effective delegation, and talent development—to transform personal expertise into high‑leverage leadership impact.
This article explains the OKR work method, its practical impact on a testing team, how to set effective Objectives and Key Results, and contrasts OKR with KPI to help organizations adopt goal‑oriented management practices.
This article shares an Alibaba technical expert’s data‑driven case study on improving a software development team’s efficiency and quality through agile practices, detailed metric analysis, targeted solutions, and continuous data operations, demonstrating how systematic measurement can reduce overtime and create a virtuous development cycle.
This article explains how a product‑focused, fast‑response team can efficiently select and use software for environment setup, project management, and technical knowledge accumulation, ensuring minimal distraction and streamlined development.
At SpringOne, Credera engineers Jason Goth, Micah Blalock, and Patricia Anderson explained how they leveraged Conway’s Law to redesign a client’s technical architecture and processes, overcoming productivity decline by restructuring teams, applying the open/closed principle, and introducing new communication roles, ultimately accelerating high‑quality code delivery.
Drawing on interviews with over 500 engineers from top tech firms, this article outlines ten actionable practices—such as speeding iteration, embracing automation, fostering code ownership, and allocating 20% time—that together create a respectful, high‑performance engineering culture.
The Joel Test offers a fast, 12‑question checklist that lets you gauge a software team’s practices—from source control and build automation to testing and quiet workspaces—helping you spot critical weaknesses and improve overall productivity in just minutes.
