What Changed When I Stopped Selling Hours
FeaturedHourly billing quietly punishes the engineer who gets faster. Moving Reivex to scoped outcomes changed how I estimate, how I write proposals, and which clients I say no to.
Ahad Nawaz
Writing
Engineering notes, project write-ups, and what I learned shipping them.
Hourly billing quietly punishes the engineer who gets faster. Moving Reivex to scoped outcomes changed how I estimate, how I write proposals, and which clients I say no to.
Ahad Nawaz
Running teams of up to fifteen developers taught me that the failure mode of a technical founder is not bad code. It is being the person every decision has to route through.
Ahad Nawaz
A technical buyer will not ask whether your code is elegant. They will ask what happens when you leave, how the data is structured, and whether anything is load bearing that should not be.
Ahad Nawaz
Architecture, prompt design, and the message queue that keeps a WhatsApp AI bot reliable. Why I picked Puppeteer over the official Cloud API, the rate-limiting strategy, and what broke at scale.
Ahad Nawaz
The engineering was the part I was ready for. Contracts, cash flow timing, handover documents, and knowing which work to refuse were not, and those are what actually determine whether a studio survives.
Ahad Nawaz
What I learned shipping the same ERP into 15+ companies: tenant isolation, schema-per-company versus shared, audit trails, the migration story, and the boring decisions that keep the system from melting.
Ahad Nawaz
Architecture, trade-offs, and the WebSocket layer that powers PowerSell's real-time leaderboards. Four portals, edge state sync, and the decisions that made a 35-day MVP possible.
Ahad Nawaz
Reproduce first, narrow the space, then fix. A simple mental model for tracking down bugs without endless printf and hope.
Ahad Nawaz
Sharing what you’re learning doesn’t mean performing. Notes, small wins, and honest “I don’t know yet” posts that actually help you and others.
Ahad Nawaz
Using AI for boilerplate, docs, and tricky syntax—without letting it drive architecture or replace understanding.
Ahad Nawaz
Rituals, tools, and boundaries that help when your office is your laptop and your team is async.
Ahad Nawaz
RESTful conventions, versioning, and error responses that make integrations and refactors less painful.
Ahad Nawaz
How to keep a shipped project from becoming a mess: docs, tests where they matter, and a simple rule for when to refactor.
Ahad Nawaz
Communication, scope, and the art of saying “not yet”: lessons from shipping real products for real users and stakeholders.
Ahad Nawaz
Strict mode, small interfaces, and a few type patterns that cut bugs and refactor pain without turning every file into a generic maze.
Ahad Nawaz
Concrete steps to take a side project from idea to production: scoping, boring tech, vertical slices, deploying early, and protecting time so you actually ship.
Ahad Nawaz
A no-BS walkthrough of why Next.js and Firebase power this site: SSR, static generation, Google Auth, Firestore for the blog, and how to keep it simple without a custom backend.
Ahad Nawaz