{"slug": "what-is-ai-good-at", "title": "What is AI good at?", "summary": "AI excels at coding because most programming involves pattern reuse and has tight feedback loops, while it struggles with writing that requires original ideas and subjective judgment. The key factor is whether a task applies established patterns or depends on a novel viewpoint, with AI being useful for pattern-based work like documentation and routine emails but not for creative or taste-driven tasks.", "body_md": "AI is great at coding and mediocre at writing for the same reason: most useful code is really about pattern reuse and most *good* writing is not.\n\nAt first, this might seem backwards. Both code and essays are just text, but code has to follow exact rules while an essay can be written countless ways. You might expect a language model to be better at the less constrained task. In practice, those constraints are actually part of what makes coding easier for AI.\n\nI've been thinking about this quite a bit since this tweet, so I figured I'd put some thoughts on paper (keyboard?).\n\nCoding and writing require very different things.\n\n### Why AI is so good at coding\n\nThe biggest difference is that most programming does not require a new idea. Building an auth flow, a settings page, or an API endpoint is usually applying patterns that thousands of developers have applied before. Sure, the details change, but much of the implementation is familiar. That is exactly the kind of work AI is good at: recognizing a pattern, adapting it to the situation, and producing a working solution.\n\nCode also has a much tighter feedback loop, giving AI/agents an immediate way to validate their work. It either compiles or it doesn't. Tests pass or fail. Types line up or they don't. An AI can write some code, check the result, and correct itself. The space of possible solutions is large, but at least boundaries are visible.\n\n### It's not really \"coding versus writing\"\n\nGood writing is different. A good essay has to do more than assemble ideas into polished sentences. It needs an idea of its own - or at least a familiar idea seen from a perspective that makes the reader reconsider it. The writer's job is both to find that point of view and communicate it to the reader: to make a connection others missed, develop an argument worth considering, or turn an experience into an insight.\n\nThere is no test suite for that. A paragraph can be grammatically perfect, logically coherent, and still completely uninteresting. This is why AI writing often feels so average. Average code can be useful in many tasks. It just needs to follow conventions, handle the common cases, and ultimately get a job done. But average writing is usually the writing we skip.\n\nThe distinction is not really coding versus writing, though. It is work that applies established patterns versus work that depends on a viewpoint or new idea.\n\nAI *can* be very good at writing when the writing is mostly about applying patterns or logic: release notes, documentation, status updates, summaries, and routine emails. In those cases, originality may even be a liability. The goal is to communicate known information clearly, where introducing new ideas can actually be detrimental.\n\nAnd AI can struggle with coding when the work is not about building blocks: choosing an architecture with uncommon constraints, coming up with a new algorithm, or making a judgment call where information is limited. Those tasks require taste, lots of context, or a genuinely new approach.\n\n### A better way to judge a task\n\nKnowing this gives us a better way to decide what kinds of questions to ask AI. Instead of bucketing your task as \"writing\", \"coding\", \"design\", \"research\", etc., ask yourself what a good answer *requires*.\n\nDoes it require finding and applying a well-established pattern? Does it have unique constraints that are unlikely to be encountered elsewhere? Can the result be easily checked with a test, a trusted source, a calculation, or some other metric? If so, AI is likely to be useful.\n\nOn the other hand, if it requires taking a position, deciding what matters, or creating something whose value depends on taste, there is no clear feedback beyond \"what feels right\". Sure, AI may still help you think through a problem, but it should not be the one making the final call.\n\nYou can apply this filter almost anywhere. AI can summarize a legal document more reliably than it can invent a novel legal argument. It can build a page from an existing design system more reliably than it can create a brand from scratch (or at least one worth copying). It can compare logical options (well, [not all the time](https://x.com/ItakGol/status/2022317097477407103)) more reliably than it can decide the amount of risk your company should take.\n\nOn the other side, boundaries are rarely absolute. AI can occasionally produce an original connection, and people do plenty of formulaic writing. But this mental model is useful because it predicts where AI will be dependable and where it will need more supervision.\n\nThe right question is not necessarily \"Can AI do this?\". It is, \"What *kind* of work does this task actually require?\".>mg", "url": "https://wpnews.pro/news/what-is-ai-good-at", "canonical_source": "https://unstack.io/what-is-ai-good-at", "published_at": "2026-07-18 05:02:29+00:00", "updated_at": "2026-07-18 05:22:35.380071+00:00", "lang": "en", "topics": ["artificial-intelligence", "large-language-models", "ai-tools"], "entities": [], "alternates": {"html": "https://wpnews.pro/news/what-is-ai-good-at", "markdown": "https://wpnews.pro/news/what-is-ai-good-at.md", "text": "https://wpnews.pro/news/what-is-ai-good-at.txt", "jsonld": "https://wpnews.pro/news/what-is-ai-good-at.jsonld"}}