Your Data is Corrupt
Rails Concerns Code Along
Introduction to Freelancing
React on Rails: Why, What, and How?
Open Source Charity Rails Apps For Professional Development
What I Learned in 7 Years of Podcasting About Ruby
Estimates that Don’t Suck
Angular for Rails Developers
Hacking the Asset Pipeline
InSpec: Making Compliance Fun
Almost every Rails database contains records that won't pass their model validations, leading to "can't happen" bugs months or years later. This talk introduces a gem that detects unsafe practices and lurking corrupt data. Come learn to recognize and prevent five ways data becomes corrupt, and maybe replace ActiveRecord validations entirely.
Rails concerns are an excellent introduction to intermediate level Ruby and Rails programming concepts. We'll start from a github clone with a simple application designed to track ice cream inventory and usage at a network of stores. Then we'll add support for CSV import and export to load and dump data on the models. Lastly we'll see how to avoid repeating this code over and over for each Model, View, and Controller by using concerns for models and controller and the proper use of .html_safe to commonalize shared code for the views. This will be a code along talk. We will start from a github pull and modify the code step by step.
Joel Schaubert is a software consultant & started programming before Microsoft had Windows. After getting degrees in EE from Minnesota and Stanford, he realized software was where all the fun was. Specializing in Rails for Healthcare he most recently finished up five years as a Consulting CTO, designing and leading the creation of the software behind bedwatch.com using Rails, AWS, Twilio, and Mirth. He lives the minimalist life with his wife roaming across America owing nothing but a Honda Element (the Red Tardis) and whatever they can fit inside it.
Have you thought about going freelance? Does it seem scary? What do you need to know or do about going freelance? Charles Max Wood was a freelancer serving clients for 5 years before going full time on the podcasts. He shares his experience to help you know if you should go freelance and what you can do to mitigate the risks.
Charles Max Wood is a podcaster, speaker, and entrepreneur. He’s an original panelist on the Ruby Rogues podcast and has helped start more than 8 podcasts and screencast series. He went freelance in 2010 and started the Freelancers’ Show in 2012.
Inspired by the Ruby on Rails Community, Justin began blogging on RailsOnMaui and working on open source. A philosophy of sharing, plus React/Webpack/Rails integration, developed into ShakaCode! A family, coding, and surfing in Maui create a healthy life balance. Find me at http://www.shakacode.com and @railsonmaui.
AgileVentures is a UK based charity that helps groups of developers form teams to work on IT projects for other charities and non-profits. The philosophy is to provide professional development opportunities for software engineers wanting to level up their technical and team skills in the context of real-world projects with real users; while also providing a useful service to deserving causes. The majority of our projects have used Ruby on Rails as a tool for quickly prototyping systems for charities, and this talk focuses on our experiences over the last three years working with the Rails stack, onboarding developers from around the world and maintaining those apps so they continue to deliver value to the end users.
Everyone is hacking everything. Everything is vulnerable. Your site, your users, even you. Are you worried about this? You should be! Don't worry, I'm not trying to scare you (that much). We have plenty of safeguards against attempts on our applications' user data. We all (hopefully) recognise Two Factor Auth as one of those safeguards, but what actually goes on under the hood of 2FA? We'll take a look into generating one time passwords in Ruby, implementing 2FA in Rails applications and the only real life compelling use case for QR codes. Together, we'll make the web a more secure place.
Charles Max Wood has been podcasting about Ruby and Rails since 2007. He, along with 4 other developers, started Ruby Rogues in 2011. It's been an exciting and wild ride. He's had the opportunity to talk to some rock stars in the programming community and has learned lessons from his co-hosts, guests, and friends.
Charles Max Wood has been podcasting about Ruby since 2007. This is his story.
One of the most dreaded questions for an engineer is “What’s the estimate on that? When will it be done?” Too often it feels as if business users treat estimates as set in stone promises that engineers must treat as blood oaths. It is easy for an engineer to throw up his or her hands and proclaim “It will be done when it’s done!” While that may be satisfying, accurate technical estimates are a real need for any business. In order for a business to be successful, it must be able to plan. Estimates feel hopeless because too often we do them wrong. There IS a way to make accurate technical estimates based on qualitative data, rather than gut feeling or guesswork. This talk will present my method for estimating technical projects (whether for development, operations, or both) that has been honed through years of experience as both an engineer and a team lead. You will walk away understanding and knowing how to communicate the difference between an estimate and a deadline, along with recognizing when someone may say one and really mean the other. You will also see a live demo of estimating a real feature piece by piece, step by step, and immediately be able to apply it to your own work. Estimates suck because most of us (engineering or business users alike) simply don’t know how to do them. Come to this talk to find out how.
Building a single-page application with Angular and Rails is not a very straightforward endeavor. How do you structure the application? How do you deploy? How do you do testing? We don’t have time to answer all these questions in depth, but Jason can share with you how to get headed down the right path to make Angular/Rails development as painless as possible.
Rails defines clear boundaries around your application. It makes easy stuff easy. Unfortunately the convention-over-configuration paradigm we've all come to love can also be dramatically constraining if you want to do something outside the framework's purview. The asset pipeline is a great example of this. It's one of Rails' best features, but also one of its most complicated features. It's difficult to understand, difficult to customize, and has a public interface that is such a moving target the maintainers might as well call it a private interface. Still, the asset pipeline and the Sprockets gem are amazingly cool, and it's hard to find equivalent functionality in other frameworks. This talk will explore how to customize the asset pipeline in a sustainable way. In other words, we'll make customizations that (crossing my fingers) won't break horribly when the next version of Rails comes out.
Cameron Dutro works on the platform team at Lumos Labs, primarily on their Ruby internationalization infrastructure and lumosity.com, a large Rails application. He’s been building stuff in Ruby for the past five years, including the TwitterCLDR internationalization library. His recent struggles with the Rails asset pipeline inspired his talk at this year’s Rails Remote Conf.
Uh oh, it’s time for a compliance audit! You know the drill, keep the auditor on the East-side of the building, make sure you only answer the questions that are asked, and remember, this only happens twice a year. Everyone wants to move faster and ship updates with higher velocity. Regulatory burdens and compliance can add extra drag on the system. Controls that live in notebooks, spreadsheets, and PDF files are difficult to verify. Scanning the production systems for compliance means you find violations when it’s too late and when they’re most expensive to fix. Compliance must be managed as code and must be part of your everyday development process if you’d like to improve compliance and increase velocity. In this talk, we’ll look at one way you can move compliance controls directly into your development process. We’ll explore InSpec, an open-source testing framework for infrastructure with a human- and machine-readable language for specifying compliance, security and policy requirements.
Nathen Harvey, VP of Community Development at Chef, helps the community whip up an awesome ecosystem built around the Chef platform. Nathen also spends much of his time helping people learn about the practices, processes, and technologies that support DevOps, continuous delivery, and high velocity organizations. Prior to joining Chef, Nathen spent a number of years managing operations and infrastructure for a diverse range of web applications. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps.