Inconsistent Onboarding for New Developers

“Ask HN: What developer productivy tools would you need? I saw the Aviator is hiring post (https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=34248128) - a YC company I haven&#x27;t heard of before, but they seem to focus on developer productivity. At least some aspect of it (it seems to be about more SDLC, rather than ergonomy of keyboard shortcuts).<p>They seem to want to go broad with the tooling. At least this is the impression I got when reading their WWW. Nothing wrong with it. I suppose eventually they would have 5 to 10 more things than just the Merge Queue and the Flaky Bot.<p>I&#x27;d be curious what other ideas people might have for tools like this.<p>Let me start with a few from myself. Curious what others say:<p>1. A better Dependabot, which at least in Java (Maven&#x2F;Gradle) ecosystem works only for basic projects. It has so many limitations.<p>2. Onboarding helper. I.e. something which sets up everything for a new developer, and maintains that consistency of the setup going forward. So that the infra&#x2F;DevOps teams (who I guess would be the key users at your customers) can use it to provide consistent but flexible setup for everyone. And be able to evolve that. I mean things like IDE, build script setup with all the dependencies, key tools installed like terraform, GH client, a linter, etc. All of them in the same version for everyone.<p>3. Command-line friendly and user friendly credentials interface. Think of a mix of 1Password and hashicorp vault. But it should work well in all three contexts: nice GUI, CLI and automation (not only on my laptop, but as part of some CI pipeline or other toolling). It doesn&#x27;t have to be the storage, delegate to 1P&#x2F;HCV.<p>4. A collaboration tool for dealing with different kind of error messages, warnings and problems. Think of something like a mix of StackOverflow and Sentry. Group by type of the error, but focus on what developers experience in their dev environment (tests, build scripts, etc.). Deduplicate, store and offer solutions as a knowledge base<p>5. Time measurement tool, but not the one for my employer to check if I waste time on Facebook. But measure the length of my cycles - i.e. count of local runs before I commit, or count of CI-failure-then-fix iterations. And aggregate that, so that again my DevOps team can see some stats and know how to increase velocity by knowing what are the bottlenecks (but don&#x27;t trust subjective feelings on that, gather data).”