Practical, no-fluff writing on IT leadership, CRM & revenue plumbing, attribution, and AI automation — from someone who still ships the code.
15 posts · 4 categories · 23 tags
Your scale ceiling is an arithmetic result, not a feeling — throughput is concurrency over latency, and a CPU-bound box tops out at cores divided by CPU-seconds per request. Most systems fall over at a small fraction of that number because of coordination and copies, not because the machine is small.
A CRM is only as good as the data flowing into it. The interesting work is rarely the UI — it is the plumbing.
A model call is the slowest, priciest, least deterministic dependency in your whole system, so you ration it like an unreliable third-party API you call as rarely as you can. The practical skill is putting the model only where fuzzy understanding is genuinely required and doing the boring 80% with deterministic code you can test.
Before reaching for a bigger server, read the slow query log. It is the cheapest performance win you will ever get.
A spreadsheet quietly running part of the business is a production system with real users and a proven spec. You earn the right to replace it by matching its numbers exactly — bugs included — before you change a single thing.