しまもん 

モンスター・ラボ島根開発拠点のブログ

RubyKaigi 2018(仙台)のCFPを公開します

はすみん ・2018-03-15

2018年5月31日~6月2日に仙台国際センターで開催される RubyKaigi 2018 に送ったCFP(Call For Proposals)がAcceptされた(=スピーカーに選ばれた)ので、そのCFPを公開します。Acceptされなければ黙ってるつもりでしたw

CPFの書き方の具体的なコツは、ググればもっと優秀なプログラマさんのものが見つかりますのでそちらに譲ります。

ことしのRubyKaigiには130本のプロポーザルがあったみたいです。選ばれたのは50本くらい?だと思います。

その前に

ここで本投稿の主目的を書きますがw、こんなカンファレンスにガシガシ応募する元気なプログラマをモンスター・ラボでは大募集中です!

https://www.wantedly.com/companies/monstarlab/projects

勤務地は東京、島根、中国、ベトナム、バングラ、フィリピン(セブ島!)などなどの選択肢があります。わたくしハスミもあなたのCFPがAcceptされるレベルになるようにサポートします(プログラミングよりも物書き能力のほうが自信あります...)のでぜひいっしょに働きましょう!

前提知識

RubyKaigiは国際カンファレンスなのでCFPを英語で書きました(DetailsとPitchは日本語可との情報もあります)。当日は、もちろん日本語でしゃべります。

4つの項目「Title」「Abstract」「Details」「Pitch」のうち、前の2つはRubyKaigiのページにそのうち公開される部分で、後ろの2つがふつうは非公開です。トークの内容=Details と、自分がこのトークをする価値はなんなのか=Pitch の書き方を参考にしていただければ幸いです。

CFP

Title

Firmware programming with mruby/c

Abstract

We have a new choice to write firmware for microcomputers(microcontrollers). It's mruby/c.

This talk shows how to introduce mruby/c firmware programming. And besides, my actual IoT project for Japanese Sake brewery will be described.

Since mruby/c is still a young growing tool, you will know there are several(many?) things you can help it to become better.

Details

I am developing an IoT system for a Japanese Sake brewery in Shimane, Asahishuzo famous for 十旭日(Juji-asahi). The system was delivered to actual brew work in January 2018. The devices post temperature of Sake materials in brewing, surrounding temperature, humidity and atmosphere to server. Data is displayed on smartphone app.

I will bring one of those devices and demonstrate how it works at RubyKaigi.

Creating IoT system not with rich single board computer like Raspberry Pi but with somehow poor microcomputer gives us some merits. For instance, we can narrow security issue list derived from many a malware aims at Linux or Windows platform as a target. End users, brewery workers in this case, can use simply microcomputer based device because it starts immediately right after plugged in.

That's why I use microcomputers. mruby/c was a natural selection for me and it can be for all Rubyist, too.

But mruby/c is not a perfect tool as of yet. It is hard to debug because we can neither do step execution nor look into appropriate memory address of mruby/c's variables. We should carefully draw a borderline between C language and mruby/c. My conclusion at this moment is, in short, you should not use mruby for volatile logic and should use C language instead. This may disappoint you. For now, unfortunately, writing mruby/c application is not fun contrary to our expectation for nice Ruby. So let's make it better.

I will suggest some helping-hand-scripts to reduce boring tasks such as writing binding code between C and mruby which does only giving and receiving vars and behaves only as a wrapper function.

The audience will know not only how to touch mruby/c firmware programming but also how to help the growth of its ecosystem.

Pitch

I am a programmer who mainly uses Ruby on Rails. Like almost all audience knows how splendid RoR ecosystem is, I know it as well. On the other hand, a few months ago I was exactly new to mruby/c. I fell into some traps of mruby/c because of bugs or insufficient docs and examples. Using mruby/c is difficult than I imagined.

But after the struggle, I finally delivered production code to real Sake brew work.

I guess there are still few cases where mruby/c is used in actual projects. I have one of such projects. I can show real source code to the audience, not a sample code like LED flashing.

mruby/c core team member in ITOC(Shimane Open-Innovation Center) and I often discuss for better mruby/c.

These are the reasons I should talk about mruby/c at RubyKaigi this year.

| 採用情報

城下町・松江で一旗揚げたいRailsエンジニア絶賛募集中!

Blue