DoorDash Engineering Blog
blog.doordash.com · Company blog · on HN since 2013
DoorDash's company blog, with engineering posts on scaling and migrations plus announcements on policy, funding and security incidents.
What HN saysHN commenters link it as the primary source for DoorDash's tipping change and its data breach notice, and criticize its Project Dash as hypocritical.
26HN people shared it
5linked it in comments
38stories submitted
744story points
5 years agolast shared
2013people per year2026
Most-shared posts
- 1Scaling StatsD at DoorDash3 people · 10 points · first shared 2018 · 2 comments on HN
- 2DoorDash Data Leak; 4.9 Million Customers affected3 people · 6 points · first shared 2019 · discussion on HN
- 3Working to Strike a Better Balance2 people · 1 points · first shared 2019 · 1 comments on HN
- 4DoorDash removing 1-year cliff for equity grants1 people · 230 points · first shared 2021 · 269 comments on HN
- 5Tips for Building High-Quality Django Apps at Scale1 people · 191 points · first shared 2017 · 120 comments on HN
- 6Migrating from Heroku to AWS using Docker1 people · 149 points · first shared 2015 · 54 comments on HN
- 7DoorDash Raises $40M, Led by Kleiner Perkins Caufield and Byers1 people · 60 points · first shared 2015 · 46 comments on HN
- 8DoorDash (YC S13) Food Delivery by Drone1 people · 14 points · first shared 2015 · 1 comments on HN
- 9Implementing REST APIs with Embedded Privacy1 people · 10 points · first shared 2013 · 7 comments on HN
- 10Integrating GitHub with Jenkins for Continuous Integration and Deployment1 people · 8 points · first shared 2017 · discussion on HN
- 11Avoiding cache stampede at DoorDash1 people · 6 points · first shared 2018 · discussion on HN
- 12Startup Play Calling: Changing Your Tech Stack Post-Series A1 people · 6 points · first shared 2014 · discussion on HN
- 13Combining two great companies: DoorDash to acquire Caviar1 people · 6 points · first shared 2019 · 1 comments on HN
- 14127M More Ways to Move DoorDash Forward1 people · 5 points · first shared 2016 · discussion on HN
- 15Powering Search and Recommendations at DoorDash1 people · 3 points · first shared 2017 · discussion on HN
What HN people wrote when they linked it
strombofulous · 2020-12-09
Doordash stopped doing the tipping thing over a year ago https://blog.doordash.com/working-to-strike-a-better-balance-e1f66c76f…
SheinhardtWigCo · 2020-10-17
They did change it: https://blog.doordash.com/working-to-strike-a-better-balance-e1f66c76f…
luhn · 2019-09-26
The official blog post: https://blog.doordash.com/important-security-notice-about-your-doordas…
zzzeek · 2019-07-22
I think the thing that's making it look a lot worse for Doordash is their hypocrisy in things like this: https://blog.doordash.com/introducing-project-dash-bbc61ac0cb8c
the critique goes :
1. rip off workers
2. workers are poor, cant afford food
3. launch BS "anti-hunger" initiatives which address about 1% as much hunger as they cause, but make customers feel like they are doing a good thing using the service.
it's not unlike how big oil companies like BP run tons of advertisements how they are so "invested" in renewable energies like solar, spending a tiny fraction of the money they gain by profiting off of generation of greenhouse gasses and also dumping millions of gallons into the gulf of mexico every now and then.
big_chungus · 2019-09-26
Original blog post: https://blog.doordash.com/important-security-notice-about-your-doordas…
From the techcrunch article: "It’s not clear why it took almost five months for DoorDash to publicly reveal the breach. DoorDash spokesperson Mattie Magdovitz say why [sic]."
Pretty bad. If personal identity info is exposed, it is irresponsible not to notify users immediately so they can freeze credit and watch for suspicious activity. The blog post did mention a third-party vendor, so it's possible there was a delay, but it's a whole other problem if it took this long to find a breach.
This sounds like it could be "flipboard-itis". Flipboard stored passwords insecurely in the beginning (SHA-1), but switched to bcrypt as it scaled. The passwords breached were before 2015, so possibly a similar thing here where they started out with bad security and improved with scale (but left the old stuff behind). I'm guessing Doordash did something similar and improved security as it scaled.