This article was translated from Japanese by Claude Code.
2018 is already 17% over. (How scary.)
2018年03月04日になりました。今年は残り303日です。あと83%です。
— 今年の残り日数 (@remaining_days) March 3, 2018
Continuing from last month, I’ll reflect based on what I did.
What I Did in February#
Spoke at DroidKaigi for the First Time#
I had the honor of giving a presentation about Flux at DroidKaigi.
I’ve written about my thoughts on the presentation and DroidKaigi itself in the article below.
Beyond the presentation, I also had a chance to chat with @hak at the networking event after the first day—a good memory for me personally. I often watch his sessions, and we talked about things like the matching app he’s making. I’d like to talk with him again.
Beyond that, having new opportunities to meet and chat with many wonderful people I don’t normally get to talk to through the conference felt like the best part of it all.
Let me thank the organizers once again. m(__)m
Since I presented about Flux at DroidKaigi, here’s a tangent: The other day when @magiepooh and I were having drinks at home (we were mostly laughing at a show), the conversation turned to Flux.
“Flux is getting popular,” said @magiepooh
“True,” I agreed
“Flux has some awkward points though, doesn’t it?”
“True,” I said again
“We’re still exploring this…”
(I only said “true”)
Some examples of “awkward points” might include:
When you want to manage “View state,” where should you manage it? (In a Store? Elsewhere?)
If you don’t dispatch an Action/Event but want to leave the work to an ActionCreator, where do you write that logic?
We briefly discussed this as a pair. I think new designs will emerge in the future to solve these problems. (If you think “We can make this work!”, I’d love to hear from you~)
End of tangent! Next.
Presented about Okio & OkHttp at DroidKaigi Reject Conference#
About a week after DroidKaigi, there was a DroidKaigi Reject Conference. I presented there with @stsn_jp.
Here’s my reflection blog post about this:
As mentioned in that article, I didn’t have time to prepare materials, so I was making slides right up until the event after setup.
The presentation came about on a whim—originally it was “We really should read the internal implementation of famous libraries like OkHttp and Okio, right!?” and before I knew it I had applied and committed to presenting. Then DroidKaigi ended and I thought “Wait, I haven’t actually read the internal implementation yet!?” and was breaking into a cold sweat. But after presenting, people in the audience tweeted that it was interesting, so I think they enjoyed it.
Regarding DroidKaigi Reject Conference, many people stayed after for the networking event and had fun chatting, so I’d definitely like to see it happen again next year.
Started Writing for Techbook Festival#
This April, I’ll publish a book for the first time at the Techbook Festival. A few Android engineers from the same floor at work and I are publishing a book together as volunteers.
At the festival, I’ll be writing about Okio’s internal implementation, around 15-20 pages. Since what I presented at DroidKaigi Reject Conference was really just a small portion, I plan to write thoroughly within the page limit. Since all team members are publishing for the first time at the festival, I hope you’ll be lenient with us. m(__)m
Other#
Read “Money 2.0”
Went to CloudStudyJam and touched GCP and Kubernetes for the first time
In Closing#
At the end of this month, I’ll be presenting about Flux at Droidcon Boston. The content might overlap significantly with what I presented at DroidKaigi, but Droidcon seems to have about 10 more minutes for presentations than DroidKaigi, so I’ll update my materials and try to present the parts I couldn’t cover at DroidKaigi. A chance at redemption!
After it’s done, I plan to write a blog post about the experience and reflections. I’m nervous, but I’m also looking forward to my first Airbnb experience, so I’ll take it at my own pace. That’s the summary of February!
February’s been tough~!