[gavinjoyce]

At Intercom, we've been incrementally upgrading our almost 6 year old Ember app to Octane as the features have landed over the past 8 months. Our app continues to be in great health and we continue to ship hundreds of times a day with a constant stream of features that our customers love [1]

Octane is a huge leap forward for Ember. Its APIs are extremely well designed, composable and cohesive. The new Glimmer components and @tracked properties have resulted in waves of negative diffs as we refactor parts of our app to Octane and, IMO, are an advancement in the state-of-the-art component state tracking / reactive UI.

If you've tried Ember before and were turned off by some of its slightly weird APIs (computed properties, component APIs like tagName, classNames & event handling, the ember object model), you should take a second look.

With Octane, Ember is a framework for rapidly building high quality web applications that will remaining healthy over time as the web platform and JS ecosystem rapidly changes.

[1]: https://www.intercom.com/changes/en

[social_quotient]

Can you shed a little light on the sorts of things that are shipped hundreds of times a day? curious if you could share some use cases or examples.

Intercom is pretty awesome - congrats!

[gavinjoyce]

Sorry, I meant to say we ship to production about a hundred times per day, not hundreds of times per day. We've shipped continuously since the very early days of Intercom. [1]

We have a solid CI/CD pipeline meaning that every good merge to master hits production a small number of minutes later. Most of these changes are pretty small, focused and routine, adding a new button behind a feature flag, a db migration, a bug fix.

These small changes add up over time to a steady stream of highly polished features and improvements.

[1] https://www.intercom.com/blog/shipping-is-your-companys-hear...

[itwy]

Definitely a gross exaggeration.

[nullvoxpopuli]

if you have 20 people on your team, and they each have 5 PRs merged which are deployed with some continuous deployment strategy, you're already at 100 deploys in one day. :-\

[sergiotapia]

5 PRs a _day_ per engineer? What exactly are they cranking out? 1hr 30min per PR that's insane. Are these literally one-liners or extremely well defined tickets? Do your engineers work very late days?

[nullvoxpopuli]

I have days where I submit 0 PRs, and I have days where I submit 10+ PRs. It just depends a lot of things. Focus, Well defined small tickets, etc

[itwy]

Their platform is too small to have 100 merge commit per day.

[gavinjoyce]

Here's a graph showing ships / day from 2013 to 2015: https://youtu.be/NoCxHTxpmSQ?t=299

[nullvoxpopuli]

do you work there? how would you know?

[jjeaff]

Doubt it. There's a lot going on under the hood.