LLMs

AI coding tools are genuinely great and genuinely dangerous, often in the same suggestion. They will write in thirty seconds something that would have taken you twenty minutes, and it will contain a subtle bug you would never have written yourself. Here is the workflow I actually use to get the speed without shipping the mistakes.

For a long time the comforting story about AI went like this: sure, it can crunch numbers and play chess, but it will never do the human things, the creative things, the intuitive things. That was the line, repeated confidently, for years. I want to gently point out that the line keeps moving, and it is moving in a direction that deserves more honesty than it usually gets.

When a model is not doing what you want, there are three levers people pull: better prompting, retrieval, or fine-tuning. They are wildly different in cost and effort, and teams reach for the expensive one far too early. Here is how to pick the right lever without burning your budget on the wrong one.

Every model has a default voice, and it is the same voice: smooth, agreeable, faintly corporate, allergic to a strong opinion. It is the tone of a brand apologizing. If you want AI to help you write without sounding like everyone else who uses AI, you have to actively drag it away from that default. Here is how.

Every month brings a new open model, and most are footnotes. GLM-5.2 is not. Z.ai released a 753-billion-parameter model, with a one-million-token context window, under a plain MIT license. That last part is what makes it matter.

Most AI bills are not big because the work is hard. They are big because of lazy defaults: the most expensive model on every task, the biggest context every time, and no thought about which jobs actually need the premium option. Here is how to spend far less without your results getting worse.

The single most dangerous thing about a good AI model is how convincing it sounds when it is wrong. It does not hedge, it does not sweat, it just states the confident falsehood in the same tone as the truth. Here is how to catch that before it costs you something, without turning every answer into a research project.

Every model launch comes with a chart where the new model is tallest. The charts are technically true and practically useless, because they are marketing wearing a lab coat. Here is how to read a benchmark like a skeptic, so a leaderboard never again talks you into the wrong model for your actual work.

Most prompt engineering advice is either obvious or superstition. You do not need a 2,000-word mega-prompt or a secret phrase that unlocks the model true power. You need to say what you want the way you would say it to a sharp, literal-minded colleague who has no context and will take you at your word.

For years the deal was simple: Microsoft paid, OpenAI built, and Copilot ran on someone else models. At Build 2026, Microsoft quietly changed the arrangement by shipping seven models of its own. The most important AI news of the month was not a benchmark. It was a message.

If you are new to this and trying to pick your first AI model, the internet will hand you forty benchmark charts and a headache. Ignore them. The right first model has almost nothing to do with leaderboard trivia and almost everything to do with what you are actually going to do. Here is the short, honest version.

RAG, retrieval-augmented generation, is one of those terms that sounds like it needs a PhD and actually describes something you could explain to a ten-year-old. Here is the plain version, why it matters, and the case, more common than the vendors admit, where you do not need it at all.

June and early July gave us a model release almost every day, which is exactly why you should not try to follow all of them. Most were incremental. A few will still matter next summer. Here is the month sorted the only way that is useful: by how long it will stay relevant.