The article explores how engineers and managers can use clear standards to assess performance, emphasizing design ability, reliable delivery, collaborative standards, and contributions to team efficiency as essential traits for professional growth beyond mere knowledge accumulation.
The article uses the behind‑the‑scenes process of Friends Season 6 to illustrate agile concepts such as backlog, user stories, MVP, Scrum meetings and continuous delivery, showing how a sitcom’s production can serve as a model for effective R&D management.
Engineers often overestimate their work while managers struggle to set objective evaluation standards; this article explores common self‑assessment biases, outlines four engineer career types, and proposes concrete criteria—design, delivery, standards, and team efficiency—to fairly assess technical contributions and foster growth.
Xianyu transformed its product publishing and editing functions by extracting platform code, introducing the SWAK framework, and decoupling services through RPC, resulting in clearer architecture, reduced code coupling, and significantly improved cross‑team development efficiency.
This article explains the purpose, prerequisites, organization, preparation, focus points, execution, and follow‑up of daily stand‑up meetings, emphasizing value‑flow, Kanban visualization, and practical checklists to help teams collaborate effectively and deliver value smoothly.
In the VUCA era, project managers operating in matrix environments must adopt clear responsibilities, emotional intelligence, and strategic questioning to turn awkward interactions with technical experts into productive collaboration, using influence, empathy, and professional insight across all project phases.
This article explores how engineers across development, testing, and product roles can improve team collaboration and overall effectiveness by adopting a three‑dimensional mindset—product thinking, technical thinking, and engineering thinking—while addressing common misunderstandings and systemic challenges.
The article shares a designer’s journey from UI creation to product ownership, emphasizing the need to observe real users, collaborate across teams, gather industry insights, and turn user pain points into valuable product features for SaaS customer‑service platforms.
The article explains how domain‑driven design helps software teams reach a shared understanding of the problem domain by cultivating requirements through visual collaboration, structured inception and iteration activities, and continuous feedback loops, ultimately improving architecture, reducing miscommunication, and delivering higher‑quality software.
This guide outlines the key features to consider when selecting a task management tool, compares seven popular solutions for developers, and highlights each tool's strengths, pricing, and missing functionalities to help teams pick the most suitable option for improved productivity.
This article shares a step‑by‑step case study of how a small team transformed the Goapi QA testing tool’s user experience by deeply understanding the product, aligning design rhythm with team workflow, fostering cross‑functional collaboration, and building a reusable component library.
The article lists 36 common bad habits that hinder programmers' productivity, grouping them into code organization, team work, coding practices, and testing/maintenance, and explains why each habit reduces efficiency and how to overcome them.
The article explores why engineers often overestimate their work, the challenges managers face in setting fair performance standards, and outlines essential abilities—design, delivery, standards, and collaboration—that distinguish truly effective engineers and drive team efficiency and career growth.
The article describes a Technical Research Group initiative within a tech center, offering several focused sub‑groups (frontend integration, distributed databases, Python engineering, AI, productization) led by experts, limited to eight members each, running Sep‑Dec 2018 with weekly training, demos, and final deliverables, requiring commitment and registration by Aug 30.
The article outlines five typical mistakes new agile testers make—waiting for the next build, not fully integrating with the team, clinging to a quality‑control mindset, relying solely on manual testing, and ignoring the big picture—and offers practical advice for each to foster effective, collaborative testing within agile development.
This article lists 36 common bad habits that reduce programmer efficiency—from poor code organization and teamwork to bad coding and testing practices—and offers concrete advice on how to overcome each to boost productivity and advance your career.
This article examines how DevOps emerged from the merging of development and operations roles, explores automation practices in small and large teams, outlines the three-step DevOps workflow, and discusses the cultural and organizational challenges of adopting DevOps at scale.
This article presents typical developer‑product manager interactions, highlights common wrong replies, and provides concise, professional answers that improve collaboration, reduce friction, and keep projects on track.
developer communicationproduct managementsoftware development
This article explains why developers should incorporate diagramming into their workflow, outlines three key uses—understanding problems, facilitating team communication, and merging ideas—reviews various media from pen‑and‑paper to code‑generated charts, and offers practical tips for creating clear, effective diagrams.
Alibaba’s entertainment advertising CRM team replaced a slow waterfall process with a cross‑functional One Team and bi‑weekly iterations, cutting development time from 12 to under 6 days, delivery to under 20 days, improving collaboration, feedback loops, and overall product quality.
This article explores the role of software architects, outlining their responsibilities, essential qualities, differences between internet and traditional enterprises, team dynamics, common optimization practices, and practical advice on growing into an architect and advancing your career.
This article likens the legendary warrior Zhao Yun to modern programmers, outlining three essential practices—self‑cultivation, skill development, and tool mastery—to achieve high‑efficiency coding, and offers concrete advice on design methods, testing, automation, and team collaboration for sustainable productivity.
Best Practicesefficient programmingteam collaboration
The article explains how developers can boost their productivity tenfold by focusing on three core questions—what to build, why it matters, and when to act—while emphasizing communication, prioritization, and a product‑mindset over sheer coding skill.
This article explains the benefits of code reviews—early bug detection, improved code quality, knowledge transfer, and stronger team trust—while offering practical tips on what to look for and how to conduct reviews efficiently.
The article outlines seven essential qualities—positive attitude, communication, time management, rapid learning, deep technical experience, teamwork, and user‑centric thinking—that distinguish top developers and offers practical ways to assess each trait during hiring and development.
career growthprogrammer qualitiessoftware development
This guide explains how to use the KJ (affinity diagram) method to unify diverse interpretations of interview data, quickly cluster user traits, and craft compelling persona stories that secure stakeholder buy‑in during early product development.
This article shares candid insights on why many programmers struggle with entrepreneurship, highlighting common misconceptions, overconfidence, lack of teamwork, and the need for an open mindset and practical experience to succeed in building a startup.
business mindsetprogrammer entrepreneurshipstartup advice
The article explains that AI engineers need solid architecture knowledge to turn high‑performing algorithms into real‑world solutions, covering four key reasons: algorithm vs. problem solving, on‑site deployment challenges, scalability, and effective team collaboration.
AI EngineeringMachine Learning Deploymentsoftware engineering
The article explains why many hiring posts that claim they only need one programmer are misguided, highlighting disrespect, underestimation of effort, misunderstanding of project scope, and premature recruitment, and offers practical advice for both employers and developers.
This article enumerates 35 common bad programming habits—ranging from code organization and team collaboration to testing and maintenance—and explains why they harm productivity, offering concrete advice on how to recognize and replace each habit with healthier practices.
This article explores how front‑end developers can break the cycle of endless revisions by adopting the right mindset, collaborating effectively with product and design teams, embracing component‑based thinking, and developing product‑centric skills that improve efficiency and quality throughout the development process.
After attending the Phoenix Project DevOps simulation in Beijing, I reflect on five key lessons—understanding role responsibilities, leveraging visual tools, focusing on value‑driven goals, applying one‑piece flow, and reducing hand‑offs—to improve operational efficiency and foster a DevOps mindset.
This article explains how well‑crafted design specifications improve multi‑designer collaboration, reduce development redundancy, and preserve brand identity across product iterations, while also highlighting common pitfalls and offering a step‑by‑step guide to building an effective design system for newcomers.
This article shares practical advice on improving personal productivity by optimizing your environment, mastering tools, managing time flow, adopting healthy habits, overcoming procrastination, refining processes, fostering teamwork, and using software like Asana to track work and reflect daily.
The article shares practical insights for engineers transitioning to management, emphasizing the shift from doing to delegating, prioritizing important over urgent tasks, establishing clear rules, fostering team communication, and mastering strategic thinking to drive both personal and team growth.
The article analyzes the root causes of Dev‑Ops conflicts, illustrates typical complaints at each release stage, and proposes concrete measures—shared goals, platform‑driven automation, and cultural alignment—to transform friction into collaborative efficiency.
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 shares twenty practical software development lessons—from starting with a minimal version and iterating, to effective debugging, teamwork, and continuous learning—offering actionable guidance that seasoned programmers have distilled over more than a decade of experience.
The article examines why software engineers are often seen as hard to communicate with, shares Nicholas C. Zakas' experiences and analogies, and offers practical advice such as involving engineers early, minimizing interruptions, granting creative space, and providing timely appreciation to foster better collaboration.
The article outlines Douban's R&D management philosophy, describing three core constraints—product contribution, proper methods, and technical goals—how they translate into rules, the democratic rule‑making process, cross‑team collaboration incentives, and a balanced performance and reward system.
This guide shares ten practical fault‑management techniques—ranging from proactive attitude and prioritizing incidents to continuous follow‑up and team collaboration—to help operations teams reduce damage, maintain service reliability, and keep users engaged during outages.
Front‑end engineers must blend logical planning, business‑savvy estimation, and design thinking by collaborating with back‑end developers, designers, and product managers to write reusable, maintainable code, anticipate changes, propose user‑focused solutions, and translate static mock‑ups into responsive interfaces that meet both technical and client expectations.
Exploring how various project management tools—from Rally and JIRA to Trello, physical whiteboards, and Confluence—can be selected and applied based on team size, structure, and geographic distribution, this guide helps teams boost efficiency while avoiding tool misuse.
This article outlines the product manager’s role as a communication hub across leaders, design, engineering, and operations, detailing each project phase, common challenges, and practical techniques—such as focusing on product goals and respecting professional expertise—to enhance collaboration and reduce rework.
Brainwriting, a written brainstorming technique, lets participants generate many ideas simultaneously, reduces anxiety, and often yields more concepts than face‑to‑face sessions, making it a powerful alternative for product teams and large groups.