Twitxy Saved

Prayag

Verified account This account is verified. Learn more

@Prayag12B

AI engineer building for SaaS teams. Explaining neural networks, unpacking research, and sharing what breaks when you ship.
Shit post to
prayagbagthariya.vercel.app Joined December 2016
1.1K Following 1.1K Followers 5.5K Posts

Latest posts 5

Pinned post

Prayag Verified account @Prayag12B
Haptiker Product Hunt alternative
Link: edgevolume.vercel.app

#opensource #producthunt

Let me know if you have any feedback.
0:28
Prayag Verified account @Prayag12B Oct 7
#buildinpublic

Yesterday I came across Haptiker (producthunt.com/products/hapti…)
on Product Hunt. It lets you adjust your Mac’s volume by sliding along the trackpad edge.

Thought it would be fun to build my own, so I made EdgeVolume.

Still a work in progress, but yeah, here is the repo
github.com/reveuse12/edge…
#opensource
View quoted post on X
3 replies 2 reposts 29 likes 2.4K views View on X
Prayag Verified account @Prayag12B
Agents do not carry your project’s reasoning as reliably as your repository carries code.

After compaction or a fresh session, they may remember the goal but lose the rejected approaches, architectural constraints, and half-finished decisions.

Create WORKLOG.md at the start of a task with five sections:

Goal: one sentence.

Constraints: what must not change.

Current design: the relevant data flow or module boundary.

Tried and rejected: approaches that failed and why.

Next actions: small checkboxes, each with a verification step.

Example:

Goal: add idempotent webhook processing.

Constraint: do not change the public event schema.

Current design: receipt row is written before queue publication.

Rejected: retrying the whole handler, because it duplicates side effects.

Next: add a unique provider-event key; test duplicate delivery; inspect the database migration.

Then start each new session with:

“Read WORKLOG.md and the files named in it. Do not edit yet. Summarise the current design, the last failed approach, and the next unchecked action. If the file conflicts with code, stop and list the conflict.”

Update the file after every meaningful decision. Do not ask the model to maintain a huge diary. Keep it short enough that a human can review it in one minute.

This does not remove context limits. It changes what survives them. The durable file becomes a small map, while the agent retrieves the larger terrain only when needed.

Practical takeaway: preserve decisions, constraints, and failed approaches, not a transcript of the conversation.
Prayag Verified account @Prayag12B
Need a custom calculator? Build one.

Need to compare 200 products using your own criteria? Build a small tool.

Need a dashboard for an API that has no decent interface? Build one.

Sometimes a 100-line personal utility is more valuable than another $20/month subscription.
Prayag Verified account @Prayag12B
I noticed an interesting pattern in developer communities.

People are building dozens of applications with Claude Code.

Then they start another one.

And another.

Eventually, they have 40 project folders, multiple conversations and a collection of half-finished ideas.

Here's a rule I'd try:

Before starting another project, ask AI to review your existing unfinished projects.

For each one, make it answer:

What is already working?

What's preventing completion?

What is the smallest useful version?

What is the next concrete action?

Then choose one project to finish before opening another.

The ability to start building anything is becoming common.

The ability to finish useful things is still valuable.
9 replies 1 reposts 10 likes 690 views View on X
Prayag Verified account @Prayag12B
Someone turned a 7-year-old Kindle into a live dashboard using Claude.

It fetches public API data every hour, switches Wi-Fi off between updates and drains roughly 10% battery per week.

This is the kind of AI project I find interesting.

Not another SaaS clone. Making hardware you already own useful again.