Design-principles
Revision as of 22:52, 14 January 2019 by imported>Justin (Created page with "# Design ## Principles ### For Developers - Leverage their favorite tools. We want to integrate and place nice with others, not replace them. - Respect their computers. Use...")
Design
Principles
For Developers
- Leverage their favorite tools. We want to integrate and place nice with others, not replace them.
- Respect their computers. Use a reasonable amount of resources. Cleanup unused resources. Install and uninstall easily.
- Respect their privacy. No spyware, etc.
- Provide options for different preferences. Examples: what library version, what color, etc.
Maximize Effectiveness not Features
- The best software is not the one with the most features.
- Provide a designed experience.
- Avoid the turing tarpit.
- Avoid indecision. Make correct decisions. Do not reply on options as a crutch. Providing an option is to accommodate varying preferences, not differences in philosophy or design.
User Interface
Audience
- Professional programmers and new programmers.
- But, not the most opinionated, most intense power users. We want them comfortable, but don't expect to replace their favorite text editor.
- IDE not text editor.
Goals
- Make the interface look clean and clear.
- Make it easy for developers to find what they want.
- Clear the work area as much as possible. Focus on the code, not at all the extras.