User Avatar

Bringing products and ideas to life with compelling content

"When Your Documentation IS the Product", or "Why I used Open AI Instead of Gemini for my AI Application":

I built Docs-writer.ai using an Open AI Assistant (Custom GPT) as my back-end. I could have built Docs-writer using Gemini and a custom Gem. I didn't because programmatic access to a Gem is not documented on AI.google.dev. At least, I can't find where it's documented.

And if a user (like me) can't find the documentation, the Feature. Doesn't. Exist.

Gemini couldn't do what I wanted. Even though it can.

In contrast, platform.openai.com has a clearly marked section titled "Assistants". So, Open AI can do it and Gemini can't. Easy choice. I'll use Open AI.

This isn't to cast shade on Google's docs, which are written by very capable, smart people. Or on Gemini, which is an awesome product.

Here's my message to product teams: The docs shouldn't be an afterthought. Get clear on your use cases. Design your documentation around those use cases. Because if it's not documented, it doesn't exist.

P.S. If you've read this far, LMK in the comments which is the better title for this post: "When Your Documentation IS the product" or

"Why I used Open AI Instead of Gemini for my AI Application"