Skip to content

AMashoshyna/algorithm_club

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

26 Commits
 
 
 
 
 
 
 
 

Repository files navigation

algorithm_club

Gitter

FAQ

What are we learning?

Course Review Schedule

for MOOC course material

How to read this?

Quodnon on the week 1 should be reviewed by number 4 that is dm3shafieiev

reviewer\Week number week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8 week 9
1 veligura 2 3 4 5 6 7 8 9 10
2 Oleksandr Siryi 3 4 5 6 7 8 9 10 11
3 Quodnon 4 5 6 7 8 9 10 11 12
4 dm3shafieieve 5 6 7 8 9 10 11 12 13
5 dumareckii 6 7 8 9 10 11 12 13 1
6 programulya 7 8 9 10 11 12 13 1 2
7 lysenko-sergei-developer 8 9 10 11 12 13 1 2 3
8 hedgehogus 9 10 11 12 13 1 2 3 4
9 ameks94 10 11 12 13 1 2 3 4 5
10 aleshaoleg 11 12 13 1 2 3 4 5 6
11 amashoshyna 12 13 1 2 3 4 5 6 7
12 Alimova 13 1 2 3 3 5 6 7 8
13 Оля Глазкова 1 2 3 4 5 6 7 8 9
14 robobee 3 4 5 6 7 8 9 10 11

Teamwork Schedule

for additional tasks

Teammate
1 veligura
2 Oleksandr Siryi /ephir
3 Quodnon
4 dm3shfieiev
5 dumareckii
6 programulya
7 lysenko-sergei-developer
8 hedgehogus
9 ameks94
10 aleshaoleg
11 amashoshyna
12 Alimova
13 OlhaHlazkova
14 robobee
week number pairs -- -- -- -- -- --
1 1-14 2-13 3-12 4-11 5-10 6-9 7-8
2 1-13 2-12 3-11 4-10 5-9 6-8 7-14
3 1-12 2-11 3-10 4-9 5-8 6-7 13-14
4 1-11 2-10 3-9 4-8 5-7 6-12 12-13
5 1-10 2-9 3-8 4-7 5-6 11-14 12-14
6 1-9 2-8 3-7 4-6 5-13 10-11 10-13
7 1-8 2-7 3-6 4-5 5-12 9-13 10-14
8 1-14 2-13 3-12 4-11 5-10 6-9 7-8
9 1-13 2-12 3-11 4-10 5-9 6-8 7-14

What should I know and have before I join?

  1. Have optimism and responsibility enough to keep track and endure the whole course.
  2. Know at least one programming language suitable for completing course.
  3. Know git and github well enough to send pull requests with your completed work.
  4. Have a laptop to join our workshops/offline meetings.

How do we organize our work?

  • offline meetings twice per week.
    • keeping track on progress
    • peer review
    • additional tasks presenting and review
  • no restrictions on programming language to use, but we should be able and willing to explain our code to those unfamilliar with my_beloved_programming_language

How to join?

since we are just starting - we will be happy to welcome new participants

  1. Join our gitter chat linked to this project
  2. Fork this repo.
  3. Create subdirectory %username% in \tasks directory.
  4. Send a pull request your work could be included and reviewed
  5. All work is ought to be organized in \tasks\user\week1\solution_1 manner.

Are there any online sessions planned?

Yes, there are. Starting from February 8th, every Thursday from 19-30 to 21-00 there will be a google hangout session devoted to answering questions and helping each others.

list of participants will be ordered by random.org

Plan for setup and jump start located here.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 100.0%