Skip to content

Project Rules #1

@stepan-omelka

Description

@stepan-omelka

Block

  • Each block represents one week, and I dedicate 8 hours a day to it.
  • Each block has a specific goal.
  • On Friday, there is a goal review — if the goal is not successfully defended, it gets postponed by a week.
  • At the start, 3 blocks are created.

Goal

= Angular or frontend web-dev concept that should be explored. It describes what should be explored/practised. Describing how it should be done is optional - by default it is considered part of the task.

  • It is described by the tutor into issue/issues under milestone block xx
  • The goal is realistically achievable within one week.
  • The goal is well described.

The implementation

  • The implementation of the goal is as isolated from other things as possible (e.g., I don’t need to focus much on writing CSS for a goal that doesn’t involve writing CSS).
  • Critical parts of the code are well-commented.
  • The project doesn't have to make sense as a whole, it is really just practise.
  • At the end of the block it should be clear that the one who implemented the goal understands the concepts and can use them on real projects, thus it should be implemented, and implemented correctly in suitable scenario

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions