In 2017, James C. Davis moved to Charlottesville, Virginia to work at a non-profit tech company that used Ember in their original Saas platform. While James had dabbled in Ember previously, an ask to reimplement the front-end in Ember, this time using TypeScript, proved challenging. 

At the time, a few engineers were using TypeScript in Ember, but the open source framework James worked on became the de-facto reference point for projects in Ember types. And the unofficial group of engineers collaborating on the project has become the official Ember TypeScript Core Team.

Today, James works at e-commerce company Salsify with a front-end all in Ember TypeScript. Although setting the standard for using TypeScript in Ember, James believes there's a time and a place for types. Plus, he may have a solution for Robbie's monorepo grievances. 

In this episode, James talks with Chuck and Robbie about his struggles and triumphs perfecting Ember TypeScript, his real thoughts on monorepos and functional programming, keeping APIs private, and why developing Glint was a type checking necessity.

Key Takeaways

Quotes

[17:58] - "One of the cool things about the way TypeScript is done now with Babel is we can write stuff in TypeScript and we can use Babel to basically strip out all of the type annotations and just produce JavaScript." ~ @jamscdavis [https://twitter.com/jamscdavis]

[19:38] - "Basically at this point, the only really useful thing that you need inside ember-cli-typescript is its blueprint which is different from the blueprints that generate components and Ember things." ~ @jamscdavis [https://twitter.com/jamscdavis]

[21:53] - "The bigger and more complex your project is, the more that [TypeScript] helps you." ~ @jamscdavis [https://twitter.com/jamscdavis]

Links