Co-founder & CTO at Fcode Labs, where I lead engineering — including on Forevate. I write at techwithramesh.com about the part of the job that keeps proving hardest:

Writing the code was never the hard part. Deciding whether it's correct, safe, and worth shipping is — and that decision needs a contract: what has to stay true, what evidence counts as enough, and who is on the hook for the call.

AI made the writing fast. It did not make that decision easier, and on the teams I run it's usually what we run out of first. I don't think that's true of every team, and I'd rather be corrected than agreed with — if you've got a counterexample, I want to hear it.

• Writing about engineering judgment in the AI era. It mostly falls into three areas:

  • 🏗️ Build — architecture and production AI systems
  • ✅ Verify — review, security, governance, reliability
  • 🧭 Lead — productivity, hiring, accountability, team design

  Most of what I've published sits under Verify — that's the part I'm most sure of. Build and Lead are where I'm still working it out.

• Recent essays:

  • Does AI Make Developers More Productive? — the opening test: does AI improve end-to-end delivery, or just authoring?
  • Why Your Test Failed: Real Bug, Brittle Test, or Missing Contract — a red test is a disagreement, not a verdict
  • A CSP Nonce Is Never Just a Header — a security control is an invariant across rendering, caching, and failure modes
  • What a Vendor Security Questionnaire Actually Proves — and What It Can't — where security evidence holds and where it stops
  • Your Tests Pass. That Still Doesn't Tell You Whether to Ship. — introduces the verification-contract concept (from 2023 — it keeps coming back)

• Day job: shipping production AI systems — most of what I write started as a decision I had to make there.

• Programmer since forever; still enjoying it
• More code is not the same as more productivity
• 👨🏻‍💻 Programmer by day, programmer by night 😄
• PS: I love Skyrim. "I used to be an adventurer like you, then I took a programming lesson."

• 📚 Blog: techwithramesh.com
• 💼 LinkedIn: rameshx
• 🐦 X: @techwithramesh
• 📧 Email: ramesh@fcodelabs.com
• 💬 Stack Overflow: ramesh-x