
Starting a New React Project in 2026-2027: The Stack I Keep Coming Back To
I was three weeks into a new client engagement — a mid-sized insurance company building a policy administration CRM from scratch. No legacy code, no i...

I was three weeks into a new client engagement — a mid-sized insurance company building a policy administration CRM from scratch. No legacy code, no i...

Six weeks into the insurance CRM project, we had a production incident. The backend team renamed a field — policy_number became policyNumber — as part...

At the insurance company, our React app started with a structure I still like for small projects. src/ api/ components/ hooks/ layouts/ pages/ types/ ...

The first serious error-handling conversation on the insurance CRM happened after a demo. We had built the policy detail page. It fetched the policy, ...

Three months into the insurance CRM, we had a page that felt haunted. The policy list would load. Then it would blink. Then it would refetch after swi...

The policy list bug started as a support ticket. An agent filtered policies by status, page, and renewal date. She copied the URL and sent it to anoth...

The policy builder did not look dangerous at first. It was "just a form." A few sections, some conditional fields, a Save Draft button, a final Submit...

The company had a legacy PHP application, and we were not brought in to rebuild it. We were brought in to add one module. One module. A self-contained...

Ask ten React developers how to style a component and you'll start a fight. Not a discussion. A fight. Tailwind people and CSS-in-JS people don't disa...