Goutam Prusty
WritingResearchProjectsAbout

Uses

The tools, software, and systems I rely on to learn, build, and publish.

I keep my setup intentionally simple — I care less about using the newest tool than finding software that disappears into the background so I can focus on thinking, building, and writing. These are the tools I use every day, and why I keep coming back to them.

Development

Next.js

The framework behind this site, utilizing App Router, static generation, and Edge Functions. It strikes a good balance between flexibility and convention, so I spend time on product problems instead of tooling.

TypeScript

I like software that fails early. TypeScript catches mistakes before they become bugs and makes revisiting old code far less painful.

Tailwind CSS

I think in layouts more than components. Tailwind keeps styling close to the markup, so I can iterate without constantly switching context.

pnpm

Fast, predictable, efficient. Once I switched from npm, I never had a reason to switch back.

Editor / IDE

Cursor, with AI enabled. I don't use it to generate entire applications; instead, I use it to explore unfamiliar codebases, automate repetitive tasks, and stay in flow while building.

Terminal

Ghostty + zsh. Fast, clean, and out of the way.

Writing & Research

This is where I spend most of my time. The workflow usually looks like:

Question→Research→Mental model→Writing→Build

ChatGPT

The tool I use most for exploring ideas and testing assumptions, helping rough questions become clearer questions.

Gemini Deep Research

When a topic deserves more than a conversation, I use Deep Research to gather sources, compare viewpoints, and build a structured foundation before I start writing.

Claude

My preferred editor for long-form writing. I use it to sharpen structure, pressure-test weak arguments, and make technical ideas easier to follow.

MDX

Everything I write lives in plain Markdown, extended with React components where needed. Files are version-controlled in Git, decoupled from any CMS, ensuring my work outlives any framework.

Notes

Still evolving. I'm experimenting with a lightweight personal knowledge system that prioritizes writing over collecting. The goal isn't to save everything; it is to understand enough to explain it in my own words.

Hosting & Infrastructure

Vercel

Deployments should be boring. Push to Git, wait a few seconds, the site is live.

GitHub

Every article, project, and research report starts here. Version control isn't just for code; it tracks the history of how ideas evolve.

Cloudflare

DNS, caching, and a little extra speed everywhere.

Philosophy

People often ask about tools, but the biggest improvements rarely come from switching software. They come from building better habits. The tools I keep are the ones that help me think more clearly, reduce friction, and let me spend more time solving problems than managing software.

Principles

01

Boring tools over trendy tools.

I optimize for reliability, not novelty.

02

Plain text whenever possible.

I want my work to stay portable for years.

03

Own your data.

I prefer tools that make exporting easy.

04

Reduce context switching.

Every extra app has to justify its existence.

05

AI should amplify thinking, not replace it.

I use it to explore ideas, review code, and challenge my own assumptions — not to outsource judgment.

Goutam Prusty

Learning in public. Building with intention.

Personal notebook for projects, research, and writing.

NowResumeUsesRSSContact

© 2026