kishan-job/problemsolving

1. Repository Purpose

This is a Markdown knowledge-base repository, not an executable application. Its stated identity is problemSolving (README.md), but its content forms a broader personal reference system for problem solving, software engineering, business strategy, interview preparation, learning, and prompting.

2. Entry Points and Navigation

The root-level topical directories are the primary entry points:

• Problem-solving curriculum: problem solving/00-ProblemSolving-blueprint.md, problem solving/01-easy-problem-solving-guide-6-phases.md

• Software/career material: Guide/Software Guide/00-Developer Onboarding Guide.md, Guide/Software Guide/00-Project Execution Guide.md

• Business strategy material: Guide/Business Guide/00-Complete business universe map·md, Guide/Business Guide/01-brief.txt

• Prompt catalog: prompt/01-Learning Any Big New Topic-Prompts.md, Prompting-guide.md

There is no package manifest, source code, build system, deployment descriptor, or runtime entry point in the provided tree.

3. Problem-Solving Learning Path

The repository’s nominal core is a staged problem-solving framework. It progresses from a high-level blueprint into easier and harder workflows, then adds reusable references:

• problem solving/00-ProblemSolving-blueprint.md

• problem solving/01-easy-problem-solving-guide-6-phases.md

• problem solving/problemSolving-hard-8phases.md

Supporting material captures algorithm/pattern selection, regex, duplicate removal, and type-coercion concerns. This is a conceptual control flow for human decision-making rather than software execution.

4. Software Engineering Knowledge Domain

The software guide organizes developer onboarding, project execution, career progression, AI-job context, full-stack development, and stack depth:

• Guide/Software Guide/00-Developer Onboarding Guide.md

• Guide/Software Guide/00-Project Execution Guide.md

• Guide/Software Guide/01-techstack-deep.md

The architecture subdirectory is the most system-design-oriented boundary. It covers enterprise React, rendering modes, micro-frontends, monorepos, TypeScript compilation, and Spring Boot:

• Guide/Software Guide/Architecture map/00-Enterprise react architecture map.md

• Guide/Software Guide/Architecture map/06-AuthEnterprise Turborepo Monorepo — Next.js Apps + External Java Auth Service.md

• Guide/Software Guide/Architecture map/springBoot arc.md

These documents discuss external technologies such as React, Next.js, Vite, Turborepo, Java/Spring Boot, and authentication services, but the repository does not implement or provision them.

5. Interview and Practice Content

Interview preparation is separated by technology domains and moves from maps/foundations to multi-part guides and practice:

• JavaScript: interview prep/Js/00-js-interview-map.md, interview prep/Js/04-Interview questions.md

• React: interview prep/React/00-react-map.md, interview prep/React/ReactPractice/01-React practice part1-js.md

• TypeScript/testing: interview prep/Typescript/00-ts-complete map.md, interview prep/Testing/00-React testing roadmap.md

This is a consumer-facing study layer that reuses concepts from the software and problem-solving domains.

6. Business Strategy Domain

Business documentation supplies opportunity maps, business rankings, encyclopedia-style reference content, and personalized execution paths:

• Guide/Business Guide/00-Complete business universe map·md

• Guide/Business Guide/01-Easy-start Final 15 best businesses ranked.md

• Guide/Business Guide/My-Paths/001-Complete epr infrastructure plan.md

The My-Paths boundary contains more specific ventures, including software opportunities, certificate platforms, recycling/EPR infrastructure, and partnership strategies. These are planning artifacts, not deployed business systems.

7. Operating Model and Boundaries

Content is organized as independently readable Markdown/text documents with filename prefixes (00, 01, etc.) encoding intended reading order. The primary flow is: select a domain map → follow staged guides → consult focused references/practice/prompts. No automated ingestion, data persistence, APIs, CI/CD, cloud infrastructure, external service integration, or executable runtime is present in the repository tree.