How kiranraoboinapally/java-practice-problems works
Main Project Components
– Java Programs (the bulk of the repository)
– SQL Concepts
– Web/Frontend Examples (HTML, JavaScript)
– Additional Languages (Python, etc.)
Break Down the Java Programs Section
• Under the “Java Programs” block, subdivide further to represent the organization shown in the file tree and README:
– Basics: Contains fundamental programs (age.java, swapBitwise.java, etc.)
– Loops: Further subdivided into “for”, “while”, and “do-while” folders.
– Arrays: All array-related problems (such as sorting, searching, rotations).
– Strings: String manipulation problems and supporting examples.
– OOPS: All files that demonstrate Object-Oriented Programming concepts.
– Collections: Programs related to Java’s collection framework.
– Exceptions: Source files dealing with error handling.
– Leetcode: Solutions to external coding problems.
– Rough: Experimental or rough drafts of problems.
– Additionally, include a block for “SpringBoot Projects” (which itself is subdivided into firstproject, secondproject, thirdproject, one) to capture microservice-like examples using Spring Boot.
SQL Concepts Component
• Inside this block, note that the “ChatGPT.md” file and other SQL related documents serve as documentation and query practice material.
Web/Frontend and Other Language Components
• HTML & JavaScript:
– A separate block for “HTML” that shows various sample HTML files (forms, pages, style examples).
– A block (or a note within the HTML block) indicating associated CSS and “rough” examples in the HTML folder.
– Similarly, a “JavaScript” block for the files in js/ (e.g., first.html, first.js, second.js).
• Python:
– A small block labeled “Python” that includes the hello.py script.
– The “Java Programs” section is the primary learning engine.
– “SQL Concepts” and “Web/Frontend” samples serve as supporting or complementary learning material.
Architectural Patterns and Design Principles
• Following:
– Modular organization: the division of Java practice problems by topic (basics, loops, arrays, etc.) supports a modular design.
– For Spring Boot modules, note the typical layered architecture (src/main/java for main code, src/test/java for tests, and the use of dependency injection if applicable).
– Use grouping to represent “Experimental or Rough Work” which is kept separate.
Final Assembly
• Branch off into major components: Java, SQL, HTML/JS, and Python.
• Optionally, add annotations (like “SpringBoot Projects” are examples of microservices architecture) to provide context.