My Needs
- Source control. This means copy, modify, merge. lock, modify, unlock is not good enough.
- ViewVC or equivalent functionality.
- Bug Tracking, an excel spreadsheet is not good enough here. Trac or Mantis or something more is needed.
- More detailed implementation specs to accomplany functional specifications.
- Use cases/user stories.
- To not write in TSQL, plSQL, or even SQL unless absolutely necessary.
- Mozilla/Gecko/FF as the primary target and IE as a secondary target.
- Continuous Integration.
- Communication via source repository logs
- Sensible naming standards. TBL_ prefix for tables doesn’t add anything. Plural table names ala Rails makes a little more sense.
- A good domain language for the problem at hand. Most of the time this comes from a good OO design.
- To focus on not inconveniencing others. Most programming is problem solving. Solutions that inconvenience others often just shift a problem. A solution should not shift problems.
- Practice YAGNI (You ain’t gonna need it) principals. There is always someone who says “If you abstract that just a little more, it is a great for all of these cases too.” Much of programming is supposed to only solve a specific case. If the general case were solved so easily, it would already be done. Of course this should be balanced with looking at what CAN be done, but YAGNI is a great guide here.
