-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
368d892
commit 7a24b51
Showing
1 changed file
with
15 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# How Tos | ||
|
||
These are some How Tos for the project. I want to follow them for this project | ||
1. Write tests as much as possible. This is because I want the software to be robust | ||
2. Reuse existing code / libraries / software whenever possible to speed up development, | ||
and to stand on the shoulders of other giants as a lot of time and effort has been put to | ||
make them, which doesn't have to be necessarily reinvented | ||
3. Since we are already planning to write tests, do test driven development (TDD) whenever | ||
possible | ||
4. For any bug reported, write a failing test first for the bug, then fix the bug to pass the test | ||
5. Keep the software as simple as possible - not much complexity in terms of code written, | ||
design and architecture. To do this, write as little code as possible. Unnecessary code leads to | ||
complexity and maintenance. No code means no maintenance and no complexity :P | ||
6. Users are the core of the software. The software should be easy to use. If user can't use it | ||
or understand how to use it, see behvaiour and try to change the software accordingly! |