What happens when a linguist learns to code? by Erica Sosa When people find out about my former career as a linguist and language teacher, they often ask if my background helped me learn how to code. I started to wonder if there was some overlap between learning a natural language and a programming language. What can we draw from the fields of first and second language acquisition that will help us become better software engineers? How can we apply the principles of language learning and teaching when training new developers? Join me as I discuss my journey from Ruby as a first language to JavaScript as a second, and stay for some code-learning tips from a former language acquisition professional. #confreaks #rubyconf2019

Containerizing Local Development... Is It Worth it? by Tony Drake Containers are the current hotness for deployment. But, how about development? They can provide a good way to manage local dependencies even if you're just writing a gem instead of an app. While writing and running code directly on your laptop has its own obstacles, using containers for development is not a silver bullet and brings along its own set of headaches. Which cases do containers make sense and how would they be configured? Containers may not be for you, but we'll go through some example setups. It'll be up to you whether or not you want to change your local setup after this talk. #confreaks #rubyconf2019

Technical Background of Interactive CLI of Ruby 2.7 by ITOYANAGI Sakura Ruby 2.7 will be released with new multiline IRB that uses a new input library Reline. I'll talk about the technical background of it. the history of terminal the Morse code typewriter teletype escape sequence escape sequence on Unix like OS Windows support GNU Readline compatible features editing modes inputrc that is a setting file I8n support too many character encodings in the world Unicode's complex tweaked specifications ...it's very difficult to understand for non-CJK people so I'll try to explain it by emoji #confreaks #rubyconf2019

Don’t Hang Me Out To DRY by Kevin Murphy Close your eyes and imagine the perfect codebase to work on. I bet you’ll say it has complete test coverage. It’s fully-optimized, both in terms of performance and architectural design. And, of course, it contains only DRY code. Surely we can all agree that this is an aspirational situation. But...do we really want that? Don’t get me wrong; these qualities are all beneficial. However, if we also think we should value everything in moderation, when should we push back on these ideals? What problems can they introduce? Let’s talk about the exceptions to some of the “rules” we all hold dear. #confreaks #rubyconf2019

Bursting at the Seams by David McDonald Our industry remains in its infancy but we've had many important contributions to how we all think and talk about design. In order to tighten the existing gap between where theory and practice meet, we need to continue to add to our shared vocabulary. With this aim, I want to underline one of the more accessible and oft-overlooked concepts from software's past: seams. Seams are easy to identify, and point to crucial incisions in our code. Learning to see code in terms of seams will improve your existing codebases, help you write better tests, and aid as you develop greenfield projects. #confreaks #rubyconf2019

Algorithms: CLRS in Ruby by Brad Grzesiak One of the most celebrated books in Computer Science academia is "Introduction to Algorithms," also known as "CLRS" after its 4 authors. It's the go-to (pun!) textbook for many intermediate college courses, and this talk will introduce some of its many wonderful algorithms in Ruby form, including: various sorting techniques, dynamic programming, and some fun graph techniques. If you want a theory-heavy lecture, this talk is NOT for you! #confreaks #rubyconf2019

Parallel Ruby: Managing the Memory Monster by Kevin Miller At Flexport, we process a lot of data. One sunny day, we decided to switch from a swarm of single-threaded Ruby processes to a wonderful new threadpool. Threads have way less overhead than processes, after all, so we could run far more. Fast forward a couple of hours and everything is on fire. Let’s talk about what went wrong, why it was the Ruby garbage collector's fault, and we did about it. #confreaks #rubyconf2019