5 ms·
It is the speed of iteration so testing, ci/cd, and monitoring are necessary after the MVP.
by antupis 3y ago
It is the speed of iteration so testing, ci/cd, and monitoring are necessary after the MVP.
- sesm 3y agoIf you really care about speed of iteration, connect REPL to a running process and develop with it. Enterprise development practices are not about speed
- underdeserver 3y agoAt Google they absolutely are about speed - they're trying to help you go as fast as possible without breaking users.
- bootsmann 3y agoWould you say that Google has a reputation for shipping things quickly?
- underdeserver 3y agoI wouldn't. But I left Google early this year to work at a startup. I can tell you that the confidence I have with Google's tooling, testing infra, presubmits etc. are miles ahead of the confidence I have with our current pre-commits. But at Google we had millions of daily-actives and at the startup we have dozens, so if something breaks it's not too bad.
- Jensson 3y agoDo any other company start as many new things as Google? Google builds things extremely quickly for being that large. Then they shut them down just as quickly, which is another matter, but it is hard to argue that they are slow at building products.
- sesm 3y agoCan developer at Google run a copy of service in production environment and interactively develop it via REPL or some other hot code reload technique? It won't break any users if load balancer doesn't route real traffic to your instance.