<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Dhruv Kothari — Writings</title>
<link>https://kothariji.in/writings/</link>
<atom:link href="https://kothariji.in/rss.xml" rel="self" type="application/rss+xml" />
<description>Posts and notes by Dhruv Kothari, a software engineer.</description>
<language>en</language>
<item><title>Build your own JSON parser</title><link>https://kothariji.in/writings/build-your-own-json-parser/</link><guid>https://kothariji.in/writings/build-your-own-json-parser/</guid><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate><description>Your code calls JSON.parse all the time. This tutorial shows what happens inside it, and how to build a JSON parser yourself.</description></item>
<item><title>Six hours, from Slack thread to shipped UI</title><link>https://kothariji.in/writings/notes/six-hours-end-to-end/</link><guid>https://kothariji.in/writings/notes/six-hours-end-to-end/</guid><pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate><description>So today, here is what I did. Slack/Looms → intent, personas &amp; conversion gaps → journey → Figma MCP → critique with Impeccable → built with Claude Code. Used @coreyhainesco's marketing-skills throughout. 6 hours, end-to-end. What a wild time to be a curious engineer. 👨‍💻</description></item>
<item><title>Noticing beauty, noticing pain</title><link>https://kothariji.in/writings/notes/noticing-beauty-and-pain/</link><guid>https://kothariji.in/writings/notes/noticing-beauty-and-pain/</guid><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><description>The same mind that notices extraordinary beauty often notices ordinary pain more vividly. Maybe that's the price of seeing the world a little differently.</description></item>
<item><title>The shift toward engineers who do it all</title><link>https://kothariji.in/writings/notes/jack-of-all-trades/</link><guid>https://kothariji.in/writings/notes/jack-of-all-trades/</guid><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><description>I can sense a shift. A move toward "jack of all trades." Frontend devs are picking up backend work. Backend devs are finding it easier to handle UI. Curious devs are leaning into becoming generalists. One thing's clear - curious devs will climb faster.</description></item>
<item><title>Taste is why AI is not there in frontend</title><link>https://kothariji.in/writings/notes/taste-is-subjective/</link><guid>https://kothariji.in/writings/notes/taste-is-subjective/</guid><pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate><description>Frontend is all about design, and design is all about taste. But taste is subjective. That is exactly why AI is not fully there yet.</description></item>
<item><title>How Redis snapshots with copy-on-write</title><link>https://kothariji.in/writings/notes/redis-copy-on-write/</link><guid>https://kothariji.in/writings/notes/redis-copy-on-write/</guid><pubDate>Thu, 06 Jun 2024 00:00:00 GMT</pubDate><description>Redis Copy-on-Write (COW) snapshot optimization! 💾 Instead of duplicating all data for a snapshot, Redis marks data as read-only and only copies modified data. This minimizes memory usage and boosts performance. Efficient and clever 💡</description></item>
<item><title>Hop-by-hop vs end-to-end HTTP headers</title><link>https://kothariji.in/writings/notes/hop-by-hop-headers/</link><guid>https://kothariji.in/writings/notes/hop-by-hop-headers/</guid><pubDate>Wed, 05 Jun 2024 00:00:00 GMT</pubDate><description>Hop-by-hop and end-to-end headers in HTTP! 🌐 Hop-by-Hop: Processed by each intermediary (like proxies) and not forwarded (e.g., Connection, Keep-Alive). End-to-End: Carried the entire path to the final recipient (e.g., Content-Type, User-Agent)</description></item>
<item><title>REPL: the read–eval–print loop</title><link>https://kothariji.in/writings/notes/repl-read-eval-print-loop/</link><guid>https://kothariji.in/writings/notes/repl-read-eval-print-loop/</guid><pubDate>Fri, 24 May 2024 00:00:00 GMT</pubDate><description>Repl (in programming) stands for Read–eval–print loop</description></item>
<item><title>The URL fragment never reaches the server</title><link>https://kothariji.in/writings/notes/fragment-identifier/</link><guid>https://kothariji.in/writings/notes/fragment-identifier/</guid><pubDate>Tue, 14 May 2024 00:00:00 GMT</pubDate><description>(very late 🥲) The fragment identifier, or the part of a URL that comes after the # symbol, is not sent to the server as part of an HTTP request and is not directly accessible on the server side</description></item>
<item><title>June 1, the universal birthday date</title><link>https://kothariji.in/writings/notes/june-1-universal-birthday/</link><guid>https://kothariji.in/writings/notes/june-1-universal-birthday/</guid><pubDate>Sat, 23 Mar 2024 00:00:00 GMT</pubDate><description>June 1 is considered a universal birthday date for people who have forgotten their actual birth date. 🥲</description></item>
<item><title>/usr means Unix System Resources, not user</title><link>https://kothariji.in/writings/notes/usr-unix-system-resources/</link><guid>https://kothariji.in/writings/notes/usr-unix-system-resources/</guid><pubDate>Sat, 20 Jan 2024 00:00:00 GMT</pubDate><description>/usr in Linux file system stands for Unix System Resources and not user.</description></item>
<item><title>Unsolicited late-night thoughts: Placements</title><link>https://kothariji.in/writings/late-night-thoughts-placements/</link><guid>https://kothariji.in/writings/late-night-thoughts-placements/</guid><pubDate>Wed, 05 Jan 2022 00:00:00 GMT</pubDate><description>Written at 2:36 a.m. A preparation strategy in four verticals, and the things I wish someone had told me a year earlier.</description></item>
<item><title>SyntaxMeets — the curious saga</title><link>https://kothariji.in/writings/syntaxmeets-the-curious-saga/</link><guid>https://kothariji.in/writings/syntaxmeets-the-curious-saga/</guid><pubDate>Sun, 21 Mar 2021 00:00:00 GMT</pubDate><description>How three of us built a real-time collaborative coding room during the pandemic: React, Socket.IO, Express, and a drawing pad for the algorithm.</description></item>
<item><title>Must-Know C++ tips and tricks for Competitive Programming — Part 1</title><link>https://kothariji.in/writings/cpp-tips-for-competitive-programming/</link><guid>https://kothariji.in/writings/cpp-tips-for-competitive-programming/</guid><pubDate>Thu, 11 Jun 2020 00:00:00 GMT</pubDate><description>Seven things that save time in a contest: bits/stdc++.h, endl versus \n, auto, range-based loops, string conversions, cctype, and a code visualizer.</description></item>
<item><title>Complete guide to kick-off Competitive Programming!</title><link>https://kothariji.in/writings/kick-off-competitive-programming/</link><guid>https://kothariji.in/writings/kick-off-competitive-programming/</guid><pubDate>Thu, 19 Mar 2020 00:00:00 GMT</pubDate><description>Where to start, which platforms to practise on, and the five things a beginner should keep in mind.</description></item>
</channel>
</rss>