At DevTeach this past week, I had some great conversations, but one in particular is the conversation that many people have had: about using sharp tools. A common thought we come across is that a vendor or someone in management decides that the software team should be restricted in some way for their own good. If this measure isn’t taken, the software team could hurt themselves or the software could come out wrong. Some of the analogies used are:
- Running with scissors
- Unsafe tools
- If given a sharp knife, you might cut yourself.
These can be applied to many environments. For instance, an argument against dynamic languages is that without compile-time checking, errors won’t be found until runtime. If developers are allowed to use dynamic languages for _real_ projects, then the software would fail because we don’t know if it works until we run it. (I won’t bother replying to common arguments, but I invite readers to give their reply in the comments).
Unsafe tools could be IDE features, frameworks, libraries, or even permitted architectures. For instance, if we use 3rd party libraries or frameworks, developers might hurt themselves. Better stick to what comes from Microsoft.
Then, like children, I’ve heard that developers might cut themselves if given a sharp knife.
I credit 100% of the dysfunction of these thoughts to managers who allow or encourage these thoughts in their organizations. Being a software manager myself, I know that I’m paying quite a bit for good developers. I’m not paying for children, so I’m certainly not going to give them safety scissors, blunted markers or non-toxic playdough. Developers should be adults, not children. By the way, if you encounter developers who aren’t professional adults, then HR functions should step in. I want to give my developers the best, sharpest tools possible. They might hurt themselves or the company? There are other ways to manage that risk other than giving developers safety scissors.
I was reminded of these conversations by a blog post by Oren Eini, with whom I spoke about this issue at DevTeach. Oren came up with the following logo, which enumerates that one of the facets of the spirit of Alt.Net is that developers are professionals, and if there is a need to run with Scissors amids flying bullets, then they are capable of making that decision.
Chad Myers quickly condensed it down to the badge that I’ve added to my blog: