After graduating from college, I had back-end developer roles for the first twelve years of my career. After becoming proficient in several languages and technologies, I found Ruby and Ruby and Rails, and when I set out to do freelance work, that was my tool of trade.
After 2.5 years as a key employee at a startup, I went back to freelancing, learned about Ember.js in January 2013, and fell in love. After learning the ropes and getting a client project that used the framework, I wanted to show others the beauty and thought behind Ember.
Thus, I held workshops, presented at conferences, wrote dozens of blog posts on https://balinterdi.com , created a screencast series, and launched an Ember-related mailing list to which I sent weekly content.
I published the first Rock & Roll with Ember book in February 2015. Since then, I rewrote it twice and released several dozen updates to keep it in sync with the framework.
I've been an Ember.js consultant, trainer, and developer for all those years and worked with many clients. I still love and work with Ember, but I've also started diversifying and learning other frameworks, languages, query languages, etc.
When not working, I exercise, spend time with my family (3 kids), try to improve my chess, and take challenging hikes whenever I find time.
I've been working as a freelance Ember.js consultant at my own company, helping companies with their Ember.js apps (consulting, m...
I've been working as a freelance Ember.js consultant at my own company, helping companies with their Ember.js apps (consulting, mentoring and training developers, and developing features).
I was a contractor for Phorest, a B2B company for hairdressers and beauty salons. The teams I was in were rebuilding the old, Java-bas...
I was a contractor for Phorest, a B2B company for hairdressers and beauty salons. The teams I was in were rebuilding the old, Java-based client apps for the web, and I had a significant role in establishing good practices (both regarding Ember.js and general software development) to make sure we developed features at a sustained pace and that we weren't racking up too much technical debt.
I was one of the key employees (we were originally 4 people) at a startup where we rapidly built 4 product prototypes and then develop...
I was one of the key employees (we were originally 4 people) at a startup where we rapidly built 4 product prototypes and then developed one of them that had the most potential in the market.