Stephanie Gredell

I started out with jQuery and the spaghetti code. When I became more experienced and aware of best practices, I looked into front end frameworks and libraries starting with Knockout.js but ultimately ending up using Backbone. I wrote the front end piece for an internal learning platform for LinkedIn using Backbone (later refactoring it using Marionette). As LinkedIn started moving away from Backbone and more towards Ember, I researched and played with Ember. My experience is not as thorough in Ember as I haven't had many opportunities to work in it. The biggest challenge for me was learning RequireJS because at the time, I wasn't experienced in vanilla Javascript. Later, I moved to Browserify which using CommonJS module instead of AMD.

I started writing CSS when I was in high school and learning to build simple websites. Some of the biggest challenges for me was learning about cross browser compatibility (because back in my early career, I had to support IE6).

My experience has only been in the context of Adobe CQ/AEM while building custom components for LInkedIn Blogs. However, I started learning Java while at LinkedIn. Since I knew other programming languages, it was really easy for me to pick up.

I've been using Git since the very early years of my career. I'm familiar with Sourcetree and command line.

I used Backbone for a lot of my "on the whim" applications. I built controllers using FiberJS (prototypal inheritance model) to better organize my code and follow the MVC format. The way I usually structure my Backbone application is that the router would use the controller which manages views and models and the data that flows in between them. I used the event bus to trigger events globally throughout the application but more often than not, I just listened to the view/model/collection's events. I learned the hard lesson of view clean up and unbinding events. I found ways to do this (having a base view that has a remove method triggered on view.close). Eventually, I moved more towards Marionette to help reduce boilerplate.

I worked at a creative agency for a year and a half doing nothing but Wordpress. I've build a video wine course using Wordpress which including integrating FlowPlayer (this was back in 2012). I've also done a lot of eCommerce using WooCommerce in Wordpress. I've built my own plugins to help reuse functionality throughout the websites I've built at the creative agency. I'm familiar with custom meta fields and how to build an options screen. It's been a while (about a year) since I've done Wordpress work.