Preface

I believe everyone should benefit from tech. It is not just business and money but making products for your own needs.

That is why I wanted to write Slopware 101. The jokes about someone sharing a localhost link tell us there is a missing explanation. They do not provide it. A person has made something they want to show a friend, and there is a small, useful piece of computing between those two people. We can explain it.

I am Damla, and noseydewdrop is my independent studio. My projects connect things I am curious about: sewing and geometry in stitchu, language and world events in ir-globe, the work of coding agents and the evidence it leaves in Rabadon. Moving between those subjects gives me reasons to learn the machinery underneath them. I like understanding enough of a tool to change what it can do.

This book is for the person who already has something on a screen and wants to understand what they have made. Perhaps you wrote it, perhaps an agent helped, perhaps you started from a template. Open that project beside the book. We will begin with the screen and the person trying to use it, then follow the page from a folder to a browser and the data it reads and changes. Once those movements make sense, questions about permissions, deployment and repeated payments become questions you can investigate.

You do not need a large product to do that. A notebook with a save button is enough to ask whether a note survives a refresh, where it was saved, and who else can read it. Each answer gives the next question somewhere concrete to stand. The exercises use small examples and disposable data, so you can change one thing and see what happened.

If your own project behaves differently from an example, keep the difference in view. Finding which assumption changed is part of learning to read software.

You can be ambitious and still need someone to explain what a port is. Knowing the word is not the entrance fee.

For the first page exercises, you need a text editor, a browser and Python 3. Install Git when you reach version control, Node.js for the JavaScript test examples, and PostgreSQL for the local database exercises. The Node examples use version 24 or later. You do not need to install everything before starting. Shell commands go in a terminal, browser-console instructions go in the page's developer tools, and SQL goes in the named database's SQL client. Each exercise identifies its setting; keep practice data separate from an app people actually use.

I respect anyone who is dreaming and building something.