I Am Not a Developer
Thirty years in supply chain, no engineering background, and a platform running in production. The distinction that matters is not who writes the code.
I have never written a line of production code, and PreShiftIQ is a live platform serving five categories.
Both of those things are true, and I understand why the second one makes people skeptical of the first.
What exists today runs on Next.js and Vercel at the front, an Express and TypeScript service on Railway behind it, and Postgres underneath, with Clerk handling identity, Stripe handling payments, and Sentry watching for what breaks. There are five live categories, a few hundred tracked work items closed, and an append-only audit layer recording every scoring decision the engine makes.
I sold technology for years before I built any, so I was not starting from zero. I could say migration in a meeting and mean roughly the right thing. I knew what a webhook was. I could hold my own on a technical discovery call and follow most of what came back at me.
What I did not have was any operational understanding, and the distance between those two things turned out to be enormous.
Knowing what a migration is does not tell you to apply it locally first, verify it, then apply it to production, and never let it run automatically on deploy. Knowing what a webhook is does not help you when one silently stops firing, with no error, no log line, and nothing in the database to indicate that anything was ever attempted. Knowing what an environment variable does does not tell you that rotating a single credential means auditing every system that depends on it in the same sitting, because otherwise you have not fixed the problem, you have only moved it somewhere you are not looking.
That is the gap, and it is not a vocabulary gap. Vocabulary is what selling technology gives you. Operations is what being responsible for it gives you.
What I did bring was thirty years in supply chain, and a specific kind of knowledge that turns out to be far harder to acquire than any of the above.
I know how buyers actually decide, which is almost never how the process diagram says they decide. I know where implementations fail, and that it is rarely the thing that got the most attention during the demo. I know what vendors overstate, and which parts of a capability claim are load-bearing. I know which questions produce honest answers from an operator and which ones produce the answer they think you want to hear.
That knowledge is the input this product runs on, and everything else was learnable.
Gartner predicted that by 2024, 80% of technology products and services would be built by people who are not technology professionals. I originally read that as a forecast about tooling. I now read it as a forecast about who gets to build, and the answer is the people who understand a problem well enough to specify it correctly.
Truth is, it doesn't make me a developer or an engineer.
I could not sit down and write this platform from scratch, and there are corners of it I understand at the level of what it does rather than exactly how. What I can do is specify precisely, review every change before it lands, understand what each change does and why it was made, refuse the ones I cannot explain, and catch the ones that are wrong because I know what the output is supposed to look like when the system is behaving correctly. That last one is not a technical skill at all. It is domain knowledge doing the job that testing cannot do on its own, because a test only checks what someone thought to check.
The distinction that matters is not whether I write the code. It is whether I understand the system well enough to be accountable for it, and I do.
Which brings me to the objection I hear most often, and it is never "you could not have built that." It is "sure, but it must be a mess underneath."
Selecting supply chain technology?
PreShiftIQ matches buyers to vendors on measured fit across TMS, dock scheduling, ELD, carrier vetting, and fleet management. Vendors pay for outcomes, never for influence, and the buyer match is free.
See how matching works at preshiftiq.com/how-it-works.
Sources
- Gartner, low-code development technologies forecast, on technology products and services built by non-technology professionals by 2024.
Next in the series: it isn't spaghetti, and here is the discipline that keeps it from being so.
