---
title: "Akash Goenka (@akashgoenka) | Hashnode"
description: "Akash Goenka (@akashgoenka) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@akashgoenka"
---

@akashgoenka

# Akash Goenka

@akashgoenka · Bengaluru, India · Joined August 2026

### [Notes about code should be written by whoever read the code](https://codebase-memory.hashnode.dev/notes-about-code-should-be-written-by-whoever-read-the-code?utm_source=hashnode&utm_medium=feed)

Why codebase notes for AI coding agents should be written by the agent that did the work, not reconstructed later from a transcript.

6 min read · [codebase-memory.hashnode.dev](https://codebase-memory.hashnode.dev/notes-about-code-should-be-written-by-whoever-read-the-code?utm_source=hashnode&utm_medium=feed)

[Aug 3](https://hashnode.com/posts/notes-about-code-should-be-written-by-whoever-read-the-code/6a70ec4759f04c38ec57e28b)

### [From four tools to two](https://codebase-memory.hashnode.dev/from-four-tools-to-two?utm_source=hashnode&utm_medium=feed)

An origin story told through deletions, the traversal tools that were missing fields, the labels that were guesses and the server that served nothing

13 min read · [codebase-memory.hashnode.dev](https://codebase-memory.hashnode.dev/from-four-tools-to-two?utm_source=hashnode&utm_medium=feed)

[Aug 3](https://hashnode.com/posts/from-four-tools-to-two/6a70eba0a6d55c4a3c29f0eb)

### [The tool the agent does not call](https://codebase-memory.hashnode.dev/the-tool-the-agent-does-not-call?utm_source=hashnode&utm_medium=feed)

You can ship a tool, document it, and instruct the agent to prefer it and it will still reach for grep. Why availability isn't adoption.

8 min read · [codebase-memory.hashnode.dev](https://codebase-memory.hashnode.dev/the-tool-the-agent-does-not-call?utm_source=hashnode&utm_medium=feed)

[Aug 3](https://hashnode.com/posts/the-tool-the-agent-does-not-call/6a70e9d792fbdf461f05b8e4)

### [Why an index of your code cannot answer the same question twice](https://codebase-memory.hashnode.dev/why-an-index-of-your-code-cannot-answer-the-same-question-twice?utm_source=hashnode&utm_medium=feed)

A code graph makes each step of a search cheaper. It never reduces how many steps you need, and it can't hold a conclusion and that gap matters.

10 min read · [codebase-memory.hashnode.dev](https://codebase-memory.hashnode.dev/why-an-index-of-your-code-cannot-answer-the-same-question-twice?utm_source=hashnode&utm_medium=feed)

[Aug 3](https://hashnode.com/posts/why-an-index-of-your-code-cannot-answer-the-same-question-twice/6a70e8d009ceda0c02061cfc)

### [Where the tokens go in an agent session](https://codebase-memory.hashnode.dev/where-the-tokens-go-in-an-agent-session?utm_source=hashnode&utm_medium=feed)

Most of what an agent session costs isn't the answer it produced — it's the same context, re-sent on every turn. Here's the one lever that matters.

7 min read · [codebase-memory.hashnode.dev](https://codebase-memory.hashnode.dev/where-the-tokens-go-in-an-agent-session?utm_source=hashnode&utm_medium=feed)

[Aug 3](https://hashnode.com/posts/where-the-tokens-go-in-an-agent-session/6a70e3a277aa6e54117da7f7)
