Saraswati Stitch needle-and-thread markSaraswati Stitch®contact@saraswatistitch.com
← All stitches

The Resource · Field notes

Field notes.

Our own take on talks, releases, and ideas moving through the AI field, source always credited.

Use AI to learn, not just to get answers

Most people ask AI a question, copy the answer, and retain nothing. Used differently, the same tool becomes the best tutor you have ever had. The shift is small and almost nobody makes it.

Read the stitch

Your first AI agent: when to build one, and how to define it

The difference between a chatbot and an agent is the difference between a meeting and an employee. Most first agents fail for two boring reasons, and both are fixable before you build anything.

Read the stitch

AI content pipelines: the assembly line reaches creative work

A full 3D documentary, an animated historical film, produced almost entirely by an AI pipeline. Creative work just got an assembly line, and the same old rule decides whether the output is worth watching.

Read the stitch

The biggest problem with AI is not capability. It is trust.

People keep waiting for AI to get smart enough. For most business work, it already is. The thing actually blocking adoption is quieter and harder: can you trust what it produces enough to act on it?

Read the stitch

The honest way to make money with AI: sell a solved problem, not "AI"

Sell Claude workflows, build a $12k-a-month channel, sign AI clients fast. Most make-money-with-AI advice is hustle theater. The honest version is boring, durable, and it does not lead with the letters A and I.

Read the stitch

Building an AI "second brain" that actually holds up

Connect a few tools, capture every note and voice memo, and let AI organize your whole life. The second-brain idea is real and useful, and most builds collapse within a month. The difference is not the tools.

Read the stitch

Your AI bill is a context problem

Someone recently cut a model bill in half by rendering text as images to dodge the tokenizer. It is a clever hack, and it points at the real lesson: your AI cost is a context problem you can actually manage.

Read the stitch

What a business should take from the AI-doom discourse

You have three years left. Superintelligence is coming and it is scary. The doom discourse is gripping and mostly useless for running a business, but not entirely. Here is the part worth keeping.

Read the stitch

The real workflow for building with AI (it is not one prompt)

The demos make building with AI look like one prompt and a finished app. The real workflow is less magical and far more effective, and it is mostly the opposite of how beginners use these tools.

Read the stitch

The cost of intelligence is collapsing. Plan for it.

Every few weeks a frontier model gets 50 or 80 percent cheaper, usage jumps five-fold, and the discount pays for itself. The price of intelligence is falling on a curve, and it should change your plans.

Read the stitch

Open-weight models are a business decision, not an ideology

The open-source AI debate has become a religious war. Strip out the ideology and the question a business actually faces is dull and practical: control, privacy, cost, and who owns the off switch.

Read the stitch

Does AI create jobs or destroy them? Wrong question.

Every week a new report declares that AI will create more jobs, or destroy them all. They cannot both be right, and the fight over the headline hides the thing that actually matters.

Read the stitch

The harness matters more than the model

People argue endlessly about which model is best, and the same model somehow gets called both brilliant and useless. They are usually not judging the model. They are judging the harness around it.

Read the stitch

Coding was never the hard part? Only half true.

A popular take says coding was never the hard part. As a claim it is half true, and the untrue half is where the money and the difficulty actually live.

Read the stitch

How good does AI have to get before you stop reading its code? Never.

People keep asking how good models must get before we stop reviewing their code. The honest answer is never, and the reason is more than caution.

Read the stitch

Stop pointing AI at problems that do not need it

People are handing AI jobs that a plain script does faster, cheaper, and without the chance of deleting your home directory. That is not innovation, it is a downgrade.

Read the stitch

The "AI employee" is a stack of gaps, not one tool

The dream of an AI employee that never sleeps is real. What the demos hide is that no single tool is the employee. It is a stack, and the stack is the hard part.

Read the stitch

"Delete your CLAUDE.md": the case for leaner AI context

The instinct is to feed an AI agent more context. The people who built the agent keep telling you to feed it less.

Read the stitch

You are not getting less from AI because the model is weak

Most people ask an AI a question, get an answer, and leave. The same model, pushed differently, would have told them what they actually needed to hear. The difference is direction.

Read the stitch

What actually carries the quality when an AI agent builds your site

We rebuilt this very site with an AI coding agent. It is fast and genuinely good, and it still cannot decide what "good" means.

Read the stitch

The AI tools got free. The advantage moved to your data.

When a giant gives away a tool that used to cost thousands, it is not charity. It is a signal about where value is moving, and it is moving toward the one thing you own and they do not.

Read the stitch

Avoiding "AI slop": generated design still needs a human eye

"AI slop" became a phrase because so much generated design looks the same. The fix is not a better generator.

Read the stitch

Agentic AI integration: lab numbers vs the shop floor

Enterprise Japan just made a very large bet that AI agents can run the entire software-integration pipeline. The headline productivity number is 200x. The number that matters is much smaller.

Read the stitch

Why AI is going vertical, and what it means for small teams

The general-purpose chatbot was the demo. The durable value is turning out to be narrow, deep, and domain-shaped.

Read the stitch

Agentic AI accountability: when the workflow says no, who answers for it?

Picture an agentic workflow that quietly declines the wrong customer because of a fault upstream. Now picture the meeting where your organization decides whose fault that was.

Read the stitch

Graph engineering: give the agent a map, not a haystack

An AI agent loose in a big codebase is a smart intern with no map. The fix is to give it the map.

Read the stitch

AI ticket triage: what it does well, and the line it must not cross

A ticket lands, and before a human reads it the system has already tagged it, summarized it, and drafted the first response. That is a genuinely good use of AI, right up to one hard boundary.

Read the stitch

If we had to rebuild the agency from zero with AI

The "make money with AI" videos sell tricks. The real answer is older and duller than any trick, and it still works.

Read the stitch

MCP is leaving the chat window

An AI that builds a city inside a game engine sounds like a gimmick until you read the three rules Epic used to make it work. Those rules are the whole point, and they are not about games.

Read the stitch

AI consciousness is a fascinating question and a business distraction

People love arguing about whether AI is conscious. It is a great debate and a terrible basis for a business decision, because a system does not need an inner life to be useful or to be dangerous.

Read the stitch

Everyone has the same AI. That was never the advantage.

A student asked a sharp question: if everyone has the same AI, how do you stand out using it? The answer is the same for a business as it is for a beginner.

Read the stitch

How to read AI news without getting played

Every week an AI podcast tells you the singularity got closer. Most of it will not change a single thing you do. Here is how to tell the difference before you act on any of it.

Read the stitch