On-premise servers • Poor service level ◦ Service unexpectedly stops once in a week (in my impression) • Poor UX design ◦ Specialty based sitemap • Poor authoring system ◦ Need additional development to add an image to an article! ◦ => New CMS Selection
Couldn’t catch what was said again. • Heavily depends on its context / guess ◦ Couldn’t participate in “discussions” • Recognized how bad I was at English ◦ Ability to watch movies without subtitles was required
Peter (Frontend Engineer) ◦ Some interviewees • Meetups ◦ React NYC / 2w ◦ VueNYC ▪ @youyuxi talked at Vue X’mas! • Japan engineers are competent enough ◦ With their generality / specialty ◦ Especially in this phase. https://www.meetup.com/vueJsNYC/photos/
◦ Building prototypes quickly, and prove its capability. ◦ Prove our competency. • Drawbacks ◦ Showing prototypes made participants focus on detail. ▪ Caused endless requirements list ◦ It’s important to clarify what is the purpose of a discussion ▪ Control expectations
with endless requirements ◦ Took too long to decide one thing • Making perfect system from the first ◦ No SaaS offers the perfect solution for us. ◦ “Done is better than perfect” • => Want to make a more agile team!
What were Japanese engineers for the U.S. team? ◦ Difficult to contribute in the Time Differences ▪ Does it mean there’s nothing we can do? ◦ Assumed minimum engineering resource • => Want to prove we can contribute to the U.S. team from Japan!