Ben Orenstein – Adam Wathan

Topics:Putting yourself in the shoes of the person reviewing your applicationCrafting a high quality application tailored to a specific positionStanding out in a more traditional hiring process by doing something a little extraShowcasing very specific examples of your work instead of asking the person reviewing your ap

Topics include:Why deadlines are criticalUsing manual processes to avoid building features entirelyHow launching a stripped down version of your idea can help you build the right thingRecognizing when you don't need to solve a problem yetWhy you shouldn't design your entire UI up frontHow evolutionary design applies to

Topics include:The benefits of pairing with someone more experienced than youThe benefits of pairing with someone less experienced than youHow pairing helps you build things fasterWhy pairing often removes the need for code reviewHow to get started with pairing if you've never done it before Sponsors:Cloudinary, sign u

Sponsors:Rollbar, sign up at https://rollbar.com/fullstackradio to try their Bootstrap Plan free for 90 daysCodeship, check out how they performed in Forrester's latest Continuous Integration Tools report Links:Refactoring Rails, Ben's refactoring courseThe 30 Day Code Quality Challenge, Ben's free 30-day code quality

This episode is brought to you by Laracasts.Ben's blogUpcaseDHH on "Dependency injection is not a virtue"A criticism of DHH's post on Dependency InjectionDependency Management in Rails on UpcaseRefactoring by Martin FowlerUnderstanding the 4 Rules of Simple Design by Corey HainesCoupon link for 50% off your first month