Field notes from an AI Lead at Gravity9
I built Codehance to share what I am learning about using AI, working with AI, and building AI. Choose the conversation that matches where you are today.
You + a model
Use AI thoughtfully in the work you already do—from asking better questions to checking what comes back.
You + an agent
Move from prompting to collaboration: agents, context, tools, workflows, and the judgment that holds it together.
Your product + AI
Understand what it takes to create AI systems and product capabilities people can depend on.
New here?
One article to understand the whole framework before choosing your path.
Essential reading · 01
My brother, who has never written a line of code, and a software engineer with years behind him asked me the same question in the same month: I want to get into AI, where exactly do I start? There are three answers, they are different jobs, and the order you take them in matters.
Read the starting note →Latest field notes
I started by asking what Jev actually built. A four-subagent RAG example brought the opportunity into focus: useful decisions need useful context and software that knows what to do next.
The valuations attached to frontier-model companies will not rise forever. If they correct, the useful question for engineers is not whether AI disappears, but which parts of the stack remain worth understanding.
I keep hearing the same reaction around AI-heavy meetings: people leave tired, confused and unsure what was decided. The problem is not simply new terminology. It is what happens when teams discuss an AI solution before agreeing on the business problem.
Follow the questions that matter to your work, or subscribe to the RSS feed and take the journey at your own pace.
