Read the ". NET design Specification"

First, what impact on software quality? such as performance, reliability, security, dependency management and so on.

Second, customer-first programming-if you have to describe the functions provided by your library, and let a developer without looking at the library of the premise,

Based on what he thinks the library should look like to write a program, does the developer ultimately write a program that is close to what you provide? On a

Group developers do this test, if most of the written programs are close, but not the same as the libraries you provide, then they are right, you

Wrong, the library should be modified accordingly. "From the user's point of view, first write out the customer code, and then the library implemented accordingly."

There must be a balance between simplicity and the inherent complexity of the provided functionality. 】

Iii. The general specification for building a single framework for a broad range of developers is that the API is divided into low-level and high-tier types, exposing rich APIs to low-layer types and providing strong

High-level types are packaged with a convenient API for low-layer APIs.

Read the ". NET design Specification"