Slightly safer vibecoding by adopting old hacker habits (addxorrol.blogspot.com)

The post argues that “vibe coding” can be made somewhat safer by moving development to a rented VM accessed via SSH with limited local secrets, using detached tmux/screen sessions for long agent runs. It says this reduces the impact of most supply-chain compromises, but notes that SSH key forwarding could still be abused—so it recommends separating a main repo from a forked development repo and using cross-repo PRs for human review. The author links the approach to older hacker practices of developing on systems you don’t own.