https://github.com/sankalp1999/dsa_problems

Solutions to some standard DSA problems on InterviewBit and LeetCode including SDE sheet solutions
https://github.com/sankalp1999/dsa_problems

algorithms-and-data-structures dynamic-programming gfg-solutions graph-algorithms interviewbit-solutions leetcode sde-sheet

Last synced: about 1 month ago
JSON representation

Solutions to some standard DSA problems on InterviewBit and LeetCode including SDE sheet solutions

• Host: GitHub
• URL: https://github.com/sankalp1999/dsa_problems
• Owner: sankalp1999
• Created: 2020-07-22T12:03:36.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2022-02-18T10:22:04.000Z (almost 3 years ago)
• Last Synced: 2024-10-26T18:47:08.975Z (3 months ago)
• Topics: algorithms-and-data-structures, dynamic-programming, gfg-solutions, graph-algorithms, interviewbit-solutions, leetcode, sde-sheet
• Language: C++
• Homepage:
• Size: 1.81 MB
• Stars: 4
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Problem-solving()

This repository contains solutions of some of the problems I have solved on different platforms across the Internet.

- All problems in [Problem_Tree](https://github.com/sankalp1999/DSA_problems/blob/master/Problem_Tree.txt)

- SDE sheet solutions = Latest -> sde_sheet_revision_probs

- Graph algorithms = Latest -> Graph

- DisjointSet = Latest -> CF or DisjointSet folder

Check out my [Approach to CP in a nutshell](https://github.com/sankalp1999/3rdSem-Data-Structures-Lab#some-thoughts---cp-related) if you have interest in Competitive programming.

### Mind.push_back(points)

- Constantly, push throughout your comfort zone. It's recursive.

- Read the problem statement and constraints carefully. 

- Don't panic, giveup, rush.

- Work on a paper. Thinking is better on paper.

- No need to stress. Play.

## if(done) Reflection()

Emphasis should be on the thinking process.

:what small changes can I make in order to improve my speed/logic or efficiency in general?

- **Focus on thinking for more time**. Try to code after you are clear with the algorithm/logic

  Debug it if you think it's correct or if it is passing some later

test cases. Don't change approach abruptly.

- Think of some simple logic i.e from scratch initially and not apply any algo design technique directly. When you think from scratch, your previous experience might also help in solving. Later, you can apply other logic and patterns after sometime if implementation does not work. Basically, narrowing down after sometime.

- Avoid assuming difficulty of question initially. If scores are there, then thats good to estimate.

- Deep breaths or small breaks (1 - 2 minutes) can help.

## try {} catch {Common Mistakes}

-  Being lazy and not thinking properly. Not working on pen/paper

-  Mapping out previous problems to new problems. Solution: think from 1st principles

- Panicking

- Changing approach fast when some more checking can help get AC. This is basically hurrying. Try to stick longer and work out on paper.

- Do not get disheartened by failures/not being able to solve. Analyse your mistakes and move forward

- Don't run away from stuff you don't like/ basic difficult stuff. You will have to cover them sometime. 

## BFS(Resources)

[Youtube Channels for CP and CI](YoutubeChannels.md)

### A small post/article

[Meta Coding Interview Style Problem Guide](https://docs.google.com/document/d/1Cl0PZh6MQcb9XgcmiBkUXcoY7ahi7hO5sSRqwfU16Mc/edit#) - I had written this for a friend. Might help you also.

### Ignore Bookmarks 

1. https://happygirlzt.com/codelist.html

2. https://kennyzhuang.gitbooks.io/algorithms-collection/content/burst_balloons.html

3. http://adilet.org/

4. https://yangshun.github.io/tech-interview-handbook/

5. https://happygirlzt.com/codelist.html Nice youtube channels coering problems.Questions 

https://leetcode.com/discuss/general-discussion/494279/comprehensive-data-structure-and-algorithm-study-guide