Skip to content

Minor point on problem description - main vs bonus features #842

@hnryjmes

Description

@hnryjmes

The retro for this weekend challenge focused primarily on how to write the UI for the bowling challenge, particularly writing the UI in jQuery, program flow between the UI and model layer, writing jQuery UI code in render methods like you would write React UI code, etc.

Reading the problem description (and the review.md document) it isn't clear that the UI is such an essential feature of this weekend challenge, as it is listed in the 'optional' or 'bonus' extras section. It is clear to me now that working on the UI would have been a more valuable thing to start with this weekend. Our coach (Mark) also suggested that he started with the UI first.

I'd suggest that none of the learning of the weekend challenge would suffer if the UI was listed among the main features rather than as an optional feature, as this seems to be how most people in the retro and our coach thought about it anyway.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions