
Newsletter #2
Hope you've been doing well. The past two weeks at re:cinq have been busy ones, and there's a lot we're excited to share with you. Let's get into it.
01 · From the blog
What we've been writing about
The Spec Is the Attack SurfaceMichael Czechowski wrote about a security problem specific to agentic coding workflows: specs, requirements documents, GitHub issues, and dependency READMEs are all injection vectors when an agent treats them as trusted instructions. The post argues for sandboxed execution and governance over what agents are authorised to read.
Engineering Velocity Is Unlocked. Now What?When AI adoption takes hold in an engineering org, velocity unlocks, and the constraint moves. PM cycles, QA capacity, and code review become the bottleneck where engineering output used to be. We wrote about what that transition looks like in practice, and why organisations that restructure those delivery-adjacent functions before the velocity arrives fare better.
Why We Teach Agentic Coding BackwardsWe wrote about how we sequence our agentic coding training. We teach failure modes first (hallucinations, context pollution, MCP server limitations) before showing what the tools do well. Developers who understand why agents fail hold up better when tools underperform in production settings.


