Forem: Naveen Karasu

Day 1/60: Go backend development setup - Go Backend Engineering

Naveen Karasu — Fri, 24 Apr 2026 17:14:46 +0000

Day 1/60: Go backend development setup

60 Day Go Backend Engineering Challenge

Today I focused on building a Go backend workspace that makes services easy to run, test, and evolve. The strongest checkpoints were keep the module layout simple enough that handlers, services, and storage code do not bleed together, use go run, go test, and a small local config path as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the service design because they compound over 60 days.

The mistake I wanted to avoid was treating project shape as disposable and rebuilding the same service skeleton every week. The day felt better once the service boundary stayed visible and each component had one job.

The goal for tomorrow is simple: keep the rule clear enough that the next service still feels related to the same design idea. I also want to keep tracing one request path end to end because it exposes weak assumptions faster than a larger demo.

Day 1/60: JavaScript DSA environment setup - JavaScript DSA

Naveen Karasu — Fri, 24 Apr 2026 17:08:15 +0000

Day 1/60: JavaScript DSA environment setup

60 Day DSA in JavaScript Challenge

Today I focused on building a JavaScript setup that makes daily DSA work fast to run, inspect, and test. The strongest checkpoints were keep the project layout simple enough that daily problems share helpers and quick checks cleanly, use node, console checks, and test scripts as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the practice system because they compound over 60 days.

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

The goal for tomorrow is simple: keep the rule clear enough that the next variation still feels related to the same idea. I also want to keep tracing tiny examples because they expose weak assumptions faster than large random tests.

Day 1/60: Rust DSA environment setup - Rust DSA

Naveen Karasu — Fri, 24 Apr 2026 17:02:44 +0000

Day 1/60: Rust DSA environment setup

60 Day Rust DSA Challenge

Today I focused on building a Rust workspace that makes daily DSA work fast to run, test, and benchmark. The strongest checkpoints were keep the project layout simple enough that daily problems share tests and helpers cleanly, use cargo, tests, and benchmarks as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the practice system because they compound over 60 days.

The mistake I wanted to avoid was treating the workspace as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/75: Go DSA environment setup - Go DSA

Naveen Karasu — Fri, 24 Apr 2026 16:55:14 +0000

Day 1/75: Go DSA environment setup

75 Day DSA in Go Challenge

Today I focused on building a Go setup that makes daily DSA work fast to run, inspect, and benchmark. The strongest checkpoints were keep the project layout simple enough that daily problems share helpers and quick checks cleanly, use go run, go test, and tiny benchmarks as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the practice system because they compound over 60 days.

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/75: C++ DSA environment setup - C++ DSA

Naveen Karasu — Fri, 24 Apr 2026 16:48:12 +0000

Day 1/75: C++ DSA environment setup

75 Day DSA in C++ Challenge

Today I focused on building a C++ setup that makes daily DSA work fast to compile, run, and profile. The strongest checkpoints were keep the project layout simple enough that daily problems share helpers and quick checks cleanly, use g++, tiny harnesses, and fast reruns as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the practice system because they compound over 60 days.

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/60: Go backend development setup - Go Backend Engineering

Naveen Karasu — Fri, 24 Apr 2026 00:34:54 +0000

Day 1/60: Go backend development setup

60 Day Go Backend Engineering Challenge

Day 1/60: JavaScript DSA environment setup - JavaScript DSA

Naveen Karasu — Fri, 24 Apr 2026 00:26:54 +0000

Day 1/60: JavaScript DSA environment setup

60 Day DSA in JavaScript Challenge

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/60: Rust DSA environment setup - Rust DSA

Naveen Karasu — Fri, 24 Apr 2026 00:19:09 +0000

Day 1/60: Rust DSA environment setup

60 Day Rust DSA Challenge

The mistake I wanted to avoid was treating the workspace as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/75: Go DSA environment setup - Go DSA

Naveen Karasu — Fri, 24 Apr 2026 00:10:24 +0000

Day 1/75: Go DSA environment setup

75 Day DSA in Go Challenge

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/75: C++ DSA environment setup - C++ DSA

Naveen Karasu — Fri, 24 Apr 2026 00:02:35 +0000

Day 1/75: C++ DSA environment setup

75 Day DSA in C++ Challenge

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/75: Java DSA environment setup - Java DSA

Naveen Karasu — Thu, 23 Apr 2026 23:54:38 +0000

Day 1/75: Java DSA environment setup

75 Day DSA in Java Challenge

Today I focused on building a Java setup that makes daily DSA work fast to compile, run, and test. The strongest checkpoints were keep the project layout simple enough that daily problems share helpers and quick checks cleanly, use javac, small harnesses, and unit tests as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the practice system because they compound over 60 days.

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.

Day 1/75: Python DSA environment setup - Python DSA

Naveen Karasu — Thu, 23 Apr 2026 23:47:07 +0000

Day 1/75: Python DSA environment setup

75 Day DSA in Python Challenge

Today I focused on building a Python setup that makes daily DSA work fast to run, inspect, and test. The strongest checkpoints were keep the project layout simple enough that daily problems share helpers and quick checks cleanly, use the Python REPL, small scripts, and test files as part of the feedback loop instead of as afterthoughts, and treat tooling choices as part of the practice system because they compound over 60 days.

The mistake I wanted to avoid was treating the setup as disposable and rebuilding the same helpers every day. The day felt better once the invariant stayed visible and each update had one job.