On Mar 6, 11:54 am, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Sun, Mar 6, 2011 at 2:41 PM, Vivek Narayanan <m...@vivekn.co.cc> wrote: > > @Sebastien: I got your point about using a dict as an intermediate > > structure and the use of recursion, and I looked at your > > implementation which is somewhat similar to what I have in mind. > > > Well, here is a list of deliverables for the project: > > > • Investigate existing structure of the serializer, make changes, > > refactor to suit needs. (1 week) > > > • Implement metadata methods, change the ``fields`` argument of > > serialize(), write unit tests. (2 weeks) > > > • Implement structures and templates parsing for custom serialization, > > configurations for XML/JSON/YAML etc. Also, write tests for this. (2 > > weeks) > > > • Handling of nested and related models. (1 week) > > > • Investigate the changes to be made at deserialization side and > > implement them. (1 week) > > > • More tests and write documentation. (2 weeks) > > > This is a conservative estimate and am keeping 3 weeks as a cushion. > > Here's some advice: If this is what your final plan looks like, I > would expect that your proposal would be rejected. Here's why: > > * We prefer projects to have a clear design in mind before > implementation begins. It's ok if refinements happen along the way, > but "investigation" periods (and you have 2 of them) are not something > that should be required. You investigate while you develop your > proposal. > > * Testing isn't an activity that can be clearly separated. It's an > integral part of code development. Having a "more tests" activity > indicates you either haven't allocated enough time for testing during > development, or you're trying to pad your timeline. > > * Padding with a 3 week cushion gives the impression that you haven't > thought about the effort required. 3 weeks of full time development is > a long time. > > * I'm sceptical of any plan that consists of "2 week" estimates. > Again -- a week is a long time. If you can't clearly express what will > be developed, tested and delivered in a week long timeframe, then I > don't think you've thought about the problem hard enough -- at least, > not hard enough for us to recommend that Google give you $4k, and > someone from the project spend many hours mentoring you. > > Yours, > Russ Magee %-)
Thank you very much for your feedback, I must admit that I've not been very clear and gave an impression different from what I really meant. I already have much of the structure in mind and I would be just looking at a few minor details, that is what I meant by investigation and those periods I mentioned earlier won't be entirely dedicated to investigation. I would be testing along with development, I had just meant the tests that might have been overlooked and some final bug fixing. Here is a revised schedule: 1. Write the basic skeletal structure of the serializer. (1 week) 2. Modify/Refactor the structure of the deserializer. (1 week) 3. Implement support for the metadata methods. (1 week) 4. Modify the ``fields`` argument in the call to ``serialize()``. (2 days) 5. Implement support for the unicode conversion methods. (3 days) 6. Add the ``exclude`` and ``extras`` arguments in ``serialize()``. (1 week) 7. Add support for string templates, output formats and structure. (1 week) 8. Handling of nested and related models. (1 week) 9. Write documentation and provide many examples. (2 weeks) 10. Some final housekeeping. (1 week) Sincerely, Vivek Narayanan -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
