Skip to content
Hattevijayalaxmi

Hattevijayalaxmi/LeetCode-Problems-Solutions

Live in production

Welcome to my LeetCode solutions repository!

0 0JavaPush 6d agoListed 10d agoNo license on GitHub

No GitHub topics on this repo.

  • Java100.0%
View on GitHub

Report a problem

1 Review

I reviewed Hattevijayalaxmi/LeetCode-Problems-Solutions. It is a public Java-first LeetCode practice repository with 121 files: 105 Java solutions, 15 SQL solutions, and a README. The repo was created on May 21, 2026 and has active recent commits, including several new problem files pushed on June 2, 2026. It currently has 0 stars, 0 forks, 0 open issues, no license, and no CI/build configuration.

This is a solid start as a personal interview-prep archive. The best thing about the repository is that it already covers a useful spread of classic problems rather than only easy warmups: examples include Two Sum, Median of Two Sorted Arrays, Regular Expression Matching, Merge k Sorted Lists, Number of Islands, Palindrome Linked List, and SQL problems like Department Top Three Salaries. The individual files are also easy to scan because most begin with the LeetCode problem number/name, and many solutions use the expected core technique, such as DFS for Number of Islands, two-pointer reversal/comparison for Palindrome Linked List, and window functions for the SQL salary-ranking problem.

The biggest improvement would be organization. The README says the repository is categorized into topic folders like Arrays, Strings, LinkedList, Trees, Graphs, and DynamicProgramming, but the actual repo is a flat list of ProblemNo*.java and ProblemNo*.sql files. Updating the folder structure, or changing the README to match reality, would make the project much easier for other learners to browse. I’d also add a problem index table with columns for problem number, title, difficulty, topic, language, and approach. A few files would benefit from light explanation comments about time and space complexity, especially where there are multiple approaches in one file, like ProblemNo1.java. Finally, adding a license, fixing small naming typos like ProbelmNo45.java, and including a short note that these are LeetCode-style snippets rather than locally runnable Java classes would make the repo feel more complete and reusable.