I write Engineering Topic weekly...?

Blog of web engineer at Tokyo. [Japanese version] http://taichiw.hatenablog.com/

I could had session at RakutenTechnologyConference2012 #rakutentech

I got chance of giving speech titled "10% Rule - Challenge for Making Innovative Team -" at Rakuten Tecnology Conference 2012.

[Here is my slide deck]
http://www.slideshare.net/TaichiWatanabe/10rulerakutentechnologyconference2012
[Movie]
http://www.youtube.com/watch?v=q2U3xhPdCxs

It was first time for me having my session at such big conference.
Also,

I spoke in English!

It was so big challenge for me, and I could get big experience.
I appreciate everyone who gave me such chance.

So, I reviewed what I felt and wrote down them.

[I could make German laugh]
It was one of my success!

I used my picture which were taken at Oktober Fest, Tokyo for my introduction slide.
(Originaly, Oktober-Fest is a German festival.
 But recently, it takes place in Japan too)

f:id:taichiw:20121022143145p:plain


When I showed the photo, a man suddenly laughed.
It seemed He was from Europe or North American continent.

So, I asked to attendee.
"Is anyone from Germany?"
Then, the man raised his hand.

I had never imagined that my photo given me a chance for making German laugh!

[About English]
There were both good things and bad things.
For me, it was not first time giving session in English.
But I had never given speach to attendees outside of my company.
Of course, they were not familiar with my company's internal situation.
I needed explain to such guys in English. It was big challenge for me.

Fortunately, attendee could make sense my presentation.
But, at question and answer time, I felt how my English was poor.
Actually, I couldn't hear someone's question.
I'm so sorry to those attendees.

I need to improve my hearing skill more and more.

[About Question & Answer]
Not only English, also my Q&A skill was not so good.
I sometimes spoke too much as answer.
It was not clear.

[T-shirt]
Because I want for attendee of my presentation to notice me at beer bash,
I made original T-shirt.

f:id:taichiw:20121021233205p:plain


And actually, some guys called to me at beer bash.
Not only Japanese, also in English.
It's my success.

Anyway,
I've gotten grate experience by my presentation.

Thank you!

I felt "Agile is strong to change"

Last year, I was given training of Agile at San Francisco.
After that, I have been trying to use some method of scrum to small project that 1 or 2 people are assigned, for preparing big project it will start at April.

Last week, I progressed a project with my colleague.
This project was estimated it needs 2 month.
We devided this project to each 2 weeks sprint and this week was end of 1st sprint.

But suddenly, by some reason, both of us had been assinged to other project,
and it was decided other guys will progress this project.

The project was finished only quarter of whole.
If such things happend in past days, I couldn't take over remain tasks to other member easily.
Because it was middle of development, the program was incomplete and other guys would feel hard to read it.

But this time was difference.
Since we divided our project to each sprint, our project would be "completed" at the end of week.
It was not enough as service. But it was "perfect" as system.
So we could take over our code to other guys easily.

That time, I felt "Agile is strong to change".

Developers Summit 2012 #devsumi Mr. Yusuke YAMAMOTO [7 secrets for Engineer to service in the future by difference] (【差別化で未来を生き抜くエンジニアの7つの秘訣】 山本 裕介 氏)

I attended Developers Summit for the first time.

Now, I wrote feedback of this session.

Yusuke YAMAMOTO [7 secrets for Engineer to service in the future by difference]   (【差別化で未来を生き抜くエンジニアの7つの秘訣】)

In this session, Mr. Yamamoto said "7 secrets".
I agreed especially these 3 secrets.

  • Transmission of Information
  • Open Contribution
  • Language


Actually, my basic attitude is "Transmit our information openly!".

Transmission of Information

Gathering Information is surely important.
But "Transmission of Information" make "Gathering Information"
because if we transmit something, the expert may find it and teach us more things.

Open Contribution

I think this is related to previous thing.
The more we contribute openly, the more we can make difference.
So, contributing to group is better than doing to only own project.
Doing to whole company is much better than them.
And, doing to whole country is better, and further more, whole world is the best.

Language

For contribution all over the world, English as common language is so important.
Because of this reason, I'm trying to write this blog in English.


I have believed that Engineer's Growing need Output.
I could trust my opinion by this session.