|
|
|
|
|
by mdekkers
3227 days ago
|
|
On piping anything from the Internet directly to your system for execution: Don't be lazy. Don't be an ass. When I am working in a persona that responsible for managing a server or a service, I insist on knowing everything I need to know about how to keep that service and the environment in which it operates safe, alive, and providing usable performance. I require good, clean and coherent instructions for deploying something at production level, where all required components and their preferred method of interaction are clearly explained and documented by the developer, and can be repeated in a predictable manner by me. If all I have to work with is "pipe this to the shell, alternatively read the code" I'm going to go with "nah, I'll find something professional". Time spent installing a system should be only a minuscule fraction of time spent actually operating the system. Spending a few extra hours doing it right shouldn't make a difference. [edit: added "...and another thing" argument] |
|