The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Why LLMs shouldn't handle your math (and other #whennotai moments)
The "AI hype" makes people think LLMs are a silver bullet. They aren't. As an architect, my job is often to tell clients where NOT to use AI.
Don't use LLMs for:
1. Deterministic Logic: If it can be solved with a simple IF/ELSE or Regex - don't waste tokens.
2. Basic Math: LLMs are probabilistic, not logical. Use a code-execution layer instead.
3. High-Security Static Data: Don't feed private keys or static configs into a prompt. Use a vault.
I build hybrid systems: AI for intent and unstructured data, traditional robust code for the "heavy lifting". That’s how you get 99% reliability.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Turning complex AI workflows into a calm, monochrome experience, brought to life with motion. We'd love to hear your thoughts!
Then: 1 month, 1 template.
Now: 1 week, 15 templates.
Same designer, different workflow.
I wrote up how I built no-code.supply: fifteen website templates, each with its own brand, in HTML and React, and some in Framer too. Claude Code did most of the typing. I did the directing.
no-code.supply
How I built 15 website templates with an AI coding agent in a week
How I built 15 AI-ready website templates with Claude Code in a week: the workflow, the quality bar, and why a template is only the starting point.
Going from one template a month to fifteen a week is wild. How much of the design direction did you still do by hand?
An AI-built app can work perfectly while any stranger can read its customers' data. Nothing on screen shows it.
Ask whoever built it: which tables hold user data, and what stops a logged-out stranger from reading each one? A good answer is a list. "It should be fine" means nobody has checked.
Andrés, this is the check most founders never run, because nothing breaks until someone looks. Asking for the list of tables and who can read each one is a test any owner can do without writing code. Row level access belongs on the launch checklist, not the cleanup list.
