Skip to content

Instantly share code, notes, and snippets.

View tatavarthitarun's full-sized avatar
🏠
Working from home

Tarun Tatavarthi tatavarthitarun

🏠
Working from home
  • Hyderabad
  • 21:04 (UTC -12:00)
View GitHub Profile
@PrinceSinghhub
PrinceSinghhub / DSA Calendar 2026 | Plan of Action.md
Last active January 10, 2026 14:44
Everything from 0 to Advance | DSA Calendar 2026 | Plan of Action

DSA Calendar 2026 | Plan of Action 🔥

DSA is no longer about solving random sheets or memorizing solutions. It’s about a clear, structured, and realistic approach from absolute beginner to interview-ready Candidate.

  • How to start DSA from zero (even if you don’t know coding)
  • When to focus on language basics vs DSA
  • A 3-phase preparation strategy used by serious engineers
  • Exact timelines for topics, patterns, and problem counts
  • Why 300–400 problems ≠ success (and what actually matters)
@mrsasha
mrsasha / README.md
Created July 13, 2018 08:25
Jacoco setup for calculating kotlin test coverage (single module)

Jacoco setup for calculating kotlin test coverage (single module)

put the jacoco.gradle file below somewhere in your app repo (like scripts folder), and then add apply from: '../scripts/jacoco.gradle' to your module gradle file.

This will add additional gradle build tasks to your app, in the form of "testFlavourUnitTestCoverage" that you can run manually (e.g. testStagingDebugUnitTestCoverage) to generate the coverage.

You can edit def excludes definition to further exclude classes you don't want to generate the coverage for. If you have source in other folders beyond those specified in def coverageSourceDirs, add them.

This will generate both exec file used by external code quality analyzers (like Sonarqube), in the build/jacoco folder, and XML and HTML reports, in the build/reports/jacoco/flavourName folder.