Scalable System Design

Access rights for different roles

- one header file for each role v.s. one header file (with lots of if/else) for all roles
- assign ID to each page, assign ID list to each role

Slicing system to layers

- DB access, business logic, HTML, CSS
- uniqueness
- reusability
- accumulation of code/solution

System analysis

- Client requirements analysis
- technical requirements analysis
- risk points, risk control
- configuration, separate control points from code
- data dictionary, allow user to adjust this themselves

Communicating to clients

- guide/educate clients

Team building

- source control
- no new assignment before end of current assignment period even if current assignment is done before schedule
- grow together
- mutual tech evaluation/no boss participation