Create templates to quickly answer FAQs or store snippets for re-use.
Thank you for the links Amy 👌
Hi, Yvonnick. Thanks for joining the Ember community! I hope you will have a great time learning and sharing with others your experience with Ember.
I read that you were interested in learning good practices and architecture, in particular. In addition to the resources that Amy and Preston mentioned, I'd recommend joining Ember Discord (discord.gg/emberjs) to see how people may approach a problem in a few different ways.
Recently, I gave a talk on how Ember encourages good practices for writing tests. If you are interested, please visit crunchingnumbers.live/2019/10/11/w... !
Thank you for sharing, just join the discord server!
I will say that working with Ember.js was one of the most unpleasant experiences I had in my career. I would recommend rejecting this client unless the ask is to refactor onto a different codebase.
The problem with Ember is that it relies on tightly-coupled code, variables on a constantly mutating "this" object, which makes it near impossible to track down bugs, and almost certainly violates both the Object Oriented principles of encapsulation and the functional programming principles of no side effects.
Thank you for sharing 👍
I will not be as categorical. I have been developing apps with React since 4 years for various customers and teams. In these experiences, I struggled to set up practices like pair-programming, testing, code reviews, ... For this customer I will work for have mature teams that embraces these practices and work for public service (I used to work a lot for banks and insurance). So working with the framework you like or the one who respect the best coding principles is nice but on daily basis there are other aspects that could be taken in account when it comes to choosing a customer.
There is also emberatlas.com ;)
Feel free to add stuff
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.