AL Object ID Ninja

Zero-configuration, dead-simple, lightning fast, no-collision object ID assignment for multi-user repositories

From the blog

Your Object IDs Have No Excuse Now - Ninja Comes to CI/CD

AL Object ID Ninja is now available as a GitHub Action and an Azure DevOps Pipeline Task. It scans your AL repository during CI/CD and fails the build if it finds any object IDs, field IDs, or enum value IDs that aren't tracked by the Ninja backend. No more spreadsheets, no more "we'll coordinate manually", no more conflicts surfacing during deployment.

Multi-app repos and app pools are supported automatically.

Context Engineering - The Thing Almost Nobody Is Actually Talking About

Today I want to talk about something that barely anyone is talking about. Context engineering.

We hear about prompts constantly. We hear about the latest model releases, the agentic frameworks, the AI-powered IDEs, the MCP servers (luckily we don't hear about vibe coding all that much anymore). We hear about a lot of things. You name it - we hear about it.

But context engineering? Not so much.

And I find that strange, because if there is one lesson I have taken away from spending the past nine months writing code almost exclusively with AI agents (last six of which you can drop the "almost" word), it is this: context matters more than your prompt. Significantly more. Whenever my agents produced results that I could never match - faster, more consistent, undeniably better - every single time I could trace that back to one thing. Precise context.

That word, precise, is doing a lot of work in that sentence. Remember it.