The 2017 book I still keep
The paperback still sits on my desk because it framed control questions I still ask before I trust a stack with data.
A paperback from 2017 still sits on the corner of my desk, spine toward the wall so the long title does not dominate the room. The cover is faded. I have read the coin chapters once. I keep the book because it gave me plain language for a problem that keeps returning under new names.
The full title is Blockchain: Ultimate Guide to Understanding Blockchain, Bitcoin, Cryptocurrencies, Smart Contracts and the Future of Money (2017). I name it here so you know which volume I mean. After this paragraph I will call it the 2017 book, the way I refer to an old admin manual by the job it helped me do.
Why it stayed on the desk
I bought the book during a stretch of client meetings where every slide deck had a chain diagram and almost none had a backup plan. I needed vocabulary for the room, not a trading strategy. The chapters on wallets and markets dated quickly. The framing around custody did not.
Custody, in that context, meant knowing who held the authoritative record and whether you could recover it when the hosted service changed terms or shut down. I learned that lesson at midnight on a corrupted MySQL database, with no documentation of who had admin rights on the box.
The LAMP box and the same habit today
In the late 1990s I ran PHP and MySQL on hardware I could touch. I could follow a request from the vhost config through the include path to the query log. The stack was messy and legible to anyone willing to spend an afternoon with the files.
When a client asked whether their order history was safe, I could point to the backup tape rotation and the user table permissions. The answer was sometimes uncomfortable. It was never mystical. The 2017 book reminded me that comfort came from knowing where the bits lived and who could change them, not from a buzzword on a slide.
I run small open models on hardware I own for a related reason. The weights sit on storage I control. The inference runtime is software I can inspect and pin to a version. A cloud API can be faster. It can also change behavior between Tuesday and Wednesday without a changelog I am allowed to read.
The 2017 book did not teach me how to quantize a model or tune PHP opcache. It trained a reflex. Before I hand data to a system, I want to know where the record lives and whether my inputs become someone else’s training set. Ledger pitches and model pitches use different nouns. The control question is familiar.
The paperback stays on the desk as a custody reminder. When a vendor promises efficiency without naming who holds the record, I still reach for it before I reach for a new acronym.