MSDEVBUILD Azure Money debited. Order failed. The payment worked. The webhook did not.
· Why a slow payment webhook loses orders after the money is taken · Why a webhook should save the event and answer 200 before doing any work · How a reconciliation timer finds payments whose webhook never arrived Azure · 10 steps · October 5, 2026
MSDEVBUILD Design Pattern Paid. Then sold out. The last room went to another site first.
· Why every booking site can sell the same last hotel room · Why you authorize a payment at Pay and capture it after the supplier confirms · What to do when the supplier does not answer at all Architecture · 10 steps · October 3, 2026
MSDEVBUILD Design Pattern One hotel. Three JSONs. Every hotel supplier speaks its own dialect.
· Why supplier JSON cannot be shown to travellers as it arrives · How one adapter per supplier and a canonical model fix prices and units · How a master hotel ID and a time budget fix duplicates and slow search Architecture · 10 steps · October 2, 2026
MSDEVBUILD Azure One tap. Two orders. A double tap charges the customer twice.
· Why a double tap or a retry after a timeout creates two orders · What an idempotency key is, and why the app has to create it · How a unique index in Azure SQL stops the duplicate, on any server Azure · 10 steps · October 1, 2026
MSDEVBUILD AI One feature. Fourteen agents. The handoffs are the workflow.
· How one agent’s question becomes the next agent’s input · Why a business rule must hold in every layer · How a Firestore rule can be wider than its comment AI · 9 steps · September 29, 2026
MSDEVBUILD Azure 1.6 million downloads. One photo. A flash sale turns the API into a file server.
· Why a flash sale sends the same image bytes from one server to every phone · How a CDN like Azure Front Door serves files from an edge location near each user · What never goes on a CDN, and why a changed image needs a new URL Azure · 10 steps · September 28, 2026
MSDEVBUILD Azure Security Your public API has no login — and no identity Browsing without signing in is the requirement. Trusting the header was the bug.
· An Origin or X-Client-App header is a string the caller chooses, so it authenticates a channel, not a caller. · A short-lived guest token gives an anonymous request a countable, expiring, revocable identity without any account behind it. · Rate-limit on the token subject rather than the IP: addresses rotate hourly on a proxy pool and a whole office shares one behind NAT. Azure · 8 steps · September 28, 2026
MSDEVBUILD AI 14 prompts pass. One never got checked. A hook on staged files never audits the past.
· Why refusal conditions matter more than instructions · Why a new hook misses files that already exist · When a rule belongs in AGENTS.md instead of a prompt AI · 9 steps · September 20, 2026
MSDEVBUILD Azure Six jobs. Six specialized models . Azure AI Foundry pairs each business problem — search, images, video, claims, calls — with the model actually built for it.
· Which Azure AI Foundry model fits which business problem — embeddings, image and video generation, vision, and speech. · Why semantic search beats keyword search for real customer questions. · How a multimodal model and speech models turn a photo or a phone call directly into structured, actionable data. Azure · 8 steps · September 17, 2026
MSDEVBUILD AI It looks like a heart. It says "button". Silent for the team. Loud for the user.
· Why unnamed buttons pass every code review · Why a script finds candidates and an agent confirms them · Why a sentence built from fragments cannot be translated AI · 9 steps · September 12, 2026
MSDEVBUILD copilot The 7 files Copilot reads Most devs have never opened half of them. Here's what each one actually does — and why it matters.
· copilot-instructions.md is auto-attached to every chat request — repo-wide, no reference needed · instructions/*.instructions.md scopes rules per path, skills/SKILL.md loads itself when your ask matches, and agents/*.agent.md (formerly chat modes) packages personas per task · mcp.json and copilot-setup-steps.yml extend Copilot into real tools and give the autonomous coding agent its own preinstalled sandbox GitHub Copilot · 9 steps · September 10, 2026
MSDEVBUILD AI Saved two hours. Cost four days. Licence risk compounds with time, not size.
· Why a dependency gets more expensive every week · How to find packages nobody imports · Why the licence check belongs in a hook AI · 9 steps · September 4, 2026
MSDEVBUILD AI The rule read fine. Any rider, any order. A review uses one identity. An attack needs two.
· Why a security finding needs an exploit path · Why Firestore rules need a second identity per role · How to rank credentials by blast radius AI · 9 steps · August 27, 2026
MSDEVBUILD AI Which backend is this build? Nobody knows. Code complete is not shipped.
· Why a build should say which backend it talks to · Why release notes from commits read like a diff · Why incident questions come before dashboards AI · 9 steps · August 24, 2026
MSDEVBUILD Azure Security Secure a Mobile API in 5 Steps In order. The order is most of the value.
· The five layers a mobile API needs, and what each one actually stops · Why authentication and authorization are two separate steps, not one · Why monitoring is last but is the step you will be glad you did Azure · Security · 8 steps · August 23, 2026
MSDEVBUILD Azure Security What Happens When You Tap Sign In The full login journey on a secure Azure app, step by step.
· Why a secure app hands the password to Entra ID and not to your API · What a signed token is and why verifying it needs no network call · Why there is no password left anywhere in the chain, including the database Azure · Security · 8 steps · August 22, 2026
MSDEVBUILD Azure Security Your Mobile App Is Leaking Its API Key It's hardcoded inside the app — anyone can unzip it and read it.
· Why an app package is public the moment you upload it to a store · Why a key inside the app is already leaked, before anyone looks · How Azure Key Vault behind your own API keeps the key off the phone Azure · Security · 8 steps · August 21, 2026
MSDEVBUILD Azure Security 5 Mobile App Security Vulnerabilities Found by a routine scan — nobody wrote any on purpose.
· The five findings a scan reports on almost every working mobile app · Why insecure storage and a disabled TLS check are leftovers, not bugs · Which of the five to fix first, and why it is not the one you expect Azure · Security · 8 steps · August 20, 2026
MSDEVBUILD Azure Security Insecure vs Secure: Same App, Two Builds The same mobile app on Azure, built two different ways.
· Why the insecure architecture ships first — it genuinely works · The six moments where the two designs stop behaving the same · Why the difference only shows up when something goes wrong Azure · Security · 8 steps · August 19, 2026
MSDEVBUILD Azure Security What Happens When You Hardcode an API Key Stealing it costs hours. Rotating it can cost days.
· Why a leaked key costs money long before anyone notices it leaked · Why rotating a hard-coded key kills every installed copy of your app · Why a secret in Azure Key Vault rotates with nobody updating anything Azure · Security · 8 steps · August 18, 2026
MSDEVBUILD Azure Security Hacker vs Azure: 5 Attacks, 5 Defences Each attack, matched to the Azure feature that stops it.
· Which Azure service stops which specific attack, by name · Why a valid token from a real user is still an attack you must block · Why "allow Azure services" is far broader than it sounds Azure · Security · 8 steps · August 17, 2026
MSDEVBUILD Azure Security How Azure Protects Your Mobile App The 5 layers standing between your app and the database.
· Why an app talking straight to a database is the bug, not a shortcut · Why authentication and authorization are two different checks, not one · Why a private endpoint means the database has no public address to attack Azure · Security · 8 steps · August 16, 2026
MSDEVBUILD Azure Security Azure Key Vault, Explained Properly The one secret most tutorials forget to remove.
· What Key Vault stores and how your app reads it at runtime · Why moving secrets to a vault leaves you one secret you did not expect · How a managed identity removes that last one so the count reaches zero Azure · Security · 8 steps · August 15, 2026
MSDEVBUILD Azure Security An AI Bot Is Attacking Your Login 8,000 password attempts a minute, while nobody's watching.
· Why an automated attacker changes the maths, not just the volume · Why watching your logs is not a defence against something that never sleeps · The three Azure controls that make speed useless: rate limits, lockout, alerts Azure · Security · 8 steps · August 14, 2026
MSDEVBUILD Azure A 118-character URL. 15 characters back. Designing a link shortener on Azure — and the one digit that decides whether you ever see your click stats.
· Why a link shortener is really two systems: one write, a thousand reads · How the short code is made, and what Cosmos DB does when two people roll the same one · Why the redirect must be 302 and not 301, and why Front Door answers most clicks Azure · Architecture · 13 steps · August 13, 2026
MSDEVBUILD Azure A million taps a second. One tiny message. 25 million people tapping 🔥 at the same moment — and not one of those taps is ever delivered to anyone.
· The live-reactions use case in four steps — what the app actually owes every viewer · Why sending every reaction to every viewer is impossible, in one line of maths · The five Azure services that count instead — Front Door, Container Apps, Event Hubs, Stream Analytics, Web PubSub Azure · Architecture · 14 steps · August 12, 2026
MSDEVBUILD Azure One line of code. Seven stops. What really happens between await http.GetAsync(...) and the JSON landing back in your app.
· The seven stops every HTTP call to an Azure API makes, and what each one costs · Why the first call is slow: 100 of the 160 ms is DNS and the TLS handshake, before your code runs · Why new HttpClient() in a loop pays that cost forever, and IHttpClientFactory pays it once Azure · Architecture · 13 steps · August 11, 2026
MSDEVBUILD Azure The queue was in order. Your workers were not. A customer paid $120 for an item they removed, and Service Bus did nothing wrong.
· That FIFO delivery and FIFO processing are different things, and concurrency is what separates them · Why SessionId is a partition-key choice, not a yes/no on ordering · The one setting that silently gives back the race after you enable sessions Azure · Messaging · 12 steps · August 11, 2026
MSDEVBUILD Azure Why Your AI Agent's Token Bill Exploded Nothing failed. The loop just paid for its own history, twelve times per task.
· Why an agent loop’s input tokens grow with the square of its step count · What prompt caching actually charges — reads at 0.1×, writes at 1.25× · The one line that silently stops the cache being read, with no error Azure · AI · 12 steps · August 10, 2026
MSDEVBUILD Azure You tapped View Product. Five Azure services answer before the page paints. Here is the order they run in.
· Why the edge answers first and your API never hears about a cache hit · What cache-aside actually does on a Redis miss, including the write-back · Why product images take a different path and never reach your API Azure · Architecture · 12 steps · August 10, 2026
MSDEVBUILD AI 93 green tests. The rule never ran. Tests written from the code agree with the code.
· Why a green suite can skip the rule that matters · How a testing agent writes tests that can fail · What a UI state matrix finds that review does not AI · 9 steps · August 9, 2026
MSDEVBUILD Azure A rack just lost power. The shop kept selling. Why Azure places your VMs on different physical racks, and what breaks the moment it does not.
· What a rack shares — one power feed, one switch, one blast radius · How an availability set spreads VMs across fault domains for you · Why two VMs in the same fault domain is not redundancy Azure · Basics · 16 steps · August 8, 2026
MSDEVBUILD Azure Azure is rebooting your server. Nobody notices. How an Azure Availability Set keeps an online shop selling straight through planned server maintenance.
· Why one VM cannot survive Azure patching the host under it · How an availability set spreads VMs across fault and update domains · What the load balancer health probe does during a reboot Azure · Basics · 14 steps · August 7, 2026
MSDEVBUILD Azure The outage lasted 18 minutes. Your retries lasted 4 seconds. 720 good orders in the dead-letter queue, and not one of them was poison.
· Why ten redeliveries take about four seconds, not four minutes · That MaxDeliveryCount caps attempts and says nothing at all about time · How to build the backoff Service Bus does not give you, with ScheduledEnqueueTimeUtc Azure · Messaging · 12 steps · August 7, 2026
MSDEVBUILD Azure One server goes down. Nobody can buy anything. How Azure Availability Zones keep an Amazon-scale shopping app online while an entire datacenter fails.
· What a single-server outage actually costs a shopping app · How three zones in one region are physically separate buildings · Why sub-2 ms replication turns 99.9% into 99.99% Azure · Basics · 10 steps · August 6, 2026
MSDEVBUILD Azure Azure rebooted the server. The bank never noticed. How update domains let Microsoft patch the hosts under your VMs without dropping a single customer.
· How Azure reboots hosts one update domain at a time · Why the load balancer always has a healthy VM to use · Update domain versus fault domain, in one line Azure · Basics · 16 steps · August 5, 2026
MSDEVBUILD Azure What is MCP ? Model Context Protocol — how an AI assistant reaches GitHub, your database, your files and Slack.
· Why a model on its own cannot reach GitHub, SQL or Slack · How an MCP client and server carry one request down and back · Why M + N connectors beats M × N bespoke integrations Azure · AI · 8 steps · August 4, 2026
MSDEVBUILD copilot LLMs have no memory So how does Copilot know your code? It never remembers. It re-reads, re-ranks and re-sends your context on every single request.
· Why the model holds nothing between two requests · How your editor rebuilds the whole prompt every time · What competes for the same fixed token budget GitHub Copilot · 9 steps · August 4, 2026
MSDEVBUILD Azure From a model to a shipped AI product Azure AI Foundry is the platform Microsoft built for the part everyone underestimates — everything after the demo.
· Why the demo works and the product still does not ship · How one Foundry project holds the model, your data and the agent · What to evaluate and filter before a release, not after Azure · AI · 8 steps · August 3, 2026
MSDEVBUILD Azure Your Durable Function runs many times The orchestrator body re-executes from line one, over and over, until every step is answered.
· Why an orchestrator body re-executes from line one, many times · How completed activities are answered from the event history · Why DateTime.Now and Guid.NewGuid break a Durable Function Azure · Messaging · 8 steps · August 2, 2026
MSDEVBUILD Design Pattern Netflix does not stream from Netflix The video you watch tonight is already sitting inside your internet provider.
· Why the video almost never comes from Netflix’s own datacentres · How the control plane answers play with a ranked manifest · How Open Connect boxes inside your ISP are filled overnight Architecture · 8 steps · August 1, 2026
MSDEVBUILD AI The screen got reviewed. The rule did not. One agent, one wide diff, one reviewer.
· Why a wide diff gets reviewed only where the reviewer looks · Why a role check in Firestore rules is not ownership · Why a count over a streamed collection is a bill AI · 9 steps · July 31, 2026
MSDEVBUILD Python In Python, a name is a sticker , not a box Two names can sit on one object. Whether it can change is what makes lists and strings behave differently.
· Why b = a is a second name, not a copy · Which Python types change in place and which are replaced · How the mutable default argument bug gets written Programming · 8 steps · July 30, 2026
MSDEVBUILD AI "Users can cancel an order." Six words. The hole they left sat in the code for months.
· Why a one-line requirement hides its hardest question · Why a business rule in a screen protects only that screen · How an ADR and a hook make a decision stick AI · 9 steps · July 26, 2026
MSDEVBUILD AI Code done in week 9. Shipped in week 14. Not one of those five weeks was code.
· Why a fast coding agent moves the bottleneck · When a job should be a hook instead of an agent · Which four agents to build first AI · 9 steps · July 17, 2026
MSDEVBUILD Azure Nine tools. Time to split. Route by role in code, not by a model.
· When one agent is no longer enough · Why routing by role belongs in code · What handoff costs Azure · 9 steps · July 9, 2026
MSDEVBUILD Azure Function tool or MCP? Count the consumers. One consumer: function tool. Two: MCP.
· How MCP differs from a function tool · Why approval matters for remote servers · When MCP is not worth it Azure · 9 steps · July 3, 2026
MSDEVBUILD Azure A call needs both people free. A message does not. Sync versus async, decided by one question — and priced honestly.
· How three chained dependencies become your own downtime · Why going async turns an outage into lag instead · The three jobs you inherit the moment you queue it Azure · Messaging · 10 steps · July 2, 2026
MSDEVBUILD Azure Two Azure queues. Which one do you pick? Five questions that settle it, and the one where the cheap option wins.
· The five questions that decide which Azure queue you need · Where Queue Storage stops: no topics, no sessions, 64 KB · Why the cheap queue is the right call for most background work Azure · Messaging · 10 steps · July 1, 2026
MSDEVBUILD Azure Somebody said “we need Kafka”. A broker and a log are not two brands of the same thing.
· The real difference between a broker and an append-only log · Why Kafka partitions put a ceiling on your consumer count · When the Event Hubs Kafka endpoint is the cheaper answer Azure · Messaging · 10 steps · June 30, 2026
MSDEVBUILD Azure The sale opened. The orders vanished. What a queue actually does to a traffic spike your server cannot absorb.
· What a flash sale does to an order API with nothing in front of it · How a queue decouples arrival rate from processing rate · Why an uncompleted message comes back without a retry loop Azure · Messaging · 10 steps · June 29, 2026
MSDEVBUILD Azure The gateway timed out. Where did the payment go? Retries, delivery counts and the queue Azure fills for you whether you read it or not.
· Why you never complete a message you cannot confirm · How delivery count and MaxDeliveryCount stop an endless retry · What lands in the dead-letter queue, and what to alert on Azure · Messaging · 10 steps · June 28, 2026
MSDEVBUILD Azure Azure Relay: No Inbound Ports Needed How the cloud reaches a server it is not allowed to connect to.
· How the cloud reaches an on-prem service with no inbound port · Why the private side dials out to a rendezvous point instead · When Relay beats a VPN, and when a queue beats both Azure · Messaging · 10 steps · June 27, 2026
MSDEVBUILD Azure You picked the topic. Then it filled up. Five Service Bus traps that only show themselves six months later.
· How the $Default rule keeps matching everything you filtered · Why one idle subscription fills the topic and pages the publisher · The five settings that prevent all of it, none of them code Azure · Messaging · 10 steps · June 26, 2026
MSDEVBUILD Azure The upload froze the app for 8 seconds. The fix is the cheapest queue Azure sells, and a pointer instead of a payload.
· Why image processing inside the request exhausts the web tier · The claim check: put a blob path on the queue, not the file · How visibility timeout and DequeueCount handle a dead worker Azure · Messaging · 10 steps · June 25, 2026
MSDEVBUILD Azure Three teams. One queue. Everyone missed messages. A queue is a DM. A topic is the group broadcast. The difference is a real bug.
· Why three teams on one queue each get a third of the messages · How competing consumers differ from real subscribers · What a subscription gives you that a second reader never will Azure · Messaging · 10 steps · June 24, 2026
MSDEVBUILD Azure Azure Notification Hubs: One Push, a Million Phones Why looping over device tokens yourself is the answer that fails the interview.
· Why a loop over a million device tokens finishes too late · How one send becomes APNs, FCM and WNS payloads · How tag targeting replaces holding device tokens yourself Azure · Messaging · 10 steps · June 23, 2026
MSDEVBUILD Azure 15,000 GPS pings a second. Do not put that in a queue. Partitions, offsets and the reason four teams can read the same event.
· Why a queue cannot hand the same event to four teams · How a partition key keeps one driver’s pings in order · How consumer groups and offsets let a slow reader catch up Azure · Messaging · 10 steps · June 22, 2026
MSDEVBUILD Azure Assert the tool. Not the prose. Model wording changes every run.
· Why prose assertions flake · What a recording executor checks · Where agent cost really goes Azure · 9 steps · June 21, 2026
MSDEVBUILD Azure Six seconds. Then under one. Streaming does not make it faster.
· What streaming changes and what it does not · How tool rounds fit a streaming loop · How Flutter should read SSE Azure · 9 steps · June 15, 2026
MSDEVBUILD Azure Four to nine seconds. Name the step. A spinner that long feels broken.
· How long an agent turn really takes · Why a named step beats a spinner · Why writes need a real button Azure · 9 steps · June 7, 2026
MSDEVBUILD Azure Firebase token in. No secret anywhere. Validate the token. Deploy with a managed identity.
· How to validate a Firebase ID token in .NET · Where roles must come from · How a managed identity removes secrets Azure · 9 steps · May 30, 2026
MSDEVBUILD Azure No user ID in any tool. The model can only pass what you let it.
· How prompt injection arrives through tool output · Why identity must never be a tool parameter · Where role checks belong Azure · 9 steps · May 23, 2026
MSDEVBUILD Azure Event Grid vs Event Hubs One is a doorbell. The other is a tape you can rewind.
· The doorbell-or-tape question that settles which one you need · Push with retries versus pull with offsets and retention · Why a real pipeline usually ends up using both Azure · Messaging · 10 steps · May 22, 2026
MSDEVBUILD Azure One order. Four teams need to know. Why the fourth subscriber is the only argument for Event Grid that matters.
· Why checkout should not call email, stock and shipping itself · How subscriptions and filters fan one event out to four teams · What Event Grid retries before a delivery is dead-lettered Azure · Messaging · 10 steps · May 21, 2026
MSDEVBUILD Azure The queue drained. Nothing was consuming it. One Service Bus default, six hours, and 4,318 orders that never existed.
· How a message TTL deletes orders with no error and no log line · Why a queue draining with no consumer is deletion, not recovery · The three queue properties and one alert that would have caught it Azure · Messaging · 10 steps · May 20, 2026
MSDEVBUILD Azure Tool descriptions are routing. Say when a tool does not apply.
· Why descriptions decide which tool runs · How the run loop works · Why a round cap matters Azure · 9 steps · May 14, 2026
MSDEVBUILD Azure Your first agent. In code. The portal cannot edit function tools.
· The setup steps in order · Why RBAC comes before code · Why the agent belongs in source control Azure · 9 steps · May 6, 2026
MSDEVBUILD Azure Build the URL before the agent. If Postman fails, the agent will too.
· Why the API comes before the agent · What the agent actually does in a call · Why a wrong URL looks like an AI bug Azure · 9 steps · April 28, 2026
MSDEVBUILD Azure "Spicy food under RM20." Zero results. Seventeen matching dishes were in the catalogue.
· Why keyword search fails a sentence · What an AI agent is underneath · Why the API stays the trust boundary Azure · 9 steps · April 20, 2026
MSDEVBUILD copilot Twenty messages. 91% of the month. The question was never the expensive part.
· What a token is, and why it is not a word · What really gets counted in one Copilot chat turn · Why a long thread costs far more than short ones GitHub Copilot · 9 steps · April 12, 2026
MSDEVBUILD copilot One bug. 212,000 tokens. The cost is the conversation, not the prompt.
· Why a long chat with files attached costs so much · How selecting and naming a symbol shrinks the context · Why a diff beats a rewritten file GitHub Copilot · 9 steps · April 4, 2026
MSDEVBUILD copilot Day nine. 61% gone. The tier you choose sets the cost.
· What a 400,000-token month means per day · Why an agent thread with files pinned is so expensive · How to route a task to the cheapest tier that can do it GitHub Copilot · 9 steps · March 27, 2026
MSDEVBUILD copilot The model read the rule. It moved on. Instructions ask. Hooks enforce.
· Why an instruction can be weighed and dropped by the model · What a preToolUse hook is and where it runs · How to write a guard script that exits 1 to deny GitHub Copilot · 9 steps · March 19, 2026
MSDEVBUILD copilot Eleven files. "fixes stuff". The diff shows what. Only you know why.
· Why a PR summary that restates the diff wastes review time · What Copilot can draft and what only the author can write · How to point the reviewer at the risky line first GitHub Copilot · 9 steps · March 10, 2026
MSDEVBUILD copilot All green. Still wrong. AI reviews how code is written, not whether it is right.
· What an AI review Skill reliably catches · Why a clean, tested pull request can still be wrong · Where the human reviewer still has to decide GitHub Copilot · 9 steps · March 2, 2026
MSDEVBUILD copilot Correct. Deployable. Quietly expensive. Copilot writes the convenient Azure, not yours.
· Why Copilot leaves public access on and keys in the output · How a Skill makes the secure, cheap choice the default · Where a Skill sits next to Azure Policy and Resource Graph GitHub Copilot · 9 steps · February 22, 2026
MSDEVBUILD copilot Firestore. Inside build(). Copilot writes the common Flutter shape, not yours.
· Why Copilot calls Firestore inside a Flutter build() method · Why a Skill description is its activation trigger · How a Skill produces a repository, a Cubit and a bloc_test GitHub Copilot · 9 steps · February 14, 2026
MSDEVBUILD copilot The whole feature. In the controller. Copilot writes the common shape, not yours.
· Why Copilot puts business logic in ASP.NET controllers · Why a Skill description is its activation trigger · How rules, a workflow and a checklist produce a thin controller GitHub Copilot · 9 steps · February 6, 2026
MSDEVBUILD copilot Every request paid for one method. Instructions are always on. Skills load on demand.
· Why a method in the instructions file costs every request · How Copilot reads only a Skill description until a task matches · Why the description is the trigger GitHub Copilot · 9 steps · January 29, 2026
MSDEVBUILD copilot The draft is true. It is not enough. /init describes the code. It decides nothing.
· What Copilot /init gets right when it drafts AGENTS.md · Which sections only a person can write · How to audit an AGENTS.md file in five grep lines GitHub Copilot · 9 steps · January 21, 2026
MSDEVBUILD copilot Three agents. Three conventions. One feature, built three ways in one sprint.
· Why every AI coding agent starts each session from zero · How one AGENTS.md file gives every tool the same rules · How Claude Code reads it through CLAUDE.md GitHub Copilot · 9 steps · January 13, 2026
MSDEVBUILD copilot 14 review comments. 11 were conventions. Copilot guessed. Nothing told it otherwise.
· Why Copilot picks the most common pattern, not yours · How to count convention mistakes in a pull request · Which lines in copilot-instructions.md carry the weight GitHub Copilot · 9 steps · January 5, 2026
Nothing matches that. Try a different term, or clear the category filter.
