The straightforward way of applying dynamic class/attribute bindings to a component is within that component's class definition. For build-in and third-party components that would require subclassing, which is often undesirable. It's tempting to pass the bindings from a parent template without subclassing, but that works not how you think it works.

ember-concurrency is an extremely powerful and useful addon. Yet, if your only use case is fetching or sending data, there's a lighweight alternative.

Most frameworks have a concept of environment. Many developers are misusing it as a deploy target.

It's always been a dream of mine to build a product from developer for developers.

It's a relatively widespread opinion that returning a hash from the model hook is a bad practice. I believe it's not! I always return a hash, following a witty pattern, and find it very beneficial.

The new personal website is live! Though it looks humble, it's packed with Ember features and best practices. Meant to be a showcase of my skills.