Books

Effective Code Review Tips and Tricks

Learn how real databases work by following this practical guide to building your own in a programming language of your choice.Build a language from scratch- Create an interpreter that can parse, type check and run SQL queries. Start with running simple queries and build up to more complex ones.Learn SQL (the fun way) - Gain a deeper understanding of SQL. Cover the order of execution of queries, how SQL uses ternary logic and the techniques that databases use to join and group data efficiently. Compare your implementation with databases such as PostgreSQL, MySQL, SQLite and DuckDB.Improve as a programmer- The perfect project to practice how to structure and refactor code as you grow the feature set of your database server. The 200+ included test cases provide a safety net for refactoring your code, giving you freedom to experiment. Learn computer science topics including creating a recursive descent parser, building a type checker and implementing iterators.

This book is written for anyone who wants to understand what testing and testing leadership are all about. A better understanding will help to lead and improve your testing - whether testing is outsourced or in-house. CEO, CIO, or CTO - this is the testing book for you, too! It's also for anyone who works with software: product owners, project managers, system analysts, developers, testers, test managers, and many others, including students. We have created ACT 2 LEAD mnemonic to help you in leading testing.  Read the book to learn what it means!

Smart Contract Security: Finding DeFi Vulnerabilities is a comprehensive technical guide to understanding, identifying, and mitigating security vulnerabilities in Ethereum smart contracts and decentralized finance protocols. The title begins with the foundations of EVM architecture, Solidity execution, storage layout, threat modeling, and access control before progressing into the most important vulnerability classes encountered in modern smart contracts. Topics include reentrancy, read-only reentrancy, arithmetic and precision issues, denial-of-service patterns, unchecked calls, transaction-ordering dependencies, MEV, and integration risks.

It is three in the morning and something is wrong with your LLM application. This is the book you open. Not a tutorial — a reference manual, organised by symptom, for the moment something you built has already broken.

Generative AI can write code fast, but fast does not always mean safe. This practical guide shows software teams how to verify, test, secure and govern AI-assisted code across the full development lifecycle. Packed with real-world examples and practical workflows, it offers a clear path to adopting AI without lowering the bar for software quality.

This book is all about testing and closing the gap between infrastructure health and output quality, and how easily that gap can be filled for weeks by a failure that's gone unnoticed.This book looks at the less obvious side of the problem. In the next few chapters, we're going to run 41 experiments on one application. About half of them will give you a result that the system doesn't report. It's not a dig at anyone's engineering, since the systems in question are competently built and mostly behave well.

Turn Python testing from a manual chore into a reliable engineering workflow. Learn pytest through practical examples covering assertions, exceptions, fixtures, parametrization, test organization, coverage, and CI. Build a stronger safety net for your Python projects and refactor with confidence

An English CTFL guide that teaches you not to memorize the correct answer, but to understand why the distractors are wrong. Complete coverage of all six chapters, worked examples for every K3 learning objective, and a full mock exam with detailed answer rationales. Aligned with the CTFL Syllabus v4.0.

The QA field manual: the entire career arc, from your first two weeks on the job to strategic leadership, told through patterns and anti-patterns.

Everything in the series, deployed into the interviews that decide your career — STAR stories, live exercises, negotiation scripts, first 90 days.

Documents that drive action: test plans people read, bug reports that get fixed, RCAs that prevent repeats, and docs that outlive team turnover.

Move from running tests to leading quality: strategy aligned with business goals, automation ROI you can defend, and metrics that drive decisions.

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