Engineer Statelessly: My Scoop Environment Selection for Recovery in 5 Minutes

For engineers, setting up a development environment is often seen as building up “assets”. However, I believe the opposite is true.

Meticulous settings, indispensable resident software, and scripts used for years. The more these accumulate, the stronger the dependence (state) on the physical device—the PC—becomes, and environment migration or reconstruction turns into “debt”.

My strategy is simple: Maintain a “stateless” condition where I can discard my PC at any time, while achieving lightning-fast response speeds.

To achieve this, I thoroughly lightweight the Windows Native environment and offload heavy development machinery (such as Node.js) to WSL2. By managing these with Scoop, environment recovery can be completed in just 5 minutes.

In this article, I will introduce the tools I’ve carefully selected to “discard information and live lightly”, along with my selection criteria.

”Environment as Code” with Scoop

Visiting official websites and clicking through installers is a waste of time. I manage all my tools with Scoop and build my environment “declaratively”.

The reason I choose Scoop is that apps are consolidated into a specific directory with paths already configured, preventing system clutter. By selecting tools that don’t scatter settings, a single scoop export can reproduce the same behavior even on a new PC.

The Three Pillars: “High-Speed” Tools to Free Up Brain RAM

I won’t explain every single app. Instead, I’ll focus on the three most important tools that support my “efficiency” and “philosophy”.

Clink (+ fzf) — Externalizing Memory

The standard Windows cmd.exe is the fastest to start. By introducing Clink, I add a Bash-like operational feel, combined with history searching via fzf. By shifting from “memorizing” commands (a brain state) to “searching (JIT generation)” from past history, I can free up brain memory.

Keypirinha — Keeping Thought Velocity High

The optimal solution for those who find even PowerToys Run to be too heavy. I operate it by changing the shortcut to Alt + Space. It is as light as air even when running in the background—the fastest interface for me to instantly convert thoughts into actions (launching apps, calculations, dictionary lookups).

bt (Browser Tamer) — Automatic Context Control

For a full-stack engineer who uses multiple browsers and profiles, wondering “which browser should I open this in?” every time they click a link is noise. With bt, links are automatically routed to the optimal browser based on domain or URL rules. By delegating the “judgment” state to a tool, the development flow remains uninterrupted.

Rational Hybrid with WSL2

I don’t put everything into WSL.

• Windows Native: GUI operations, system utilities, and lightweight tools that require the speed of thought.
• WSL2: Execution environments for Node.js, Python, etc.

Specifically for Node.js, running it on WSL2 is the correct choice to avoid NTFS IO overhead and reap the benefits of Linux native performance. Connecting the agility of Native with the power of WSL2 through the infrastructure of Scoop is my optimal solution.

My scoop list (CLI/Utility)

This is not everything in my environment. However, it is the “definition list that prescribes the standard functions of this PC”, which I pour in immediately after installing the OS.

Installed apps:

Name                Version         Source
----                -------         ------
7zip                25.01           main
aria2               1.37.0-1        main
bt                  5.5.6           extras
busybox             5857-g3681e397f main
clink               1.9.13          main
clink-completions   0.6.7           main
clink-flex-prompt   0.18            main
curl                8.18.0_4        main
dark                3.14.1          main
ditto               3.25.113.0      extras
driverstoreexplorer 0.12.135        extras
ffmpeg-shared       8.0.1           main
firefox-esr         140.7.0         extras
fzf                 0.67.0          main
gh                  2.86.0          main
git                 2.53.0          main
innounp             2.67.3          main
keepassxc           2.7.11          extras
keypirinha          2.26            extras
libwebp             1.6.0           main
modern7z            1.9.2           main
mpc-hc-fork         2.6.1           extras
obsidian            1.11.7          extras
python              3.14.3          main
rclone              1.73.0          main
steamguard-cli      0.17.1          extras
sumatrapdf          3.5.2           extras
vscode              1.109.0         extras
windows-terminal    1.23.20211.0    extras
winmerge            2.16.54         extras

Tools are Better When They Are “Transparent”

The goal is not to master tools or admire their settings. The ideal of “Stateless Engineering” is a state where you can immerse yourself in development without even being aware of the tools.

By discarding attachment to a specific environment and gaining the lightness to rebuild at any time—that is my technical strategy.