Check out Jared's talk above, and follow along with the transcript below.
Transcript of "A Backend Engineer's Vue of Front-End Development"
Jared Knipp: Hi, I'm Jared Knipp. I'm a staff software engineer and technical lead here at Spreedly. I recently had the opportunity to lead development on the customer experience team building customer facing applications, but I've primarily been a back end engineer throughout my career, so it was a big change for me to shift to more of a front end development focus.
Jared Knipp: A quick background of the customer experience team ... There we go. Okay. The team was originally formed to focus on customer facing applications, where Spreedly has traditionally been a back end focused engineering group. One of customer experience's core objectives was to consolidate multiple existing applications into a single tool that we called Dashboard, which we hope one day will be our primary customer facing application.
Jared Knipp: Next we looked at build tools. Our Phoenix application was originally built using Brunch, but we also considered using Gulp and Grunt, but the Phoenix and Rails communities were moving to Webpack as their default, so we made the decision to use Webpack as well.
Jared Knipp: My big takeaway is that front end development doesn't have to be mysterious and scary. Define your tooling needs ahead of time and be intentional in picking the right tool for the right job. If you'd like to talk more about our front end tooling decisions, our challenges in dashboard or payments in general, please come find me. Thank you.