choose-dev-entrypoints

Choosing the right dev entrypoint requires a layered delegation model that assigns ownership to the lowest capable layer, keeping shell entry cheap and workflows cacheable across Nix, Just, Bun scripts, and Turbo tasks.

Split responsibilities by keeping environment setup in Nix shellHook and delegating imperative task running to Just scripts, ensuring the shell entry remains fast while preserving understandable and cacheable workflows.

Use Turbo tasks for build and test workflows when you need cacheable, delegated task execution across a monorepo, whereas package scripts are better suited for simpler, localized command execution within a single package.

Nix develop works well with Bun scripts and Turbo by providing the isolated environment, while Bun and Turbo handle service startup and task delegation, maintaining a clean separation between environment setup and command execution.

Dev workflows slow down because shellHook executes on every shell entry, so placing heavy operations like code generation there violates the cheap shell entry principle and increases startup latency.

You might still need a ./scripts directory for imperative, one-off commands that do not fit Just's declarative task model, keeping Just focused on repeatable, cacheable dev, build, and install workflows.