Dev.to
7/9/2026

Unboxable in Tech: The Evidence Locker
Short summary
A developer with a non-linear career (trainer, restaurant owner, postal worker, school aide, developer) reframes their CV as a skill graph instead of a timeline, then applies the same "don't replace what isn't broken" philosophy to building side projects: a WordPress-to-static-site bridge plugin, a self-hosted dev.to analytics platform using FastAPI and PostgreSQL, and a Cloud Run cost-optimization fix against a botnet. The recurring theme is questioning conventional tool choices and building infrastructure layers that preserve personal fluency rather than chasing fashionable replacements.
- •Author reframes a fragmented career as a graph-based CV, arguing the timeline format was a rendering problem not a content problem
- •Built a WordPress-to-static-site bridge plugin and a full dev.to analytics stack using FastAPI, PostgreSQL, pgvector, and Streamlit with GitHub Copilot CLI assistance
- •Reduced a Cloud Run billing spike by 96% by closing unnecessary public endpoints after a botnet attack rather than scaling up
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



