42nd Monthly Technical Session (MTS) Report

42nd Monthly Technical Session (MTS) was held on January 19th, 2018. MTS is a knowledge sharing event, in which HDE members present some topics and have QA sessions, both in English.

The moderator of the 42nd MTS was Hayashi. f:id:michael-wangsa:20180202200312j:plain

First topic was Okubo's introduction on JavaScript framework Vue.js. He began his explanation on reasons we should use vue.js by showing us a video from https://vuejs.org/index.html. Then he continued with the history of technology stack evolution throughout his career. He concluded his presentation with tips and tricks on how to develop vue.js applications.


Second topic was about WebAssembly and Go by Shinohara. He began with the explanation of WebAssembly and why WebAssembly is needed. Then he proceeded with the use cases of WebAssembly. He also explained why WebAssembly is fast. After explaining WebAssembly, he went on explaining WebAssembly support in Golang. Golang support will be released with version 1.11 around this summer. He tried the Golang support for his project and it failed for several reasons. One of the reasons is there are too many TODO to support WebAssembly in Golang.


Third topic was brought by Xudong. His talk was about how to optimize memory usage within embedded system's SoC. SoC (System on a chip) has built in RAM and ROM memory for programming, but the their sizes are limited. Their sizes are so limited that he has to do some careful planning on things that really matter to be put inside the ROM and runtime execution of the program not to go beyond limited size of the RAM. He shared some of his experiences, tips, and tricks to do programming on such system.


Fourth topic was about AWS Batch brought by Doi. In the beginning of his presentation he recommended us to watch the video from AWS Re:Invent 2017 titled CMP323 - AWS Batch: Easy and Efficient Batch Computing on AWS for deeper understanding on AWS Batch. He began his presentation by explaining in simple terms about AWS Batch and showed an example of system architecture built in AWS Batch. He explained some components that are important in running AWS Batch, which are AWS Batch Definitions, Job Submission, and VPC Configuration. He stressed the important points in VPC configuration that should be enabled are MapPublicIpOnLaunch, EnableDnsSupport, EnableDnsHostnames which might not be enabled by default when building new VPC. He then showed us some demo on AWS Batch.

Here are some links that Doi recommends to start using AWS Batch:


Fifth topic was brought by Bumi, it's the continuation of his previous Elasticsearch MTS Presentation. He explained various use cases of Elasticsearch and recommendation on where to host it. Bumi began his presentation by explaining the application search feature of Elasticsearch and why we would want that. Then he moved to a real use case: operational log analytics. He explained that analyzing logs is arguably the most popular use-case of Elasticsearch because search is not only about matching text but matching everything including timestamps, app code, IP addresses, etc. Combined with its partner, Kibana, the logs can be transformed into interesting visualizations which are easy to digest for both programmers and decision makers. He mentioned three ways to host Elasticsearch:

Bumi didn't recommend building your own cluster because it might be too much of a burden for your organization. He also presented some pros and cons of using hosted Elasticsearch service between Elastic Cloud and AWS Elasticsearch Service.


Last but not least, our intern Jazman presented The Art of Storytelling. The presentation content was about his internship experience in Japan. He began his presentation with his story of new year holiday to Kyoto. He went to Kyoto using the local train with Seishun-18 Ticket and got on the wrong train on the way to Kyoto, but he managed to correct his course and reach Kyoto safe and sound. He also shared another story of his train trip when he went back from Asakusa to Shibuya but he ended up in Saitama. Then he explained the point of telling his story, everyone's story is unique and different.

He stressed several points about stories:

  • Stories connects people.
  • Stories makes people understand.
  • Stories gives people a new perspective.
  • Stories enables people to learn something new.


As usual, we had a party afterwards :) f:id:michael-wangsa:20180202200856j:plain f:id:michael-wangsa:20180202201043j:plain f:id:michael-wangsa:20180202201139j:plain

41st Monthly Technical Session (MTS) Report

41st Monthly Technical Session (MTS) was held on December 15th, 2017. MTS is a knowledge sharing event, in which HDE members present some topics and have QA sessions, both in English.

The moderator of the 41st MTS was Tanabe-san.


The first topic was "GIP Brand: Redefined" by Jazman-san. He is one of our Global Internship Program (GIP) participants. According to Business Dictionary, brand is a unique design, sign, symbol words, or a combination of these, employed in creating an image that identifies a product and differentiates it from its competitors. His task during his internship is to refresh the brands of GIP and HDE as an employer.

In order to achieve those tasks, Jazman-san is going on a 2 months long campaign on social media. Based on his analysis, there is a loss of potential applicants due to the lack of showcasing internship activities. Naturally then, his goal with the campaign is to gain more GIP applicants by showcasing internship activities at HDE, Inc. in a fun, exciting, and comprehensive way.

He went on to explain various aspects of the campaign, such as its objectives, identity (logo, title, mood and tone, color palette) target audience, framework, and timeline. He ended his session by reporting the progress of the campaign. In a relatively short time, the campaign has significantly improved the reach, post engagements, and net likes of GIP's Facebook page.


The second topic was "Basic Knowledge about Authentication" by Okumura-san. He explained several standards related to authentication and authorization. To put it simply, authentication is the process of ascertaining that someone really is who one claims to be. On the other hand, authorization refers to rules that define who is allowed to do what.

Okumura-san explained standards such as SAML, OpenID, OAuth, and OpenID Connect. In very general terms, in SAML, service providers redirect users to a predefined identity provider, which does the authentication. One of the ways OpenID differs from SAML is in the way that relying parties provide users options of OpenID providers.

OAuth is an authorization standard. Similar to SAML, service providers redirect users to a predefined identity provider. However, instead of an assertion of identity, the response from an identity provider is an access token that may grant service providers access to the identity provider's APIs on the user's behalf. OpenID Connect is a simple identity layer on top of OAuth 2.0. It allows clients to verify a user's identity based on the authentication performed by an authorization server.


The third topic was "Rust and the Web Platform" by Hugo-san. He was also one of our GIP participants. He began by explaining the concepts related to Rust itself, such as asm.js, WebAssembly, and emscripten. asm.js is a low-level strict Javascript subset. It is still JavaScript, with some performance benefits. WebAssembly is a low-level bytecode format. Recently, Rust supports compilation to WebAssembly. Emscripten is a source-to-source compiler. It allows code written in statically-typed languages with memory management to be translated to JavaScript.

According to Hugo-san, some of the main properties of Rust are safety and control. He likes that Rust has types, sets variables as immutable by default, uses modern syntax but can also be low-level, and provides validations during compilations. One downside of Rust that he pointed out was the absence of a garbage collector. Instead, it utilizes lifetimes to keep track of usage scope and object destruction. He also explained how to compile a Rust code to WebAssembly.


The fourth topic was "Our AI Overlords" by Kirby-san. He was also one of our GIP participants. AI has been advancing rapidly in recent years. In his talk, Kirby-san explained the many feats AI has achieved. He first explained AlphaGo, the first computer program to defeat a professional human Go player (in 2015). Fast forward two years later, AlphaGo managed to defeat a Go world champion. Its most recent incarnation, AlphaGo Zero, is an AI neural network with 0 human data.

DeepMind, the team behind AlphaGo, is now aiming to conquer another game, StarCraft II. The game's rich and multi-layered gameplay makes it an ideal environment for AI research. Another team, OpenAI created a bot which beat the world's top professionals at 1v1 matches of Dota 2 under standard tournament rules. Interestingly, players eventually managed to beat the bot (for now?) by way of unconventional strategies.

Obviously, AI can do so much more than win games. It can drive cars, recognize faces, reduce data center cooling bill, and even recreate Nobel-winning physics experiment. The potential of AI had a lot of people talking. Some believe AI will eventually supersede humans, which raised concerns of regulation. Still, some others believe it is still too early to regulate or worry to much about AI.


The fifth topic was "Hands on AWS Fargate" by Michael-san. AWS Fargate, introduced at AWS re:Invent 2017, is a technology for Amazon ECS and EKS that allows you to run containers without having to manage servers or clusters. In other words, it is the ECS and EKS you know, only without the need to manage EC2 instances. There's no need to manage EC2 count, ECS agent, auto scaling groups, task placement, networking, etc.

According to Michael-san, what's so good about AWS Fargate is that it makes scaling easier, integrates with load balancers seamlessly, and equips each task with its own network interface. On the other hand, Fargate is not cheap and provides limited log processor choice, at least for now. He ended his talk by demonstrating how AWS Fargate works.


The sixth topic was "QQ English in Cebu" by Tsukuda-san. He went to Cebu last month to learn English for 4 weeks. QQ English is located in Cebu IT Park. There are about 1,000 teachers in QQ English, all of which have international licenses for teaching English.

On the first day, students had a placement test. Classes started at 9 AM and ended at 6 PM. There were 8 classes in a weekday, each of which lasted for an hour. Tsukuda-san's curriculum consisted of listening, grammar, pronunciation, reading, group discussion, and more. On the last day, students had another test to check their progress.

Tsukuda-san also shared how he spent his weekends at Cebu. He went to a shooting club in Mactan and spent some time in Pandanon Island. He also introduced some Filipino foods, such as Lechon and Balut.


The seventh topic was "ServerlessConf Tokyo 2017" by Jeffrey-san. ServerlessConf Tokyo 2017 was held on November 2nd and 3rd. The first day was for workshops. In the AWS track of the workshops, participants were separated into teams and asked to create either a dashboard, chat, or dating application using only AWS serverless technology. After 8 hours of coding, his team became one of the few ones that managed to finish their application.

The second day was for the conference itself. Jeffrey-san learned quite a lot of interesting things, the first of which is Serverless Event Gateway. It allows serverless functions to communicate across different cloud providers using a set of standardized event format, using a publisher/subscriber model. Microsoft came full force to the conference with Microsoft Azure Functions, which supports JavaScript, C#, and F#. Durable Functions is its extension which allows user to write stateful function in a serverless environment. There was also a talk about serverless patterns.

Jeffrey-san was not only an audience of the conference, but he was also a speaker. The title of his talk was "AWS Lambda Pain(less): Adventures in Stream Processing". He taught the audience the high-level architecture of one of his projects and the lessons he learned from its development.


The eighth topic was "Office Tour in San Francisco" by Doi-san. The intent of this office tour is to learn how the companies in San Francisco are organized, how they run their business, and how they build successful company cultures. He went to several offices in San Francisco, like Oracle and Box. He also visited Googleplex and Apple Park Visitor Center.

Doi-san learned the most from his visit to Box' office. The office itself has many interesting features, such as cafetaria, bar, pool tables, table tennis tables, presentation halls, and more. Apparently, Box' employees regard the office as one of their communication tools. They display customers' use cases at the entrance and use customer names as room names. Box define their core values and applies them everywhere, on their products, working style, hiring process, etc. He also learned about Box' release flow and how they automate parts of their customer success efforts.


The ninth topic was "re:Invent 2017" by David-san and Ito-san. As you may have already known, re:Invent is Amazon Web services' global customer and partner conference, which is held annually. This year, the event was held November 27 - December 1. They began by explaining what Las Vegas was like, such as the weather, the hotels, and the gambling.

The impression that they got from attending re:Invent 2017 is that the world of cloud computing is shifting to serverless and container. re:Invent 2017 is considerably larger than its past iterations. There were more than 40,000 attendees (an increase of 35% from last year), 6 venues (twice compared to last year), and about 1,000 sessions. Some of the sessions they found interesting are "NEW LAUNCH! AWS Serverless Application Repository", "Deep Dive on AWS CloudFormation", "Advanced Design Patterns for Amazon DynamoDB", "Tools Won't Fix Your Broken DevOps", "Life of a Code Change to a Tier 1 Service", and "Serverless Architectural Patterns and Best Practices". Besides these sessions, they also took interests in Amazon Alexa, AWS X-Ray, Amazon Neptune, AWS Cloud9, and many more.

They also participated in some non-technical activities such as Pub Crawl and re:Play Party. There were even activities such as Tatonka Challenge, 4K Run and Harley Ride. They ended this session by giving various advice for next year's participants.

We've also written an article about AWS re:Invent 2017 on-site activities. The article elaborates on workshop, hands-on, and JAM sessions.


The day of the 41st MTS was also the last day of Hugo-san and Kirby-san's internships. We had a small event for them and gave them some souvenirs. In turn, they shared their impressions of their time working for us. Thank you very much for your contributions, Hugo-san and Kirby-san!



As usual, we had a party afterwards :)


AWS re:Invent 2017 Report: On-site Activities Such as Workshop, Hands-on and JAM Session rather than Presentations

Hi, I'm Toshi from Cloud Product Development Division. I work as a software engineer at HDE.

This year HDE sent 6 software engineers to AWS re:Invent 2017 held in Las Vegas from November 27 to December 1. In this article, I would like to share my experience from this big conference. Since many videos and slides of presentations are already available, I will focus on on-site activities I had instead of presentations which you can watch right now.



40th Monthly Technical Session (MTS) Report

40th Monthly Technical Session (MTS) was held on November 17th, 2017. MTS is a knowledge sharing event, in which HDE members present some topics and have QA sessions, both in English.

The moderator of the 40th MTS was Matsuura-san.


The first topic was an explanation of a fixed bug in one of our projects by Fukutomi-san. He noticed that his project sometimes labeled HTML emails as illegally modified. The cause of the bug was excessive newlines generated by the use of a certain email client. After removing those excessive newlines, HTML emails were no longer incorrectly labeled as illegally modified.


The second topic was "OWASP Top 10 2017" by Kodama-san. OWASP Top 10 is an awareness document written by The Open Web Application Security Project (OWASP), which represents a broad consensus about the most critical security risks to web applications. A variety of security experts from around the world shared their expertise to produce the list. Furthermore, the list is free to access for everybody. So it is very recommended to adopt the OWASP Top 10 as the first step to producing secure code.

Kodama-san also described how OWASP Top 10 2017 differs from the last one that came before it, OWASP Top 10 2013. Some risks from 2013 didn't made the list this time around, and the community decided to put some new risks in their place. Most risks stayed in the list, understandably with a change in their importance. He also explained the risk rating methodology that was used to make the list. To finish the topic, he mentioned what developers, security testers, application managers, and organization each needs to do as their next step in producing secure code.


The third topic was an introduction to one of our projects by Xudong-san. He began by explaining what the project is and why it is needed. The approach that is used to achieve the goals of the project is data-driven decision making. He mentioned the kinds of data that this project needs, how it retrieves those data, and how the software system works in general. He wrapped the topic up by reporting the project's current status.


The fourth topic was "Slack Frontiers" by Kawatake-san and Hosaka-san. Frontiers is a conference by Slack about exploring how the nature of teamwork is changing. Participants get to hear about Slack's newest products, learn how Slack improves work and workflow, and hear from customers about the ways their organizations are evolving. This year is actually the very first time Frontiers was held. The event was held September 12-13 in San Francisco.

Akane-san began the topic by explaining what San Francisco and the atmosphere of the event was like. In this event, Slack announced two new products, Shared Channels and Dialogs. A Shared Channel is a bridge connecting a company's Slack Workspace with another company's. According to Hosaka-san, Shared Channels are simple, transparent, and controllable. Dialogs, on the other hand, are forms which provide a focused workflow to quickly collect information from users. For example, during Frontiers, Slack itself used Dialogs to file in customer inquiries. They ended this topic by describing how other companies use Slack.


The fifth topic was "O'Reilly Velocity" by Bagus and Tanabe-san. Velocity is a conference by O'Reilly about building and maintaining complex distributed systems. Sessions covered themes such as capacity planning, distributed data, distributed systems, monitoring, networking, orchestration, resilience engineering, serverless, systems engineering, and technical leadership. The conference was held October 17-20 in London.

Some of the keynotes that either of them found interesting includes "Why an (Interactive) Picture Is Worth a Thousand Numbers" by Miriah Meyer and "The Evolution of Chaos" by Kolton Andrus. Some of the sessions that either of them found interesting includes "Serverless Security: What's Left to Protect?" by Guy Podjarny and "A Postmortem of Postmortems: Trends and Behaviors across Organizations" by Eric Sigler. They also shared their experience traveling to London, such as the food, transportation, and sights.


The sixth topic was "Understanding the Bitcoin Forking Drama" by Kirby-san. He is one of our Global Internship Program (GIP) participants. Bitcoin is a cryptocurrency and worldwide payment system. There are currently several Bitcoin forks out there. Hard forks bring radical change to the protocol, so new version rejects all transactions made from the older client software. On the other hand, in soft forks, new client is backwards-compatible.

He then explained some Bitcoin forks, such as XT, Classic, Unlimited, Cash, and Gold. The aforementioned drama of each forks were explained by walking us through the development of Bitcoin itself.


The seventh topic was "The Dat Project Ecosystem: Distributed and Decentralized Tools for the Open Web" by Hugo-san. He is also one of our GIP participants. Dat Project is a distributed data community, with which people can share, backup, and publish their file systems. It was created for scientists (e.g. to share data sets), but is useful for everybody.

He then explained in more detail what the protocol is like. According to him, Dat Protocol shares some similarities with others, such as Git (e.g. versioning of data), BitTorrent (e.g., peer-to-peer), and DropBox (e.g. synchronization of data sets). He also explained how to share data with the CLI tool dat. He also presented some practical applications of Dat Project, such as Beaker Browser and Rotonde (a social network).


As usual, we had a party afterwards :)



Escape Hunt and 屋形船

Working in the global team, which comprises of members located in Japan, Taiwan and Thailand majorly, it is much a rare opportunity to be interacting closely together physically solving puzzles and enjoying a dinner event like this. During the escape hunt, we were collecting the puzzles, clues, under limited time and trying to solve all of the puzzles under pressure. This is one of my first times working with a group trying to solve multiple riddles like this and the experience was not only pleasant by gratifying. I was teamed up with two of sales members; one from Taiwan and one from Thailand and one executive member and myself was working as the consulting team. I believe this team member was quite diverse and I was able to get perspectives from different members.

Initially, we were trying to collect the clues that was sporadically hidden in the room; however, everything looked suspicious and everything seemed like a clue to us. We had found an armor, several wooden cards, locks and number symbols on the mirrors. These clues do not combine and we were not able to reach unanimity between the members. In the end, we tried to grab the first hint for our very first clue and found out. After the gamemaster, the person in charge of running the game or the referee, encouraged us to look for more wooden cards have we realized that we were on the right track but lacking the wooden cards needed to proceed. When we finally collected all of the wooden cards needed for solving the puzzle, we had to match the color orders in order to come up with the combinations that would solve the numbered lock.

The opened lock led us to a whole new room and there were plenty more clues to look for. However, I was very obsessed with the left wooden cards and trying to combine the numbers on the wooden cards with the numbers on the mirror. Later have I finally realized that the numbers I have do not combine with the clues any more I should go on to look for more clues. I found out that other members were much more interested in the armor that was left aside by me and they had started building the armor. This is the reason I think team work was important-each one of us was focusing on a different clue and none of us were sure what would lead to the next clue. Finally, one of the member got a white piece of paper that he was holding, I left the wooden cards aside and looked at him afar. I saw the broken patterns on the backside of the paper he was holding, and I was reminded that a similar pattern I had found in the new room that had arrows on it too. Suddenly, I asked him if I could briefly borrow the paper and I rushed into the new room trying to recover the broken patter on the map. I found out once the patterns are matched, I could obtain the numbers that matches the arrows. The arrows allowed us to unlock a lock that enclosed a cabinet of the rest of the armors.

After the armors parts were collected, we were unable to correctly assemble the lose armor to the instructions on the page. We had to finally call the lifeline and ask for the gamemaster to help us correct the armor. This is when I realized that the armor I had overlooked was very important for acquiring the next clue. As foreigners, we were not able to fully assemble the traditional Japanese armor. However, once the armor was completed and matched with the numbers on the mirror, we were able unlock the final combination lock that leads us to the final room. The final room required us to solve an arithmetic calculation.

In the end, compare to the average group, we did not score very well-have we not only passed the time limit, but also asked for more clues than the average team. However, I believe that as four members that were not so used to working closely together, we worked together immediately well. We have only exceeded the time limit by a minute, but we only have four members compared to the other groups. As a tradition, we had took a few photos and received our certificate to celebrate our victory. Unfortunately, there were not many photos that we could take during the escape; as a result there was only the picture at the bottom.

f:id:ted-chou:20171108193145j:plain After the escape hunt, we went to a dinner on a boat party for a group of 15 members. The boat seemed quite big for our party and I hoped that we could have more members than present. However, it is indeed a rare opportunity to enjoy a yagatafune to such a small party. The main theme of the party was the farewell of our manager from the global team and welcoming a new manager into the team. However, since we rarely get together, I believe it was also a bit more difficult to find the common topic to talk among all of the members, luckily, beer and sake made everyone more talkative. The speech given by the ex-manager was also compelling. There were members that made a card for our ex-manager and handed over during the meeting and the dinner ended with lots of singing and laughter.

f:id:ted-chou:20171108193157j:plain A big 屋形船 with only about 15 members.

f:id:ted-chou:20171108193209j:plain Farewell of the ex-manager.

f:id:ted-chou:20171108193129j:plain Singing and laughter.

FY2018 Global Training - 文化を超えたチームワーク

毎年恒例HDE グローバルメンバーのトレーニング、今回は浅草にある「ESCAPE HUNT」に行きました。「ESCAPE HUNT」は全再開各地にグローバル展開(HDEと同じく)しているリアル体験型脱出ゲームができる場所です。参加者は14人3チームに分かれて、それぞれ三つのステージに挑戦しました。 (ステージ内は撮影禁止となってましたのクリア後の写真をつけておきます o(*>Д<)ゝ) f:id:seisho-jo:20171026170803j:plain

僕たちは日本、台湾、タイからなる五人チームでステージ「禅」に挑戦しました。部屋の中は禅という名前の通り和式づくりになっていました。部屋のあちこちにナンバーロックが仕掛けてあり、それらを解き、板のカギを四つ集めることでこの部屋を60分以内に脱出するというルールです。ナンバーロックの四桁の番号に関するヒントは部屋のあちこちに隠されてあり、チームが一丸となり、協力して解いていかないとなかなか制限時間内に脱出成功できない仕組みになってます。 f:id:seisho-jo:20171026172530j:plain

部屋に入ってから僕たちは総員でヒントになりそうなものを探しました。最初に見つけたものは各自1番から3番が書かれた石と、紫色の光を放つ懐中電灯。部屋の中には5x5マスで石を並べる台と屋とその的がありました。石を並べる台には同じ番号の石をこの5x5マスの中に置き、対同士を線でつなぎ、それらの線でマスをすべて埋めるという指示でした。これだけでは何もわからなく、僕たちはさっそくヒントを使うことにしました。そこで得られたヒントは四種類ある矢とその屋の形が彫ってある的に注目するとのことでした。そこでそれらを合わせて得られた四桁の数字をナンバーロックで回しても一つも開けることができず、結局もう一度ヒントを呼ぶことになりました。ここで何かまた我々が全く気づかなかったほんとが出てくるのかと思いきや、ただ矢の数を数え間違えてるだけでした(笑) f:id:seisho-jo:20171026172627j:plain

ここから先はコツをつかみ、順調に部屋のあちこちから得られるヒントをもとに次々とナンバーロックを解いていき無事50分程度でクリアすることができました。 f:id:seisho-jo:20171026172651j:plain

この脱出ゲームは所詮ゲームと考えがちですがが、色々と学ぶことがありました。 他人とチームを組んで何かをやるときにに、やはり欠かせないものが「チームワーク」だと改めて思わされました。「三人寄れば文殊の知恵」というように多人数で協力すれば、一人では解けない問題もみんなとなら解ける、それこそがチームワークの一番素晴らしく最強のところだと思います。そも一朝一夕で生まれることはできず、月日をかけてともに努力し支えあって育んでいくものだと思いました。このトレーニングもまだその長い長い道のりの入口でしかありません。


P.s. このトレーニングの後には日本会社ならではの屋形船の会食でした!

f:id:seisho-jo:20171026174651j:plain f:id:seisho-jo:20171026174614j:plain f:id:seisho-jo:20171026173029j:plain


HDE Global Sales Training: Escape Hunt !!

Sawasdee ka~ Hello everyone! I’m FAI from Thailand, a global member from HDE, Inc. in Japan. I’ve been working here as a part-timer in HDE since June 2014 and finally joined as a full-time employee recently!

Many people may have heard about an Escape Room. For those of you who has no idea what it is, escape room is actually a game in which a group of players will be locked inside a room and they will have to solve a series of puzzles in order to unlock the room and escape. Hints are usually hidden within the room. Many places provide themes to the room and integrate story line to the game itself to add the spice for the players. Sounds fun right? I, for one, have always wanted to try out the escape room, but never had a chance until just last week…


Our company decided to take us on an adventure to an Escape Hunt. You’re probably asking in your head, ‘Wow that must be nice to be working in a place where they would bring you out for a game activity’. Well, YES, it’s pretty awesome! But seriously, not only the Fun that we have had, but there are other things you can obtain from the game itself. One thing for sure is the value of teamwork that would be required for everyone to team up in order to solve the mystery and pass the game lock. But you’ll find that there are more to that. The main objective of this event is also actually a training for our Global members. So….Here goes the story of our Escape Hunt !!


On 19th October 2017, a totally normal working day in Japan, all of our global members left the company early evening and headed to Asakusa, where the Escape Hunt is located. As we reached the location, we were separated into 3 groups. My group has 5 team members, and we were assigned to an escape room called “Zen”. (No phone is allowed inside so I couldn’t take any picture of the rooms inside)

As we entered the room, we were so confused on what to do and where to start. The only instruction that was given in the beginning was that we will have to unlock the room by using hints hidden around the room. We can call for hints from the game master. Each hint worth 1 minute. And we have 60 minutes to escape.

In my group, everyone has ZERO experience in the game (O___O). We only know that Okay we will have to escape from the room, but like HOW!?


This picture is my group after we have finished the game already. Anyway, inside the room, there were two hidden rooms that we had to unlock to get the next hints and so on. I would say it was really hard in the beginning to figure out what to do and what to look for.

After spending about 10 minutes in the first room, plus calling for one hint from the gamemaster, we were able to figured out the first puzzle and unlocked the key to the second room. From here, we started to get the sense and logic of the game itself. After gaining experience from the first puzzle, we’ve learned that the first thing you have to do is Observe the whole room (<.___.>), and Find any marks or symbols that you feel it may lead you to the next hint.

I’ll give one example of the puzzle to give a better picture of how the game works. This puzzle was the easiest one to be noticed. So as we entered the 2nd room, we’ve found something similar to this on the wall. (I drew this so it’s not exactly how it was, but just to give an idea hehe).


After scanning the room for quite a while, we found that we can also find these symbols embedded into two Japanese rugs that are hung on the wall of the room. Well, here are all the hints we got for this puzzle, what is your next guess? (Hmm..)

The answer is to count all the symbols on those rugs and put it in the equation above to get the passcode to unlock the next puzzle. (Could you guess that? haha) This one was actually the easiest one to solve so we didn’t take much time to figure out after observing the whole room for a while.

You might feel that this sounds easy, but most of the puzzles have hints hidden throughout different places and rooms. There are overall about 6 or 7 puzzles and some required hints from different rooms. Hints for the last puzzle (I would say the hardest one to solve) are dropped throughout the whole walkthrough of the game. The game itself requires players to be observant and attentive at all times, and most importantly cooperative.


Since we were given only 60 minutes to escape the room. After realizing what needs to be done, we have to be quick in solving the puzzle. That’s where teamwork comes in. For instance, the example of the puzzle I’ve given above. It took us only about 3 minutes to figure what to do next. It’s the counting part that takes time. Here, we have to come up with a strategy and assign each team member each task. For our group, we assigned four people with symbols for them to count the number of symbols that appeared on the rugs, and one person record down the number to do the calculation.

To dig deeper, I believe that not only cooperative skill, but the trusts developed among members are also fairly important. Some puzzles were quite complicated that sometimes we are not sure if our direction of solving the problem is actually the right one or not. Since there are many possibilities to achieve the solution in a short amount of time, I believe it is essential to act right away once the decision has been agreed among members.


Anyway, to sum up our activity, Escape Hunt has been a fun and learning experience for all of us. We all have gotten to know other members in the group better within just this 60 minutes. We can all see that each of us has different abilities that added up to a great teamwork. Some are highly intuitive, some are great at logic, some equipped with good observation, some have high leadership, and some are great supporters.

But the best thing is that my group became the first group to solve the escape room within 37 minutes, and we are so proud of ourselves!!! HAHAHA


Hope you enjoy my article. Tune in next time~ : )