An ex-Googler's guide to dev tools

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • scalar

    Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer (by microsoft)

  • Microsoft has/had a mono-repo based on the Git Virtual Filesystem, but future efforts have apparently moved towards the use of Scalar: https://github.com/microsoft/scalar

  • mutant

    Automated code reviews via mutation testing - semantic code coverage.

  • There's a pretty good Ruby gem I've used for this before:

    https://github.com/mbj/mutant

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • rules_js

    High-performance Bazel rules for running Node.js tools and building JavaScript projects

  • I also think it is partly as the tooling is not there yet - especially in the typical case when a project depends on lots of external dependencies.

    I am looking forward to new set of bazel rules being worked on for eg. https://github.com/aspect-build/rules_js and https://github.com/jvolkman/rules_pycross which will makes it more idiomatic to work with existing language ecosystems.

  • rules_pycross

    Bazel + Python rules for cross-platform external dependencies

  • I also think it is partly as the tooling is not there yet - especially in the typical case when a project depends on lots of external dependencies.

    I am looking forward to new set of bazel rules being worked on for eg. https://github.com/aspect-build/rules_js and https://github.com/jvolkman/rules_pycross which will makes it more idiomatic to work with existing language ecosystems.

  • redirector-rs

    A dead simple human-writable URL redirector based loosely on google's `go/` system.

  • Relatedly, I was reading software engineering at google and came across the chapter about being able to find things; they have a URL shortener internally that works a little like AOL keywords from back in the day it sounded like.

    So, I was trying to find a URL shortnener which allowed for pretty links similar to what the internal “go/“ site supports. I didn’t find anything so I made it:

    https://github.com/dijit/redirector-rs

  • homebrew-tap

    A private homebrew tap to install the Graphite CLI tools. (by withgraphite)

  • https://graphite.dev/

    > Join the waitlist

    :-(

    Since you seem to be in the beta, you may want to let them know their Homebrew tap is pointing to the wrong GH org: https://github.com/withgraphite/homebrew-tap/blob/master/For...

  • clusterfuzz

    Scalable fuzzing infrastructure.

  • Then it is clear that the behavior of this for loop is either not important or not being tested. This could mean that the tests that you do have are not useful and can be deleted.

    > For most non-trivial software the possible state-space is enormous and we generally don't/can't test all of it. So "not testing the (full) behaviour of your application is the default for any test strategy", if we could we wouldn't have bugs... Last I checked most software (including Google's) has plenty of bugs.

    I have also used (setup, fixed findings) using https://google.github.io/clusterfuzz/ which uses coverage + properties to find bugs in the way C++ code handles pointers and other things.

    > The next question would be let's say I spend my time writing the tests to resolve this (could be a lot of work) is that time better spent vs. other things I could be doing? (i.e. what's the ROI)

    That is something that will depend largely on the team and the code you are on. If you are in experimental code that isn't in production, is there value to this? Likely not. If you are writing code that if it fails to parse some data correctly you'll have a huge headache trying to fix it? Likely yes.

    The SRE workbook goes over making these calculations.

    > Even ignoring that is there data to support that the quality of software where mutation testing was added improved measurably (e.g. less bugs files against the deployed product, better uptime, etc?)

    I know that there are studies that show that tests reduce bugs but I do not know of studies that say that higher test coverage reduces bugs.

    The goal of mutation testing isn't to drive up coverage though. It is to find out what cases are not being exercised and evaluating if they will cause a problem. For example mutation testing tools have picked up cases like this:

       if (debug) print("Got here!");

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts