Program

We've been debating on the concurrency solution of Ruby for several years. Numerous custom "evented" drivers have been built, but for most of these projects, developers are required to think in the "evented" way to get things work properly, which not only breaks the elegance of Ruby programming, but also greatly increases the complexity of the refactoring process.

We will then think in Ruby, looking for the solution to make your whole web application "evented" with great meta-programming features of Ruby language itself. So that, you could still concentrate on your business models while programming as usual, but the performance may boost to 5 times faster or more without any hesitation.

I believe most of us love Ruby, but I also believe most of us don't think Ruby it's perfect. So what'd your own version of Ruby look like if you can create your own one?

As some of you may know, I created a language called Goby about a year ago. It's largely inspired by Ruby, and looks very similar to it. But it also have some design choices different than Ruby or have some unique features that Ruby doesn't have. In this talk I'm going to discuss some important things we should focus on when designing a language. And I will also share the design choices made when developing Goby, as well as the philosophy behind these choices.

As web applications grow in scale and complexity, people start realizing that many parts of their domain-specific code do not fit neatly into Rails’ MVC structure. In recent years certain patterns emerged that try to rectify this situation and this talk tried to shed some light on them. Additionally it will explore some of the newer additions to the Ruby web development scene, like Hanami and dry-rb.

Humans and data science are flawed on their own. Humans lack the ability to process large volumes of information. Machines lack intuition, empathy, and nuance. You’ll learn how to guide users of expert-use systems by applying data science to their user experience. Layering data science within our systems allows us to take advantage of the human-touch while leveraging our large datasets. In this talk, you’ll learn the process for sprinkling data science into your applications, the challenges we have faced along the way, and how to measure the business impact.

Want to build a Bot without the hassle of provisioning and managing servers? Amazon’s got a service for that and it’s called AWS Lambda - it executes your code only when needed, scales automatically and you pay only for the compute time you consume.

There’s one problem with Lambda - it doesn’t support Ruby! Let’s checkout multiple options on how to build a Ruby Bot and package it into an executable which you can run on any machine without the need to actually have Ruby installed.

We all know what the acceptance testing is. However it is difficult to really adopt this into your real-life work. I want to show you how I introduce this technique and solve the problems.

In this workshop, you can learn the following four topics.

(1) Introduction to the data tools for Ruby (2) How to use pycall to integrate your Ruby scripts and Python's data tools (3) Using Ruby for machine learning (4) Summary and how to join the development of data tools

One of the Ruby 3 goals is "better concurrency support". I will talk about the progress report of this goal. I had proposed new concurrency abstraction at RubyKaigi 2016, RubyConf 2016. Our new abstraction is safer than Thread and can run in parallel. This presentation will introduce concepts of our new abstraction and will show demonstration with preliminary implementation.

When DevOps team was established in 2016, development teams in Rakuten Travel were working in silos. Development teams had had separate development processes (build-automation tool, release-automation tool, site-operation tool). Also the development environment which all teams used together had infrastructure restrictions and development processes which slowed down the development in the organization level.

DevOps team talked with each development teams and found issues to solve. Then DevOps team standardised the development processes by delivering software in the topic of System/Application Data Centralisation, Multiple Development Environment, High Availability, Data Visualisation, Table Definition Management. Most of our software is written in Ruby. After 2 years of DevOps activity, all development teams follow the standardised development process. Also, operational processes such as release automation and site operation are now consolidated to 1 team. As a result the productivity of our organisation improved dramatically.

In the process of developing software, DevOps team faced many issues. As many members did not have a developer background, we did not write unit-test for our Rails application. So we learned how to write rspec testcases and also introduced guard to achive TDD. Then, as the number of our Rails application increased, many duplicated codes exist such as getting server related information from cross-company internal API. So we learned to package duplicated code into rubygems and store it in internal gem repositories. When we faced a performance issue in our program, we tried to solve it by using multi-threading function. However Ruby was unfit for it and we ended up using Java instead.

Another important part of this DevOps activity was to adapt the standardised software to each development team. Development teams had their own development processes which were already efficient for them. So when we tried to adapt the software, while most development teams were supportive, some were not. In the latter case, we had to do many of the heavy lifting such as making code changes to the product code and testing products on our own. The most difficult part was actually creating testcases and executing testcases which are normally responsible by other development teams. This is mentally tough but very challenging part of DevOps activity.

In this workshop, you can learn the following four topics.

(1) Introduction to the data tools for Ruby (2) How to use pycall to integrate your Ruby scripts and Python's data tools (3) Using Ruby for machine learning (4) Summary and how to join the development of data tools

How many times did you run ruby directly except ruby -v for checking version? Ruby was the descendent of Perl, inherited many handy command line features. Such as easy file reading, various global variables and executing directly without file. Let's explore all sorts of little known Ruby Command Line features.

除了用 ruby -v 來檢查版本之外， 你曾經在 command line 直接執行過 Ruby 嗎? Ruby 作為 Perl 的接班人，延續了許多好用的 command line 功能。 像是方便的讀取檔案，各種實用的預設變數，不用檔案直接執行程式碼。 讓我們一起來探索各種鮮為人知的 Ruby 功能。

In Rails 5.1, webpacker gem now directly supports Javascript front-end framework such as React and Angular. However, I am running React on the Docker environment without webpacker gem. React has many advantages for making dynamic views. Especially, One way flow provided by React is similar structure with Rails data flow. So It's easy to understanding for server side engineers.

In this session, I will explain the purpose of using React in View, Pros & Cons.

In this workshop, you can learn the following four topics.

(1) Introduction to the data tools for Ruby (2) How to use pycall to integrate your Ruby scripts and Python's data tools (3) Using Ruby for machine learning (4) Summary and how to join the development of data tools