insights
From our engineers
Articles are written by the people who build the systems, not by a content team. The Briefing is compiled twice a week by our editorial pipeline: an AI writer, an AI fact-checking editor and a human review queue for anything the editor refuses. Every edition links its sources. How the Briefing is made
Articles and briefings
ARTICLE · AI Engineering
Ten questions to ask any vendor who promises you agents
ReadBRIEFING · SecurityA backdoored open model cost under $50 to build, researchers show
ReadBRIEFING · SecurityA backdoored Claude extension and an Auto Mode bypass, two months apart
ReadARTICLE · RustFive signs your estate needs a Rust core, and three it does not
ReadARTICLE · AI EngineeringHow we put a model in a pricing flow, inside bounds you set
ReadBRIEFING · SecurityEight eMudhra intermediates compromised: check your trust stores
ReadBRIEFING · Rusttsrs: a Rust port of TypeScript, and what to do about it
ReadBRIEFING · AI EngineeringDecision models arrive: what a CTO should test first
ReadARTICLE · AI EngineeringAI Business Logic Implementation: a definition, and why chatbots are not it
ReadARTICLE · RustThe memory-safety mandate: what the move to Rust means for your 2027 roadmap
ReadARTICLE · LeadershipKnowledge transfer is the wrong goal. Judgement is.
ReadARTICLE · ModernizationModernize in place: why we never recommend the big rewrite
ReadNothing in this category yet.
technology radar
Technology Radar
Our current view of what to adopt, trial, assess, and hold. Updated twice a year.
Edition 1 · November 2026 · 37 entries