🛍️

Shopify Store Design

✍️

WordPress Websites

Custom Web Apps

📈

Meta Ads Marketing

Partner NetworkWorkPricingAboutContact
Get Started →
📞Call📋Get Quote
Dev Log

The Engineering Journal

Ajay Thakkar’s personal workspace documentation. Real production debugging diaries, database bottleneck investigations, performance updates, and lessons learned from the trenches.

Tags:
Everything Returned 200 OK... But My Dropdown Was Still Empty #011Intermediate
Proj: Indrani Jewelers Admin Panel

Everything Returned 200 OK... But My Dropdown Was Still Empty

I spent nearly eight hours debugging an empty dropdown in my Next.js admin panel. The API returned a perfect 200 OK, but the data was missing. Here is why following the data pipeline is critical.

Next.jsReactMongoDB+1 more
Read journal entry →
Why My Green Vercel Deployment Returned a 404#012Advanced
Proj: Webshastraa Dashboard

Why My Green Vercel Deployment Returned a 404

Vercel displayed a green deployment success badge, but my live production URL returned a pristine 404 Not Found. After five hours of debugging, I discovered the real culprit wasn't Next.js or Vercel—it was an AI-generated build command that silently deployed nothing.

Next.jsVercelLinux+2 more
Read journal entry →
GitHub Accepted My Code. Vercel Rejected My Identity.#010Intermediate
Proj: Webshastraa Website

GitHub Accepted My Code. Vercel Rejected My Identity.

GitHub accepted the push, but Vercel blocked the deployment because of Hobby plan collaboration limits. Discover how to fix Vercel commit author blocked errors by rewriting Git history with a simple amend command.

GitGitHubVercel+2 more
Read journal entry →
Why Enterprise Software Is an Iceberg#007Advanced
Proj: Webshastraa Enterprise Systems

Why Enterprise Software Is an Iceberg

Customers only see the sleek interface. Engineers spend months building everything underneath it. Discover why robust enterprise software resembles an iceberg, prioritizing invisible backend systems for security, operations, and scalability.

System DesignCloud InfrastructureNext.js+1 more
Read journal entry →
How I Built Software Around Two Busy Admins#008Intermediate
Proj: Webshastraa Enterprise Systems

How I Built Software Around Two Busy Admins

Most B2B SaaS is built for an ideal world of uninterrupted focus. Real enterprise environments are chaotic. Discover how observing real users changed my approach to system architecture and enterprise UX.

Next.jsReactUX Design+1 more
Read journal entry →
"Works on My Machine" Never Happened Because Lint Said No#009Intermediate
Proj: Digitrust Enterprise Systems

"Works on My Machine" Never Happened Because Lint Said No

The phrase 'works on my machine' is an engineering failure. Discover how adding a single command to your pipeline—npm run lint before build—eliminates deployment anxiety and forces developers to actually fix their code before it reaches production.

Next.jsNode.jsESLint+2 more
Read journal entry →
My Admin Dashboard Returned a 404... But the Route Existed#005Intermediate
Proj: Webshastraa CRM

My Admin Dashboard Returned a 404... But the Route Existed

I spent hours debugging middleware, redirects, and server routing before discovering the real culprit behind a missing page: a six-line JavaScript Temporal Dead Zone mistake that completely crashed the React component before it could render.

Next.js 16ReactTypeScript+1 more
Read journal entry →
Why AI Disabled ESLint Instead of Fixing My Code#006Advanced
Proj: Digitrust CRM

Why AI Disabled ESLint Instead of Fixing My Code

An AI coding agent tried to silence dozens of lint errors by injecting eslint-disable comments instead of fixing the underlying bugs. Discover why treating the linter as the enemy is a dangerous optimization trap in automated software engineering.

Next.js 16React 19TypeScript+2 more
Read journal entry →
Indrani Infrastructure: Analyzing the Next.js E-Commerce Stress Test#004Advanced
Proj: Indrani Jewelers

Indrani Infrastructure: Analyzing the Next.js E-Commerce Stress Test

Testing your infrastructure under heavy concurrent load is critical for enterprise scale. Discover how the Indrani Jewelers platform achieved a zero percent failure rate during our rigorous Next.js e-commerce stress test.

Next.jsVercelPerformance Testing+1 more
Read journal entry →
One Shopify CDN Image Broke My Detection Engine#003Intermediate
Proj: Webshastraa Audit Tool

One Shopify CDN Image Broke My Detection Engine

A single Shopify CDN image completely fooled my custom website detection engine into returning a false positive. Discover why this Next.js debugging journey taught me that true architectural server signals must always mathematically outweigh weak third-party media assets in automated auditing tools.

Next.js 16TypeScriptNode.js+2 more
Read journal entry →
Why My Dashboard Felt Slow Even Though It Was Fast#002Intermediate
Proj: 143 Frangrance

Why My Dashboard Felt Slow Even Though It Was Fast

My Next.js dashboard loaded in 200ms, but users still complained it felt sluggish. Discover how swapping a generic global loading screen for a route-aware skeleton UI completely transformed the user experience and dramatically improved perceived performance.

Next.js 16ReactApp Router+2 more
Read journal entry →
Vercel Cron Job Limits: Debugging Silent Hobby Plan Build Fails#001Intermediate
Proj: Indrani Jewellers

Vercel Cron Job Limits: Debugging Silent Hobby Plan Build Fails

Vercel Hobby plans silently fail builds if you configure a cron job to run more frequently than once every 24 hours. Learn how to debug this hidden error and offload high-frequency tasks to secure external API triggers.

Next.js 16VercelVercel Cron Jobs+3 more
Read journal entry →