Learning Technical

Documenting learnings of technical topics

📚 Table of Contents

• Overview
• 🚀 Quick Start
• 🏗️ Repository Structure
• 💻 Development
• 🧪 Testing
• 🤝 Contributing
• 📊 Project Stats
• 🔗 Resources
• 📝 License

🎯 Overview

This repository is a comprehensive learning resource for computer science fundamentals, containing thousands of coding problems and system design concepts from top interview platforms and educational resources. Whether you're preparing for technical interviews or strengthening your programming foundation, this repository provides structured practice across multiple programming languages.

✨ Key Features

• 🎯 20+ Coding Platforms: LeetCode, HackerRank, InterviewBit, and more
• 🏗️ System Design: Real-world architecture problems and solutions
• 📚 Book Solutions: Implementation from "Cracking the Coding Interview" and other technical books
• 🌐 Multi-Language Support: Java, Python, JavaScript implementations
• 🧪 Comprehensive Testing: Unit tests for all solutions
• 📊 Progress Tracking: Automated problem counting and statistics
• 🔄 CI/CD Pipeline: Automated testing and code quality checks

🚀 Quick Start

Prerequisites

• Java: OpenJDK 19+ (Download here)
• Python: 3.x (Download here)
• IDE: VS Code (recommended)

Installation

1. Clone the repository:

   git clone https://github.com/manastalukdar/learning-technical.git
   cd learning-technical

2. Run tests to verify setup:

   # Java tests
   ./gradlew test
   
   # Python tests
   python scripts/run_unit_tests.py

3. Open in VS Code (recommended):

   code .

Usage Examples

Run specific problem tests:

./gradlew test --tests "*TwoSum*"

Generate coverage report:

./gradlew jacocoTestReport

Count problems in repository:

python scripts/get_problems_count.py

🏗️ Repository Structure

learning-technical/
├── 📁 src/
│   ├── 🎯 LeetCode/              # LeetCode problems & solutions
│   ├── 🏆 HackerRank/            # HackerRank challenges
│   ├── 📖 CrackingTheCodingInterview/  # Book implementations
│   ├── 🎓 EducativeIo/           # Grokking coding patterns
│   ├── 🏗️ ByteByByteGo/          # System design content
│   ├── 💡 InterviewBit/          # Interview preparation
│   └── 📝 _notes/               # Study notes from tech books
├── 🧪 scripts/                  # Automation and testing scripts
├── 🌐 website/                  # Problem browsing interface
├── 📋 build.gradle              # Java build configuration
└── 📊 requirements.txt          # Python dependencies

Problem Organization

Each problem typically includes:

• 📄 readme.md - Problem description and approach
• ⚙️ metadata.json - Problem metadata and tags
• 💻 Solution files in multiple languages
• ✅ Comprehensive unit tests

💻 Development

Tech Stack

Technology	Version	Purpose
☕ Java	19+	Primary language for algorithms
🐍 Python	3.x	Secondary implementation language
📦 Gradle	Latest	Build automation and dependency management
🧪 JUnit 5	Latest	Java testing framework
📊 JaCoCo	Latest	Code coverage analysis
🔧 VS Code	Latest	Recommended development environment

Development Workflow

1. Create a new problem solution:

   # Navigate to appropriate platform folder
   cd src/LeetCode/src/Problems/P1_P100/P1_TwoSum/
   
   # Create solution and test files
   touch Java/Solution.java Java/SolutionTest.java

2. Run tests during development:

   # Run all tests
   ./gradlew test
   
   # Run specific test
   ./gradlew test --tests "SolutionTest"

3. Check code coverage:

   ./gradlew jacocoTestReport
   # View report at build/reports/jacoco/html/index.html

🧪 Testing

Running Tests

Java Tests (JUnit 5):

# Run all Java tests
./gradlew test

# Run tests with verbose output
./gradlew test --info

# Run specific test class
./gradlew test --tests "*TwoSum*"

Python Tests:

# Run all Python tests
python scripts/run_unit_tests.py

# Run individual test file
python -m pytest src/LeetCode/Python/test_solution.py

Coverage Reports:

# Generate Java coverage report
./gradlew jacocoTestReport

# View HTML report
open build/reports/jacoco/html/index.html

Continuous Integration

All code changes are automatically tested using:

• ✅ GitHub Actions: Build and test automation
• 🔍 Super Linter: Code quality and style checks
• 📊 CodeCov: Coverage reporting
• 🎯 Multiple OS Testing: Linux, Windows, macOS

🤝 Contributing

We welcome contributions! Here's how to get started:

Quick Contribution Guide

1. Fork the repository
2. Create a feature branch: git checkout -b feature/new-problem
3. Add your solution with tests
4. Run tests: ./gradlew test
5. Submit a Pull Request

Contribution Guidelines

• ✅ Include comprehensive test coverage
• 📝 Add clear problem descriptions
• 🏷️ Update metadata.json files
• 🎯 Follow existing code organization
• 📋 Reference original problem sources

Detailed guidelines: Contributing Guide

📊 Project Stats

• 🎯 20+ Coding Platforms covered
• 📚 1000+ Problems implemented
• 🌐 3 Programming Languages (Java, Python, JavaScript)
• 🏗️ System Design problems included
• ✅ Comprehensive Test Coverage
• 🔄 Active Maintenance and updates

🔗 Resources

🌐 External Links

• 📊 GitHub Projects - Project management

📚 Documentation

Document	Purpose
📋 Requirements	Development environment setup
🏗️ Architecture	System design and structure
🔄 CI/CD	Build and deployment pipeline
📊 Metadata	Project statistics and badges

⚠️ Important Notes

Learning Philosophy: This repository prioritizes understanding over original problem-solving. Solutions may reference existing implementations to accelerate learning. All sources are properly attributed.

Problem Uniqueness: Some problems appear across multiple platforms. We're developing a web interface to filter and display unique problem instances.

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

---

⭐ Star this repository if it helps you learn!

Report Bug • Request Feature