The new and the shiny
As technologists we're naturally inclined to seek out all the latest tools and processes—but with a critical eye, because “new and shiny” doesn’t necessarily mean “best.” We don’t use something just because it's getting a lot of buzz on Medium, we select the best tool for the job and set aside research time for exploring promising tools that might not quite be ready for prime time.
If you’re using FTP for any part of your deployment process, chances are you’re doing it wrong. Are you changing configuration files in production? You’re doing it wrong. Do it properly and decrease risk by formalizing a release process. Increase predictability by lowering the chance of human error.
No silos here
Nobody’s perfect. Developers all know what “code smell” is—a feeling that something might be “off” in the code, triggering a closer look, and then refactoring with abandon until all is well. We try not to restrict that to code. Recognizing that a particular process doesn't work well, or that a tool we’re using doesn’t quite hit the mark, or even failing, is all good. We learn from our mistakes, and we evolve.