Post

I wanna hear the untold stories of the huge architectural and data migrations that go into the “smallest” changes like when Slack added the ability to add someone to a group DM and *move past messages* to the new conversation or how Amazon no longer asks which Kindle to send your library book to

Oh absolutely. It would either be one of those changes that is pretty quick & mostly a pain for testing edge cases… OR one that ended up needing 5 new services, a db migration or two, and an act of god There never seems to be a middle ground for that type of thing.

I want to hear more stories about the latter! I theorize that the examples I gave are ones in that category

0 reposts0 likes

Closest I can give is that adding a different tab for “business users” in settings required… - every product to update its user metadata - at least 3 new services to support… - … the entirely new User Service - rewriting the login service - a company wide change in how Product assumed Users worked.

The key problem being: we had user *authentication* but basically no centralized user system: each product kept its own user info locally to it, and so a Settings service/app had *zero* insight into anything other than “users exist” and like… name/email/etc. It was… a fun time I had explaining this