RepoJournal

Developer journal

Anurag Verma

@anurag629 since Jan 2022

144 stories across 32 days in 2021

Mon Wed Fri
Aug Sep Oct Nov Dec
an entry to read activity only Less More before entries began Full year →

Entries start Jan 13, 2022 — we reconstructed the previous month from @anurag629's public GitHub activity on the day they joined. Squares before that show contribution counts only.

Add this graph to your GitHub README

Paste this Markdown into your README — the badge stays current automatically and links back here.

[![anurag629's work on RepoJournal](https://repojournal.com/journals/anurag629/heat.svg)](https://repojournal.com/journals/anurag629)

Friday, Jul 10, 2026

Started 60-day system design curriculum with latency measurement labs

Anurag launched a structured eight-week system design course in anurag629/system-design-60-days with hands-on labs measuring real hardware performance across the storage hierarchy.

1 person shipped this

The curriculum spans from ground-truth estimation through storage, caching, async, distributed systems, AI systems, and production concerns [1]. Day 1 includes a scaffolded Python lab that measures RAM, SSD, localhost, and internet round trips on the reader's own machine.

Anurag spent the day fixing measurement bugs that were skewing the results. The internet latency probe was using www.mit.edu and www.unimelb.edu.au, both of which resolve to CDN edges rather than their labeled regions, so he replaced them with AWS regional endpoints [2]. The socket layer was also performing a DNS lookup on every connection attempt, timing "DNS + handshake" instead of a pure round trip, so he resolved hostnames once and reused them [2].

The SSD measurement was reporting memory latency instead of disk latency because the test file was cached in RAM. Anurag set F_NOCACHE on both the write and read handles and added an fsync before closing to ensure bytes reached the device [3]. Day 1 measurements showed "SSD random 4 KB read 84.7 us" and "localhost TCP round trip 19.5 us", revealing that the network beat the disk by 4.3x [4].

He also mapped free resources to each of the eight weeks [5] and added verified resource links to each day, week, and a master resource list, checking that all 200 links resolve [6].

Sources

  1. Start 60-day system design plan: week 1 and day 1 · anurag629/system-design-60-days
  2. Fix internet latency probe: honest hosts, resolve DNS once · anurag629/system-design-60-days
  3. Fix SSD measurement: keep the test file out of the page cache · anurag629/system-design-60-days
  4. Day 1 results, and Day 2: estimation vs reality · anurag629/system-design-60-days
  5. Add free resource list, mapped to the eight weeks · anurag629/system-design-60-days
  6. Add verified resource links to each day, week, and the resource list · anurag629/system-design-60-days

← All entries

Follow along

Follow anurag629

A short briefing every day anurag629 ships something — in about 3 minutes.

or

One email a day. Unsubscribe in one click. Read a past issue →

RSS Read other developers