New to Software Testing? Read the Software Testing article
Cultivate a deep understanding of testing on the Salesforce platform—unlock the tools, patterns, and techniques that turn good ideas into quality solutions
Build high-volume systems. Thrive through sociotechnical challenges. Survive gruesome production incidents.
Get started with Test-Driven Development (write tests before the code), Build Automation (make the overall process of compilation and testing automatic with Maven), and Continuous Integration (commit changes and a server will perform the whole build of your code). Using Java, Eclipse, and their ecosystems.
What does a pattern language built for software traces and logs see when it is turned on machine learning? This book reads training runs, inference services, and agents through their logs, and then reads the forward pass, attention, and generation themselves as traces. Every correspondence is marked as literal, structural, or metaphorical.
Thirty-eight conversations from Dave Farley's Engineering Room podcast, now in book form. Kent Beck, Martin Fowler, Jez Humble, Nicole Forsgren, Eric Evans, Kelsey Hightower and many more talk candidly about what it really takes to build great software.
89% of teams with production AI have observability. Only 52% have evals. This book builds the missing 48%. Fifteen chapters teaching you to construct a production-grade evaluation harness from scratch — golden datasets, deterministic scorers, LLM-as-judge, RAG metrics, agent evals, CI regression detection, and production monitoring.
The book is a fully revised transcript of a seminar about physical memory analysis on Windows platforms. Topics include memory acquisition, memory spaces, challenges of physical memory analysis, common WinDbg commands, memory analysis patterns and their classification, common mistakes, a hands-on WinDbg analysis example, a guide to further study.
With the advent of LLMs and AI coding assistants, we are generating code at an ever-accelerating rate. How do we manage this influx of code without getting fatigued and overwhelmed? How do we ensure coding standards are maintained? What practices and tools can we put in place to amplify our efforts while not introducing more bugs?
This book is a collection of my articles originally published in the blogs Interrupt by Memfault and PlatformIO, with some additional edits and enhancements. A unique feature of this book is the extensive use of GIF animations and videos to visually demonstrate key concepts and processes. However, since not all EPUB readers support GIF and video playback, each animation and video is accompanied by a link to an external resource. Readers can follow these links to view the corresponding content and enhance their understanding. Repo with all GIF animation: https://github.com/Zamuhrishka/diving-into-jtag-book-animations
What is a good software architecture? Why should we bother structuring the code and spending time testing it? If you like spending hours debugging your programs or staying late at the office to recover from a buggy deploy in production this book is definitely NOT for you!
Effective Code Review Tips and Tricks
FREE BOOK! This book is a comprehensive guide specifically designed for individuals preparing for the CISSP exam. It offers concentrated notes and key information for revision, making it an ideal resource after completing the main reading material. By providing a concise summary of essential topics, the book aims to save valuable time, especially during the critical last-minute study phase, possibly a week before the exam.
Make desktop automation practical, reliable, and cross-platform. Discover how to automate real-world applications, record interactions, and build maintainable GUI tests with Python.
Let’s make a confession. This handbook is about me, and, I suspect, about you, your team, and your organization too.I’ve made almost every mistake listed in these pages. I’ve seen them repeated in startups, enterprise systems, and everything in between, while mentoring teams, auditing architectures, or helping companies rediscover what testing is really for. The point isn’t to assign blame. It’s to hold up a mirror. Because the truth is, most of these mistakes are so common, you can probably spot a few right now; in your code, your team, or your last retrospective.When we talk about test failures or mistakes, the first thing that usually comes to mind is developers, missed edge cases, flaky tests, broken pipelines.
Die meisten Unternehmen können schnell liefern, aber nur wenige können sich in großem Maßstab anpassen.The Cybernetic Enterprise stellt ein einheitliches Betriebsmodell vor, das KI, Rückkopplungsschleifen und Plattform-Denken in die DNA Ihrer Organisation einbettet. Erfahren Sie, wie Sie ein System aufbauen, das Veränderungen wahrnimmt, kontinuierlich lernt und Disruption in strategische Vorteile verwandelt.