Agentic Engineering

As AI adoption accelerates, attacks such as prompt injection, jailbreaks, data poisoning, and agent exploitation are redefining cybersecurity. This book explains why these attacks work and provides practical strategies for building secure, resilient AI systems.

Most AI systems can talk, but few can actually do. This book shows you how to build AI agents that reliably use tools, call APIs and automate real workflows. Using DSPy, Pydantic AI, the Claude Agent SDK, the OpenAI Agents SDK and Google ADK, you'll learn practical patterns for building reliable agents that work in production.

AIエージェントの構築が、これほど容易だった時代はない。そして、実際に機能するものを作ることが、これほど難しい時代もない。本書は言語モデルの基礎から本番対応マルチエージェントシステムまで、失敗が起こる前に予測し、壊滅的な障害ではなく優雅な劣化を設計し、完全なアーキテクチャの所有権を確立するための深さをもって、あなたを導く。ペーパーバック版はamazonにて好評発売中。

A fundamental architectural manifesto on AI behavioral safety and the transition from "word generation" to "state synchronization." Stop building "smart calculators"—start building reliable environments.

The definitive guide to Windsurf — the AI IDE with both Cascade (interactive agent) and Devin (autonomous agent). Covers Supercomplete, Flows, .windsurfrules, large codebases, testing, Git, and the honest comparison with Cursor and Claude Code. 14 chapters.

"The AI confirmed X for me" used as proof of X. Outputs that sound brilliant but don't hold up to a severe re-reading. A three-page "AI policy" that nobody reads. Sound familiar? Thinking with LLMs, the Right Way is the system of critical thinking applied to LLMs: the Thinking-With Triangle (Intent / Adversary / Editor), the four meta-decisions of governance, the Socratic and adversarial practices for investigating and verifying. Not prompt engineering: the method for not letting yourself be mirrored.

Think The Phoenix Project or The Goal, but for the age of AI agents: a business novel that teaches a hard technical subject through story and humor, aimed at the people who have to make decisions about it, as well as people who are actively engaged in architecture and engineering.

This third edition covers Rust 1.85 and the Rust 2024 Edition in full. The new chapters on concurrency, the 2024 edition migration, GPU computing, Go integration, and Linux kernel programming show where the Rust community has moved since the second edition, and where systems programming as a discipline is heading. You might be writing your first Rust function or your hundredth production service, but I hope this book makes the language feel less like a puzzle and more like a tool you are already familiar with. That was the only goal I had when I wrote it.

AWS replaced Amazon Q with Kiro — an AI IDE that writes specs before code. 14 chapters covering spec-driven development, AI agents, hooks, MCP integrations, AWS deployment, and the honest comparison with Cursor and Copilot. The definitive guide.

The tech job market changed. Entry-level dropped 73%, AI screens resumes, interviews test system design. This is the no-BS guide: portfolio, resume, LinkedIn, interviews, negotiation, and your first 90 days. Written by someone who hires engineers.

Kubernetes exposes plenty of state, but operators still have to reconstruct operational meaning from scattered Pods, Services, EndpointSlices, Events, PVCs, owner references, and status fields. This ebook uses `kctx`, a small read-only Kubernetes context engine, to show how deterministic entities, relations, signals, graphs, namespace snapshots, CRD adapters, and stable JSON contracts can turn raw cluster data into reusable context for humans, tools, and AI agents. It is written for SREs, platform engineers, Kubernetes operators, infrastructure developers, and AI tooling builders who want better primitives than raw YAML and improvised troubleshooting pipelines.

92% of developers use AI daily. Entry-level jobs dropped 73%. This isn't a story about replacement — it's about transformation. Data-driven guide with a 30-day action plan for developers who want to thrive, not just survive.

Build defensible evaluation systems for Gen AI, RAG, agents and multimodal applications using datasets, metrics, release gates, monitoring and seven interactive labs.

A leader at a company opens Slack one morning. The brief their virtual employee wrote looks normal: same headers, same prose voice, same cadence as every other brief that week. The last line ends mid-sentence. The API returned `stop_reason: "max_tokens"`. The system shipped it anyway. No exception. No log line. No retry. That bug doesn't look like the normal kind. This book is about why, and what to build instead.