Wayward House Gear Lab
Building a Digital Research Lab from the Keyboard in Front of You
1 A Digital Research Lab
This book starts from a simple premise: scientific computing is not just about code. It is about building a working environment that helps you find things, trust your results, recover from mistakes, and keep expanding your capability over time.
The core unit is not the laptop, server, or cloud account by itself. The core unit is the lab: the system of devices, files, notes, scripts, services, habits, and checkpoints that lets you move from a question to a reproducible answer.
This edition also treats the lab as something that can be published and pulled. Instead of asking every reader to assemble a research environment from scratch, we can distribute known-good lab environments through GitHub, pair them with open data, and let people prove the setup works on day one.
1.1 What this book is for
This book is for people who want to move from a fragile personal setup to a deliberate research environment. It is written for:
- students building their first serious computing workflow
- researchers who need a calmer, more reliable foundation
- consultants and analysts who need to keep work organized across projects
- technical generalists who want a strategy, not just a list of tools
1.2 What this book is not
This is not a narrow software manual. It does not assume one operating system, one programming language, or one institution. Instead, it gives you a strategic approach that works across macOS, Windows, and Linux and scales from a single machine to a cloud-connected lab.
1.3 Design goals
By the end of the book, your environment should help you:
- set up a dependable machine on any major platform
- work comfortably from the shell and a capable editor
- manage notes, references, tasks, and decisions
- organize research projects and datasets for reuse
- pull portable lab environments from GitHub and adapt them locally
- separate raw data, derived data, and published outputs
- back up your work and retain what matters
- use cloud services without creating unnecessary complexity
- expand your lab deliberately as your needs grow
1.4 The operating philosophy
Throughout the book we return to a few ideas:
clarity before cleverness- Prefer systems you can explain and repair.
plain files over hidden state- Keep your knowledge and work in durable, inspectable formats whenever possible.
automation after understanding- Automate work that is already stable, not work you do not yet understand.
reproducibility as a spectrum- Perfect reproducibility is rare; improved repeatability is almost always achievable.
small, reversible steps- Build the lab so mistakes are easy to detect and recover from.
proof before platform- Demonstrate the lab with a small working dataset and one successful analysis before adding more machinery.
1.5 The arc of the book
We begin with foundations: machines, operating systems, shells, editors, package managers, and directory layout. Then we add a new middle layer: the portable lab environment distributed through GitHub, optionally packaged with containers, and proved out with open data. From there we move into the larger research system: project workflows, data management, analysis environments, backup strategy, cloud integration, and long-term maintenance.
The final chapter offers roadmaps for different starting points so that beginners, intermediate users, and experienced researchers can all find a sensible next step.