AI Coding Tips — May 2026. Some observations from this past month. | by Raheel Yawar | Jun, 2026 | MediumSitemapOpen in appSign up<br>Sign in

Medium Logo

Get app<br>Write

Search

Sign up<br>Sign in

Mastodon

Member-only story

AI Coding Tips — May 2026

Raheel Yawar

2 min read·<br>1 hour ago

Listen

Share

Some observations from this past month.<br>Context<br>When building context docs (RAG, Skills, Rules, etc.), minimise the number of “don’t do this” examples. During long-running conversations, the LLM sometimes mixes up the DO’s and the DON’TS.<br>RAG, Skills, etc., are often ignored in favour of training data. As an example, if you’re making a web framework similar to React and providing data via RAG, Skills and Tools, there is a chance the agent will pattern match with React from its training and go with it.<br>This might make you consider using fine-tuning. This should be your last resort when using 3rd party models.<br>Should you use MCP or give the model console access? Do both.<br>Coding<br>Codex is great at code reviewing Claude Code’s output.<br>Claude Code’s code when fixing bugs can err towards the simple and least intrusive fix. You have to ask it to be thorough if you want the most stable fix.<br>The Agent gave you a couple of implementation options and its recommendation, and you have no idea what the best approach actually is? Ask it what the “unwanted consequences” would be so you can go into a deeper conversation with it.<br>LLMs are great at TypeScript but less good at languages like Rust. Niche languages like COBOL fare even worse.<br>GenAI<br>GenAI image generation remains bad. Use image…

Written by Raheel Yawar

70 followers<br>·55 following

Software Engineer, Game Developer and Author. https://linktr.ee/raheelyawar

Help

Status

About

Careers

Press

Blog

Privacy

Rules

Terms

Text to speech