Activity Insights • Repo Structure • Approach • Features

Activity Insights

Language Breakdown

• Primary: Java
• Also used: C
• Occasional: Python / JavaScript (when useful for speed or experiments)

---

Repo Structure

src/          → one file per problem (Java-first)
Solutions/    → markdown notes (approach + complexity)
scripts/      → scaffolding (new_problem.sh)
templates/    → solution note template
assets/       → diagrams / images for selected notes

Quick Run

# Compile
javac .\src\SolutionName.java

# Run
java -cp .\src SolutionName

Scaffold a new problem

cd scripts
./new_problem.sh "Problem Name" java   # or: c | cpp | js

---

Approach

• Document > just solving It's better to document what we do.
• Step-by-step thinking, kept for future reference.
• Future use Coding is rarely clean; we revisit, copy, and adapt.

---

Features

• Structured solutions: one problem per file, predictable naming (underscores).
• Documentation-first notes: approach + complexity captured in Solutions/.
• Multi-language approach: Java core, C when it fits, scripting when it helps.
• Automation: scaffolding script + markdown template for fast, consistent logging.