Neeraj Kumar Yadav · BuildWithNY

Safer AWS changes.
Clearer engineering.

I build developer tools and reliable backend systems, and share the decisions behind them through code, articles, and walkthroughs.

Explore the tools →Read engineering notes

5 years in production software · Full-stack engineer · Building in public

AWS Permission Review / illustrative output
Policy: report-worker

+ Action entry: s3:DeleteObject
~ Resource entry changed to "*"

Review the intended access.

Scope: supplied policy documents.
Effective access: not evaluated.
The first project is starting development. This is an example of the report being designed.
AWS & IAMTypeScript & Node.jsBackend reliabilityEvidence before claims
Current focus

Useful tools. Visible decisions.

Starting with permission reviews for small AWS-based software teams.

View the roadmap →
Starting development

AWS Permission Review

A CLI and pull-request workflow for explaining changes to IAM policies, with evidence and an explicit analysis scope.

Explore the project →
Engineering note

Why a JSON diff is not an IAM access analysis

A structural change is useful evidence. Understanding effective access requires a wider view.

Read the note →
Planned

Code walkthroughs

Short demonstrations covering implementation decisions, tests, and what each tool can actually establish.

See the video plan →
How I build

Make the reasoning inspectable.

01 / IMPLEMENT

Start with a real workflow

Small, reproducible examples and a focused first release. Add complexity when the workflow needs it.

02 / VERIFY

Test the important behaviour

Correctness, failure handling, and supported scope belong alongside the implementation.

03 / EXPLAIN

Show the trade-offs

Publish the reasoning, limitations, and changes made after feedback. Let people assess the work.

Working through an AWS delivery problem?

Tell me what your team is trying to review, automate, or make more reliable. We can discuss a focused implementation and a clear handover.

Discuss your workflow →