An open API service indexing awesome lists of open source software.

https://github.com/devbigboy/problem-solving-activity


https://github.com/devbigboy/problem-solving-activity

Last synced: 4 months ago
JSON representation

Awesome Lists containing this project

README

          

# Problem-Solving-Activity#
# Problem Solving Activity

### Content
- Intro
- Important Links
- Glossary
- Do's & Dont's

## Important Links

Find a list of some important links related to the activity

| |Description |Link |
|:----------------:|-------------------------------|:-----------------------------:|
|CodeForces Site|Very popular and trusted problem solving platform that is known worldwide.|Click Here |
|Activity Guide|A recorded video explaining our plan for the problem solving activity.|Click Here |
|CodeForces Guide|Video explaining CodForces registration, problem sets, submission, etc.|Click Here |
|Thinking Approach Pt. 1|Very beneficial video explaining how to approach a problem when you want to solve it.|Click Here |
|Thinking Approach Pt. 2|Very beneficial video explaining why you should think on paper not on your PC.|Click Here |
|Problem Sets Sheet|Weekly updated with the required problems on Codeforrces. Includes Basic and Challenge sets.|Click Here |
|ICPC Community|ICPC Mansoura Community is a Facebook group for problem solving students. |Click Here |

## Glossary

Useful expressions you may hear in the problem solving community. It will be regularly updated.

|Expression |Meaning |
|:----------------:|-------------------------------|
|Handle|Your username in CodeForces platform.|
|Problem Set|A collection of problems related to a contest or activity.|
|Submission|Sending your code to the CodeForces judge to evaluate your solution.|

## Do's & Dont's

Here are some pieces of advice we though might help.


### Do's:

- Think of the solution (preferably on a paper) before starting to code.
- Stick to standards (CodeForces compiler is strict).
- Have confidence in your own abilities.
- Code in CodeBlocks or any IDE first, then submit after you test it.
- ALWAYS write clean code, make it readable; so that it's easier to debug and review.
- Test your code against the example inputs and verify the outputs.
- Be aware of the time limit in each problem.
- Make sure to choose "GNU G++ 17" from the compilers list.

### Dont's

- Never compare yourself to others in a destructive manner (Everyone started as a begginer one day).
- Don't imagine an easy development (It takes time, be patient).
- Try not to rush your submission (Test and verify first).
- We are only creating an environment for those who are willing, don't feel that it's obligatory to participate.
- Most of the problems have solutions online (Try on your own so that you can rank up).

## Finally
Make sure to have fun and enjoy the interesting and exciting problem solving realm.