Stop Hardcoding Your Timeouts
Summary
This opinion piece argues against unconfigurable timeouts in developer tooling, using examples like the skills package and Docker Gordon to illustrate how rigid defaults hamper real-world workflows. It advocates safe defaults that are clearly documented and overridable, emphasizing the need to accommodate slower networks and diverse environments.