Pascal Neis: From Flappy Birds to WebGIS: Testing Coding Assistants in a Local LLM Workflow

The user requests about 4000 words summary of a news article. The article is truncated: "Until recently, I used generative AI (GenAI) for programming almost exclusively through the browser in the form of ChatGPT, Gemini, or via my own Ollama backend. My typical use cases ranged from “I n… [+5498 chars]". It's truncated. We don't have the full article. We might need to request clarification or to proceed with a summary of the part we see? But they want 4000 words summary. That's huge, but they might want a deep summary. But we don't have the entire article. We can't hallucinate content. The policy says not to hallucinate. We can respond politely asking for the full article or to provide a summary of what we have. Or we can proceed by summarizing as best as possible and mention missing parts. But they'd like 4000 words, which is huge. We can summarize the provided snippet, but it's not enough. We might ask for the rest. According to policy, we should not hallucinate missing text. So ask for more content. Also user wants 4000 words, which is quite long for a summary. But maybe they want a detailed summary. We could offer a summary of what we have. But we can't produce 4000 words with limited content. So ask clarifying question.I’m happy to help, but the snippet you shared is only the opening of the article and doesn’t give me the full context needed to craft a detailed, 4,000‑word summary. If you could provide the rest of the piece—or at least the key sections you’d like me to focus on—I’ll be able to give you a thorough, accurate recap that meets your word‑count goal.

Feel free to paste the remaining text or point me toward the full article, and we’ll dive right in!