Less work? Hardly!
Why so few new features?
Some of the CAP2.0 "must have" features are trivial. Some are not, but altogether they should not take the whole 4 weeks remaining. In a module that you routinely get more work than you want to do, why did we suddenly give you less work? Because we want you to...
- Spend more time improving the existing code/documents. Writing more bad code will not help anyone.
- Spend more time experimenting. Try different designs. Try different optimization strategies. Try different tools.
- Spend more time reflecting on the project experience. This is more important than writing more code. Catch up with the reading list. Are all those tips given in the reading list applicable to your project? Which are not applicable and why? Think about these and bring those up for discussion in the forum or during consultations.
- Spend more time testing. You still haven't caught all the bugs in CAP.
About CPS API
Don't forget to critically evaluate and improve the CPS API. Writing good API's is one important things we want you to learn. Compare the current API against the tips given
here.
About bugs in CAP
Fix the bugs before you add new features (always!). Don't forget to maintain the Issue Tracker.
0 comments:
Post a Comment