E-E-A-T for a Solo Developer Site: Proving You Actually Used the Tools
Google rewards experience, expertise, authority, and trust. For a solo site the strongest signal is one you control: demonstrably real use of every tool you review.
Every review is written after real use. Every calculator shows the math. No recycled spec sheets.
Google rewards experience, expertise, authority, and trust. For a solo site the strongest signal is one you control: demonstrably real use of every tool you review.
A practical look at SQLite indexes: when they help, when they hurt, and how to find the queries that actually need one.
The exact systemd unit I run for Go services: restart policy, hardening, environment file, and the flags that stop a crash from becoming an outage.
This site started as a hand-built static generator and moved to my own Go CMS. The honest reasons: content workflow, ad slots, and the cost of static's purity.
The clean ways to get data out of SQLite — JSON via sqlite3 CLI, CSV with proper headers, and the escaping traps that corrupt exports.
A minimal uptime monitor you can run without any third-party service: a /healthz endpoint, a cron job, and a curl. Here is the exact setup.
The docs that pay for themselves: a DEPLOY.md, a DESIGN.md, and a SECURITY.md in the repo. What each one prevents, and how to keep them honest.
The tradeoff between speed and durability in SQLite: what WAL and synchronous=NORMAL actually mean, and when FULL is the right call.
The practical rules for keeping API keys and passwords out of version control — environment files, .gitignore, and what to do when one leaks anyway.
A calm comparison between SQLite and MySQL from someone who runs both: when the zero-ops file wins, when you need a database server, and the honest middle.