> figuring out process that are repeatable and result in high velocity and code quality, but I'd imagine that this is what an organization like Google is good a

> figuring out process that are repeatable and result in high velocity and code quality, but I'd imagine that this is what an organization like Google is good at! Seems like Go is manifestation of such process. Because something like Rust is not for a repeatable process of _producing a lot of software_ by big teams with variation in experience and headcount. Rust is probably about _fewer people_ carefully designing _less_ of software, so it can be done once and stay forever. Rust is for architecting bridges, Go is for paving streets.