Books

As the digital economy changes the rules of the game for enterprises, the role of architects also changes. Rather than focus on software architecture alone, they must connect the penthouse, where the business strategy is set, and the engine room, where the enabling technology is implemented. Learn how to ride this Architect Elevator!

Most iOS interview books teach you the answer. This one shows you what a senior sounds like giving it: three versions of every answer, candidate, senior, and staff, side by side, so you can see the gap between correct and hired. 178 questions across six career levels, each with the follow-up that decides it and the red flag that ends the loop.

Documentation format explains 10 to 127 times more variance in AI-generated code than model choice. We ran 21,462 tests to prove it. This book shows you which formats work, which ones break, and why the industry standard is the worst option for AI consumption.

The EV charging industry sits at the collision point of transport, energy, and technology, and it's growing faster than most people inside it can keep up with. This book takes you from "I know EVs exist" to "I understand how this industry actually works." Covering everything from charging fundamentals and protocols to smart charging, cybersecurity, and vehicle-to-grid, it's the book the author wished existed when he first entered the industry in 2017.

This book is meant to take you on a journey of the future. A brief, small book teaching you technologies that go beyond the traditional blockchain. Get introduced to the future today!

Software teams are building faster than ever, but scaling engineering takes more than great code. This book shows how to create developer platforms that simplify delivery, support cloud-native systems and prepare organizations for the demands of AI. Practical, technical and grounded in real-world experience.

The most technically brilliant QA engineer is ineffective if nobody listens. Bug diplomacy, blocking a release, and talking to executives.

모든 크립토 채널에는 같은 다급한 경고가 고정되어 있습니다. "운영진은 절대 먼저 DM을 보내지 않습니다." 이 책은 그 한 줄 뒤에 숨은 스캠 경제의 필드 가이드입니다. 사칭 관리자, 딥페이크로 만들어진 창업자, 피그 부처링, 통째로 합성된 커뮤니티까지 — 스팸에서 크립토, 그리고 AI로 이어지는 세 시대를 가로질러 추적하고, 이 모든 것을 끝낼 단 하나의 질문에 도달합니다. 지금 이 방에 누가 있는가?

Behind every secure network lies an unbreakable mathematical truth. 'The Guardian Algorithms' bridges the gap between pure math and cutting-edge cyber defense. Step into the mind of a digital architect to decode the formulas that outsmart hackers, lock down infrastructure, and rewrite the rules of modern warfare. The future of security isn't coded—it is calculated.

Every web application has security headers, cookies, TLS configurations, and CORS policies that need to be correct. Most teams find out they're wrong only after a penetration test — or worse, after an incident. This book shows you how to build a scanner that catches these issues automatically. You'll create a Python CLI tool that uses Hurl (declarative HTTP testing) to assert security properties, SSLyze to validate TLS protocol versions, and AI to generate specific remediation for every failure it finds. The output: structured JSON reports, visual HTML dashboards, and AI-generated security posture assessments. **What you'll build:** - 9 declarative Hurl security test files (headers, cookies, CORS, HSTS, CSP, CSRF, redirects, TLS) - A preprocessor that handles domain substitution and authentication - An output parser with built-in remediation guidance for every test - A TLS scanner validating SSL 2.0/3.0 disabled and TLS 1.2/1.3 enabled - An AI analyzer that generates context-specific fixes using Ollama, OpenAI, or Bedrock - An HTML reporter with dark-themed visual dashboards - Docker multi-architecture deployment - CI/CD pipeline with GitHub Actions **Who this is for:** - Developers who want security checks before deploying - DevSecOps engineers building CI/CD security gates - Penetration testers who need quick baseline assessments - Security students learning web vulnerability concepts hands-on - Platform teams enforcing security standards across services Every failure includes: what was expected, what was received, why it matters, how to fix it, and a documentation link. AI adds domain-specific code examples on top.

Threat modeling is broken. It takes days, costs thousands, and most teams skip it entirely. What if your AI coding assistant could do it for you — systematically, consistently, and in minutes? This book shows you how to build an MCP server that makes it happen. You'll create 80+ structured tools that guide any AI assistant through a rigorous 9-phase STRIDE threat modeling workflow. Not vague prompts that produce unstructured text — real, typed, validated tools that build up a complete threat model piece by piece: business context, architecture, threat actors, trust boundaries, data flows, STRIDE-based threats, mitigations, and a final JSON export compatible with AWS Threat Composer. **What you'll build:** - A full MCP server with FastMCP (stdio + SSE transport) - Pydantic v2 data models for type-safe threat modeling - Case-insensitive enum validation (because AI isn't always consistent) - 11 tool modules covering every phase of STRIDE analysis - Customizable organization security guidelines loaded from `.md` files - Docker deployment for team-wide access - Compliance gap analysis that validates against mandatory controls - A complete workflow orchestrator with progress tracking **What makes this different:** The server doesn't call any LLM itself. It provides the structure and tools — your AI assistant (Claude, Kiro, Cursor, Copilot) provides the intelligence. This means it works with any model, any provider, forever. No API keys, no token costs for the server itself. **Who this is for:** - Security engineers who want to automate repetitive threat modeling - Python developers building MCP servers for any domain - DevSecOps teams embedding security into AI-assisted workflows - Architects who need consistent, auditable threat models - Anyone curious about how MCP tools work under the hood **By the end of this book**, you'll have a production-ready MCP server, a deep understanding of how AI tools are structured, and transferable patterns for building MCP servers in any domain — not just security.

Device Mapper is the invisible engine behind LVM, LUKS, dm-verity, and thin provisioning — yet most engineers never look under the hood. This illustrated guide gives you the complete picture: from BIO remapping and mapping tables to real-world stacking patterns like LVM-on-LUKS and Android Verified Boot. 8 chapters, all visual, zero fluff.

Real lessons from real bug bounty work — focusing on what actually leads to vulnerabilities, not just theory.

A senior level Android book about what actually breaks in production: Compose, performance, architecture, build systems, CI, and scale. Less “hello world”, more “keep it alive”.