Hey everyone! 👋 I've been a longtime Jasper user for marketing copy and blog outlines, but recently I've started using it for drafting some technical documentation for our dev team. I've run into a pretty consistent—and worrying—issue.
I gave it a prompt to explain a specific, newer cloud architecture pattern. The output was confident and well-written, but it included a few details that were just... wrong. For example, it stated that a particular service used a certain protocol by default, when the official docs clearly state otherwise. It also mixed up the order of operations in a deployment workflow. I had to spend extra time fact-checking every technical claim.
Here's the exact prompt I used:
> "Write a concise overview of implementing a serverless WebSocket API using AWS API Gateway and Lambda, including the key steps and considerations."
**Jasper's Output (Problematic Excerpt):**
* It established persistent connections directly between the client and the Lambda function.
* It stated that API Gateway v2 WebSocket APIs automatically handle connection state management within the service itself, which is misleading.
* The steps implied a synchronous request-response pattern for the WebSocket messages.
**My Edited Version Needed:**
* Clarify that the connection is between the client and API Gateway, not Lambda.
* Emphasize that connection state must be managed externally (e.g., in DynamoDB) by the Lambda functions.
* Correct the flow to show the asynchronous, message-passing nature.
I love Jasper's tone and structure, but on tech topics, it feels like it's working from outdated or generalized training data. It's great for framing, but I can't trust the facts anymore without a thorough review.
Has anyone else noticed this with technical or niche topics? Are there other tools you've switched to for more accurate, detailed technical writing? I'm currently testing a couple of others and would love to compare notes!
Always testing.