.jpeg)
Information management bible.
Program to Product
Needs two parts
- Interface System Integration(System Design).
- Testing, Documents, Maintenance (OPS).
Human/Month
Evaluate for cost, not for output.
Scheduling a software task
1/3 planning （top-down)
1/6 coding
1/4 component/ early system testing
1/4 Integration testing (TDD)
Build a team
- Pick the right and important person.
- Focus on communication, so people can’t be too many.
10 man programming team
- Surgeon: chief programmer
- Copilot: alter ego of surgeon
- Programming clerk: Maintain all technical records
- Toolsmith: constructing, maintaining, upgrading tools.
- Tester: test any suitable test cases
- Language lawyer: know how to use language do tricky things
- Administrator: handle money, people, space, machines
- 1 Secretary: handle project corresponding, non- product files
- Editor: generating documents
- 1 Secretary: same as 6.1
- Software engineer: front-end, backend, full stack
- Site Reliability engineer: infrastructure administration deployment, deploy system (more on-call)
- Solutions engineer: cloud
- Tools and infrastructure engineer: tools
- Machine learning engineer
- UX engineer
- Engineering manager: at least I5
- Product manager
- Technical project manager
- UX writer
- UX researcher
Creative effort involved
- Architecture
- Implementation
- Realization
Large programming project
- Must have well programming organisation.
- The subjectivity of the system is greater than the creativity of the individual.
Needs
- A mission
- A producer
- A technical director or architect
- A schedule
- A division of labor
- An Interface definition amount the parts
Facts
- Second system usually over design.
- UX is important than UI.
- Document is important.
- Make the system design easy to change.
- Use modern tech.
- Millstone must be binary (Finished/Delay).
如果你覺得這篇文章很棒，請你不吝點讚 (ﾟ∀ﾟ)