Community
Guides, notes, and the writers behind them — everything worth exploring.
Debugging as a repeatable method, not luck — reproduce, isolate, form hypotheses, read the error, bisect, and the tools that make it faster.
Curated guide · updated 2026-07-13
A sensible way to lay out a codebase — folders by feature, separating concerns, config, naming, and structure that scales as the project grows.
Curated guide · updated 2026-07-09
Building UIs that stay maintainable — component boundaries, state, consistency, accessibility, and design decisions your future self will thank you for.
Curated guide · updated 2026-07-06
When something breaks and I have no idea why, I run through this list before touching any code. It turns panic into a process. 1. Reproduce it reliably A bug…
scorpionxdevNaming is the cheapest documentation you will ever write and the first thing the next reader sees. A good name removes the need for a comment. Say what it is…
scorpionxdev