battwell
You can find more information about Splitter in this blog post: https://techblog.atoms.co/p/easy-as-pie-stateful-services-at
Blog post about our in-house message broker: https://techblog.atoms.co/p/reliable-order-processing
Source code is available in the splitter repository. You can see Splitter in action in splitter-examples (only requires Docker and Bazel). Repo: https://github.com/atoms-co/splitter-examples/tree/main/robo...
We will never intend to sell this. So may as well open source it.
1 https://www.microsoft.com/en-us/research/wp-content/uploads/...
We've been doing data science and ml for years. After iterating on our tooling for a few years, we've finally settled on some tools that we're happy with. A lot of the wins came from spending more time data with DS teams to understand what they really wanted tbh
And ray has been great!
ML Infrastructure Doesn't Have to Suck
Moving Millions of Orders with Robotic Conveyance
I've used CRDB early on at a startup. There was some overhead. You don't get all the nice PSQL features
Although it did save us a giant migration later on
This feature was largely implemented as a result of on hackernews and reddit.
Just run `nanoscope flash`.
If our CI efforts prove stable, then what you're suggesting should also be possible, if I understand it correctly.
Nanoscope: Method-Tracing Tool for Android
Wouldn't you say mathmatics is the most infallible thing human's have come to creating? The level of rigor in mathematics is much higher and there aren't as many repeatability issues.
What is most interesting to me: we prioritized mobile app architecture and saw big wins as a result. Usually its hard to commit time upfront to app architecture. We've made that the norm (ex, 80% of our app code lives inside plugins). And we've seen eng productivity measurably increase over the last year because of these investments. In many cases doubled.
But the old Uber app had hit its age limit. It was build on top of technology chosen for a small number of features (ex: a single global DI component, lack of typing, a small MVC hierarchy). So we either needed lots of large migrations or a rewrite. The incremental migrations required to fix these issues would have been extremely disruptive, they wouldn't have gotten us an entirely refreshed UI and they wouldn't have given us a number of other benefits.
So we decided to do a rewrite. We had lots of engineers that knew the issues to watch for from the first time we wrote the app. And a handful of us spent months researching/building different architectures, static analysis and tooling that would ensure the rewrites success. We weren't going to repeat the same mistakes twice.
On the very first day the app launched it was more reliable and performant than the version of our app that we had been maintaining for years.