Skip to content

Programming-Tips-for-Success/Competitive-programming

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

64 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Coding Era

questions solved - stats

Programming

  • problem Solutions - There is no point in seeing the solution directly
  • Problem Solving - firstly think then write logic. write comments, high-level Pseudocode.
  • White Board Coding - a diagram, flowchart, more detailed sketches.
  • learn
    • How to speak everything you are thinking
    • How to verify that your code works (and check that it handles unexpected inputs correctly)
    • How to break a problem into parts
    • How to relate a problem to other problems you've seen/solved
    • How to test a problem against various data structures to see if it can be solved more cleverly
    • How to scope a problem (define it, identify/question assumptions, determine inputs & outputs)
    • How to write a brute force solution
    • How to improve the efficiency of a solution
    • How to externalize your thoughts
    • How to comment code in a helpful and organized manner
    • How to trace through code to verify that it works for sample inputs
    • How to identify where in your code you made a mistake if you aren't getting the output you expect
    • How to test individual parts separately
    • How to identify patterns in problems by going through sample inputs and considering expected outputs.
    • How Can you solve challenge in 4 lines of code or less?
    • How many approaches possible?
    • How to determine whether to use an iterative solution or a recursive solution
    • Every problem can be solved with recursion and without recursion
    • How Can I restate the problem in my own words?
    • What are the inputs that go into the problem?
    • What are the outputs that should come from the solution to the problem?
    • Can the outputs be determined from the inputs? In other words, do I have enough information to solve the problem? (You may not be able to answer this question until you set about solving the problem. That's okay; it's still worth considering the question at this early stage.)
    • How should I label the important pieces of data that are a part of the problem?

Algorithm problem includes

  • problem statement
  • input/output - General cases, base cases, error cases
  • Algorithm
  • code
  • Time and space complexity
  • bottlenecks
  • unnecessary work
  • duplicated work

challenges

To Visualize Code https://visualgo.net/en https://www.cs.usfca.edu/~galles/visualization/Algorithms.html https://algorithm-visualizer.org/ https://linked-list-visualizer.vercel.app/app

About

No description or website provided.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published