Minghui (James) Wang · Senior AI Engineer

I’d rather show you the decisions than the logos.

Four systems I designed and built, written up the way I would in a design review: the problem, the constraint, what I chose, and what it cost. Pick a case.

✓ 1,487 tests on one live system✓ 11 AI platforms, built solo✓ 15-person team, built from zero
How I work

Five habits

  1. Read the business first. I learn how the owner, the partner or the teacher actually works before I design anything.
  2. Every AI output has an owner. If a person would be blamed for it, a person approves it.
  3. Test where it hurts. Money, children’s data and anything legal get the heaviest coverage.
  4. Assume the model will be down. FieldsBrain falls back to plain rules and keeps working.
  5. Keep the stack hireable. Laravel, MySQL and Redis outlive any one engineer, including me.
What I reach for

Stack, with reasons

  • Laravel + MySQL + Redis for products that have to run for years.
  • OpenAI-compatible providers, with Anthropic and Gemini behind the same interface, so the model can change without a rewrite.
  • Twilio and WhatsApp Cloud API for voice and messaging agents.
  • Stripe, storing tokens only, never card numbers.
  • Docker and Jenkins for repeatable releases.
Before I join a team

Questions I’d ask you

  • Which AI output in your product would hurt most if it were wrong, and who sees it first?
  • How do you find out when a model update changes behavior?
  • What does a new engineer ship in the first two weeks?
  • Where does your team want less AI, not more?