Joining an AI startup while my social circle actively despises
The Gap Between Hype and Deployment
The biggest friction point is that my friends see the polished, marketed version of AI—the "magic" button that does everything. In reality, building an AI workflow is mostly about fighting with hallucinations and refining prompt engineering to stop the model from confidently lying about a basic API call. When they say "AI is fake," they're reacting to the marketing; when I say "this is hard," I'm talking about the actual deployment.
The real work isn't just asking a chatbot to write a poem; it's building a system where the LLM agent can reliably execute a task without breaking the entire pipeline. I've spent more time on error handling and output validation than I have on the actual "intelligence" part of the app. If you're trying to build a real-world application, you quickly learn that the model is only 20% of the battle—the other 80% is the orchestration layer.
What Actually Works in Production
For anyone trying to move past the "chatbot" phase, I've found that a few specific patterns actually hold up under pressure:
- Strict Output Formatting: Using Pydantic or JSON mode is non-negotiable. If the model doesn't return a parseable format, your backend crashes.
- Few-Shot Prompting: Providing 3-5 high-quality examples in the prompt is worth more than 1,000 words of instructions.
- Chain-of-Thought: Forcing the model to "think" in a hidden scratchpad before giving the final answer reduces logic errors by a huge margin.
Dealing with the Skepticism
The irony is that the people who hate AI the most are often the ones who would benefit from a better AI workflow. They hate the bad AI—the clunky interfaces and the generic corporate speak. But once you show them a tool that actually solves a specific, boring pain point without the "AI fluff," the conversation changes.
I've stopped trying to convince them that "AI will change the world" because that sounds like a pitch deck. Instead, I show them a specific script that automated a three-hour manual data entry task into ten seconds. That's the only way to bridge the gap. The transition from "this is a toy" to "this is a tool" happens the moment the utility outweighs the novelty.