How to Systematically Build and Manage Technical Products for Developers

Introduction

The author reflects on years of experience building internal and open‑source technical products, noting the challenges of serving developers and managing large‑scale collaborations.

Design Product

Product design starts with answering "what to build" by conducting market and user research, defining product positioning, and creating deliverables such as market research reports, user research reports, interaction mockups, component inventories, and documentation outlines.

Market research report (e.g., "AI Auto‑Coding Research Report")

User research report (e.g., "Taobao Front‑End Outsourcing Survey")

Product interaction mockup (e.g., Iceworks workbench)

Website mockup (e.g., ICE website)

Documentation outline (e.g., ICE tutorial)

Design Architecture

After defining the product, the next step is "how to build" it, which involves creating structural and behavioral UML diagrams. The author recommends a two‑step process: competitive analysis followed by architecture diagramming.

Structural diagrams: class, component, deployment

Behavioral diagrams: use‑case, activity, sequence, state machine

Example sequence diagram for a VS Code plugin is shown.

Manage Project

Project execution focuses on organizing development and collaboration. Key topics include repository layout (monorepo vs multi‑repo), branch management strategies, and Gitflow workflow.

type[optional scope]: subject
[optional body]
[optional footer(s)]

Common commit types:

feat: new feature

fix: bug fix

docs: documentation changes

style: formatting only

test: add/modify tests

refactor: code refactor

chore: maintenance

revert: revert changes

Install commit lint tools:

$ npm i --save-dev @iceworks/spec @commitlint/cli husky

Create .commitlintrc.js:

const { getCommitlintConfig } = require('@iceworks/spec');
module.exports = getCommitlintConfig('react');

Add Git hooks in package.json:

{
  "husky": {
    "hooks": {
      "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
    }
  }
}

Collaboration Mechanisms

Establish RFC processes, PR guidelines, and code‑review (CR) best practices to improve quality and efficiency. The author lists typical CR checklist items such as review standards, reviewer selection, review scope, navigation, response time, comment writing, and handling feedback.

Async vs Real‑time

Most open‑source projects use asynchronous collaboration, but real‑time updates (e.g., chat bots syncing project status) can improve visibility.

Write Documentation

Documentation is crucial for user experience. The author compares three documentation pipelines (Yuq, self‑hosted site, Git repo) and recommends the fourth approach for large or open‑source projects.

Develop Website

Select a static‑site generator (Docusaurus, VuePress, Docsify, etc.) based on theme support, custom pages, multi‑language, static export, onboarding difficulty, and customization stack.

Operate Product

Product operation requires a balanced mindset: genuine value for developers, appropriate promotion, and avoiding spammy tactics. The author lists acceptable and questionable promotional behaviors.

Manage Requirements and Permissions

After launch, handle user issues via GitHub Issues with templates and labels, use discussion platforms or chat groups for community support, and leverage internal tools (Aone, R&D Honey) for tracking requirements and defects.

Conclusion

Building a technical product is like shaping a wooden craft: the basic form is easy, but polishing the details requires patience and continuous iteration.