[THREAD] It's a new year, and I'm so excited to see what's coming for us here at @LinkedInEng! My team has so many incredible #EmberJS projects on our roadmap, and 2022 is looking to be a huge year.
Prepare yourselves for a thread...
TLDR: We're hiring, come join us!
1/
What do we do, you might ask? Well, my team is called "LTS UI Infra", which means that we're focused on enabling product teams within LinkedIn Talent Solutions (LTS) to ship applications faster and with higher quality by empowering them with the right set of tools. 2/
Jun 3, 2020 • 14 tweets • 5 min read
A thread on JavaScript technology, application architecture, frameworks, and #EmberJS:
When it comes to choosing your technology stack for web applications, your personal philosophy of architecture design comes into play. I want to talk a little about my perspective.
1/11
Some developers are tinkerers. They really enjoy being an architect of *things*. It's a great feeling to point to something and say "I designed that myself!". Everyone has a different level of tolerance for how deep they're willing to go to build bespoke architecture.
2/11
May 28, 2020 • 10 tweets • 6 min read
@Wellington_Tds@garrickcheung One of the biggest problems with the route-action helper is that it becomes very difficult to track the flow of data in your application. Data Down Actions Up exists to be a predictable flow of data through every level of your application. route-action allows you to bypass it.
@Wellington_Tds@garrickcheung The reason this is bad is that you now have to reason about where an action is going. Let's say you have three levels of nested routes in your application and 10 levels of nested components. You put a route-action on the leaf component (level 10). Where does that go? Which route?
