@tbaxter-18f asked me to provide some reasons as to why I didn't use this script for constructive feedback. A lot of my reasons are opinion-based and may or may not be valuable.

• git-seekrets: really out of date and looks to be unmaintained.
• Installs ruby. Nah, I'm good, I'll lazy init on that until I can't anymore, then I'll install rvm, not rbenv. Ruby sucks.
• Installs node via nvm. Nah. Javascript also sucks.
• pyenv-virtualenvwrapper: I prefer Anaconda to venv, all personal preference.
• Installs cloudapp, I don't need it.
• Installs the Selenium chromedriver, also don't need it.
• Installs atom, I use vscode, atom isn't my thing.
• Installs spectacle, not sure what that is, never used it, prolly don't need it.
• Installs ctags, I don't even know the last time I needed ctags because I don't use vim for more than basic editing. I use various symbol servers and language specific LSP implementations (see LSP) as it's more abstract.
• Installs tmux, I use screen (only when there's no tab support, which iterm2 has)
• Installs reattach-to-user-namespace, no idea what that is, prolly don't need it.
• Installs coreutils, while useful, can cause scripting problems for local development.
• Doesn't install Go, I need Go for cloud.gov development.
• Doesn't install dotnet core, I need dotnet core for open source dotnet projects.
• Doesn't install Java, I need the AdoptOpenJDK distribution for open source cloud foundry projects.
• Doesn't install repo, which is a multi-repository manager and would be amazingly helpful for cloud.gov's >50 repos.

I think there are some things that could be very helpful to folks at 18F first coming here:

1. Start using repo as the defacto repository manager. It will help with local dev, it's heavily maintained, and it's not going anywhere. Plus it has native code review integrations with Gerrit, which is also very useful. You can have different flavours of repo manifests, which means you can have cloud.gov manifests for cloud.gov code, login.gov manifests for login.gov code, etc.
2. Add more development languages, not just tools.
3. Installation menu, like aptitude or buildroot, so devs can install recommended categories, but specific tools of their preference.

There might be more reasons I had or improvements I've thought of, those are just the ones that immediately came to mind.