The Deliveroo engineering team blog
Only awesome code.
As data scientists at Deliveroo we evaluate our work via robust experimentation, and we take a frequentist hypothesis testing approach. The standard method places a lot of importance on deciding upfront how large an impact we believe any experiment might have. If the estimated impact is very different to the actual impact, we might waste a lot of time running an experiment where we could have obtained a result sooner. This means that we can’t iterate and innovate as quickly as we would like. Our preferred solution to this problem is sequential experiment designs.
Taking advantage of Golang’s duck typed interfaces and net/http/httptest to test third party dependencies in web applications.
While integrating with a new payment provider, we needed to sync merchant ids via SFTP. We built an AWS Lambda function with Terraform to do this. I’ll walk through our Terraform configuration and the hurdles we overcame around accessing the S3 bucket and retrieving sensitive credentials.
Last week a seemingly simple ActiveRecord query was causing problems on production, by being incredibly slow. Together with my colleague Marty I debugged the issue and as a result we decreased the query time from about 80 seconds to about 100 milliseconds.
- How to migrate your API and still be friends with your fellow client developers
- What does an Engineering Manager do at Deliveroo?
- Application Deployment at Deliveroo
- Migrating from Buddybuild to Bitrise
- Interning at Deliveroo
- How to introduce Kotlin in your codebase
- How do we interview engineers at Deliveroo?
- Reset, Rebase Workflow
- Tired of waiting for pull request reviews? Play Pull Request Roulette
- Improving Password Security
- Determinating a Scavenger Hunt
- Data Sink
- How to un-rickroll yourself
- “I assess quality……therefore I am”
- Hackday and the £17 soda
- Every service is an island
- Scaling Rails 3.old