NiharDaily

Work with me

I build the software I write about

I'm Nihar Ranjan Das — a software developer and the person behind NiharDaily. The analyses on this site are the same work I do for clients: reading what a technology actually does, then shipping something that uses it. If a post here answered your question, the build is the next step.

Projects start at $2,500. Smaller pieces of work are usually better served by an audit — one of the options below.

Start a projectEmail instead

What I take on

AI agents and LLM integration

Agent workflows, retrieval over your own documents, and model APIs wired into software you already run — built against what the models actually do today, not the launch-day demo.

  • Agent or assistant scoped to one real workflow, with the failure cases handled
  • Retrieval over your documents, tickets or catalogue
  • Cost and latency budget per request, measured rather than estimated

Full-stack web apps (Next.js / Node)

Product builds from an empty repository to a deployed application: server-rendered front end, API, database, auth, payments, and the deployment pipeline that ships it.

  • Next.js App Router front end with real SEO, not a client-side shell
  • API and database schema you can hand to another developer
  • CI, preview deploys, and production release on Vercel or your own host

Laravel and PHP development

New Laravel builds, and rescue work on PHP applications that have outgrown the person who wrote them — upgrades, queue and job pipelines, API layers, and test coverage where there is none.

  • Laravel application or module, tested and deployable
  • Framework and PHP version upgrades with a migration path, not a rewrite
  • REST or JSON API for an existing PHP codebase

Technical audits and consulting

A fixed-scope read of an existing codebase, site or architecture: what is slow, what is fragile, what is costing you search traffic, and what to do first. Written up so a non-engineer can act on it.

  • Prioritised findings with the evidence behind each one
  • Core Web Vitals, indexation and technical SEO review
  • A sequenced plan your team can execute without me

Automation and internal tools

The dashboards, scripts and scheduled jobs that stop a team doing by hand what software should do — including the content and publishing automation that runs this site.

  • Scheduled pipelines with alerting when they fail
  • Internal dashboards over data you already collect
  • Integrations between the SaaS tools your team already pays for

How it runs

  1. 1. You send the brief below.What you're building, what is blocking it, and the deadline that matters.
  2. 2. A call within two working days. Thirty minutes, free, and I tell you plainly if this is not work I should be doing.
  3. 3. A fixed-scope proposal. Deliverables, price and dates in writing before anything starts — no hourly surprises.
  4. 4. Weekly demos. You see running software every week, not a status report.

The work behind the writing

Recent deep dives on the subjects I build in. Read one before you write to me — it is the fastest way to tell whether we think about this the same way.

How MCP tool definitions and tool output consume Claude's context window

Your MCP connector spends context before you type

The advice you have read about MCP context cost is out of date. The old rule was simple. Every tool you connect gets injected up front, so a big connector spends a chunk of the window before you type

Sat Aug 22 2026 · 6 min read · 0 views

AISoftware

Amazon Bedrock prompt caching write and read pricing multipliers

Bedrock cache writes ate 85 percent of one AI bill

Prompt caching is sold as a saving. It can also be the single largest line on an inference invoice, and the failure is quiet, because a cache write succeeds whether or not anything ever reads it back.

Fri Aug 21 2026 · 6 min read · 1 views

AI

Start a project

Everything here reaches me directly. If you would rather not use a form, niharranjandasmu@gmail.com works just as well — and my author page has the rest of my links.