Postmortem: Microsoft To-Do
summary
Aleksei describes how the architectural process for Microsoft To‑Do was created, covering his involvement from the first month of development through the handover to Microsoft’s India support and development team. He will discuss concrete architectural decisions and processes used in the project, illustrated with accounts of problems, investigations, and controversial moments during the transition.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:01Microsoft buys Wunderlist
- 16:46Product evolution
- 33:33Integration challenges
- 45:04Engineering challenges
- 51:24Architecture myths & tips
- 1:00:03Summary
related talks
25mArchitecture evolution of Microsoft To-Do web app
01h 02mHow Microsoft To-Do Uses React
10mHow We React at Microsoft To-Do
53mKeynote: Enterprise transformation (and you can too)
32mDeveloper productivity 2.0
07mWhat we learned moving 65,000 Microsofties to DevOps...
01h 03mHerding cats: lessons from 15 years of managing engineers at Microsoft
15mTransitioning 69,000 engineers to one cloud system