The document emphasizes the importance for Japanese developers to read technical documents in English rather than waiting for translations, as this approach is more efficient for gaining knowledge on new technologies. It highlights the limitations of relying on translations, referencing various programming resources and the delayed availability of translated materials. The author argues that proactive engagement with English materials can prevent developers from missing out on important technological advancements.

1. One More Thing
every Japanese developer
should Try.
presented by @mike_neck

2. Question : The case you are trying ...
a new technology whose documents are written in
English only (not in Japanese).
What would you do in this situation?
• Wait for someone to translate
the document.
• Try to read the document in
English.

3. The most Effective way ...
The most Effective way to get knowledge on a
new technology is to read a document on it in
English!
• To wait translation ?
o It's wasting time! There may be no one to
translate it. In this case do you wait
translation?
• To give up to get information?
o You are going to be looser.

4. About 97 x 3 books
• 97 Things Every Programmer Should Know
... I got it in translation.
• 97 Things Every Software Architect
Should Know ... I got it in translation.
• I had got these books in translation
because I had lower attitude toward to
be good programmer.

5. But on Project manager book...
• 97 Things Every Project Manager Should Know
o I got it in English format.
o I have searched it in oreilly.com.
o I have confidence that there may have been the
97 book for Project manager.
o So, I already know the contents of 97 Things
Every Project Manager Should Know before
Japanese translated one being published.

6. For brand new technologies
To read in English is much
Faster and Effective than to
wait translation.

7. 97 Things Every Project Manager
Should Know
I found Original one luckily.

8. Beginning JavaEE6 with GlassFish3
It's published in 2008!!! The translation for it is published
in 2012!!!

9. Test-Driven JavaScript Development
It's available in 2010. The translation is available in 2011.

10. Building and Testing with Gradle
The most elegant build tools for Java developer. But it is
not used as commonly as maven2, ant. Because there are no
systematically document written in Japanese.
No Translation
Available

11. Maven3 Cookbook
Recently this book is translated.

12. How about Maven2 ... written in
Japanese
The book is no more available now...
It's no more
available

13. In English the information is
available.
Apache Maven 2 Effective Implementation.
No Translation
Available

14. Jenkins ... you can get information.
Jenkins the definitive Guide

15. Play! Framework
It's available right now!
Sorry I don't have any interest
for Play Framework. So I don't
have this book.

16. Spring Roo ...
Oops Dr. Maruyama had mentioned it so that it wouldn't be
commonly used in Japan.
No Translation
Available

17. The Jinx for the technology that
Dr. Maruyama had been interested in is not commonly used
in Japan (Maruyama Jinx). But I think the jinx is produced
by ourselves. Had been waiting we, as developer, for more
information from Dr. Maruyama? If we didn't try the
technology, it would not have been used. We were too
relying on someone who can translate English to use a new
technologies. We call the situation "Galapagosization", as is
called NTT Docomo mobile phones.

18. In US or other country ...
There are already book for Spring Roo!!! It's becoming
commonly used technology in
foreign countries.

19. For brand new technologies
To read in English is much
Faster and Effective than to
wait translation.

20. Thank you for your attention
presented by @mike_neck