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.
The article critiques common careless attitudes toward code reviews, exposing how pointless debates, condescending comments, exhaustive checklists, and rigid pass‑fail policies hinder collaboration, and offers practical, fact‑based strategies—including constructive questioning and pair verification—to transform reviews into productive, bug‑reducing discussions.
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.
