What a developer should know
After
reading Joel, and writing my response to that, I started to think about all the
things that a typical developer should know in order to produce a working
application. The list isn't in any particular order, and I'm focusing it the
business / application developer:
- Data
Structures
- Complexity
- Cost of
operations (local vs. remote)
- Designing
usable classes*
- SQL
- XML
- ACID
- Basic
Design Patterns:
- Strategy
- Decorator
- Regular
Expressions
- Data
Modeling
- KISS
- TDD
- Building
DAL
- Change
Management (SCCS)
Anything
to add that you think is essential?
*
Reusable classes are another
matter all together
Comments
Requirements Discussion
GoogleBot
YahooBot
MSNBot
GoogleBot1
YahooBot1
MSNBot1
YahooBot2
GoogleBot4
YahooBot4
MSNBot4
Comment preview