[lesson] "The Data on Diversity: It’s not just about being fair" by Beryl Nelson

source: 
http://cacm.acm.org/magazines/2014/11/179827-the-data-on-diversity/fulltext
http://rule-of-one.blogspot.kr/2014/10/the-data-on-diversity-its-not-just.html

lesson: 

1. create heterogeneous work environment or at least acknowledge benefits of diversity: 
• "Social scientists have shown that teams and organizations whose members are heterogeneous in meaningful ways, for example, in skill set, education, work experiences, perspectives on a problem, cultural orientation, and so forth, have a higher potential for innovation than teams whose members are homogeneous." 
• "Diversity is important to organizations that innovate, but the culture of an organization determines whether minority members of the community can thrive." 
2. be aware of my bias and unlearn them: "Know your own biases. Read some of the literature about unconscious bias and about the IAT, and then take the Implicit Attitude test5 at https://implicit.harvard.edu/implicit/."
• after taking this IAT (Implicit Aptitude Test), learned that I'm a little bit biased towards the relationship between weight and positivity. [link] 

[my note] "The Best Recruiter at Google" by Laszlo Bock (SVP, People Operations at Google) at Talent Connect San Francisco 2014

<video source: link> 

Below is what I learned from this talk; almost all of them are not my words but Laszlo's. Bolded texts are personal key lessons from this talk.

1. set a high bar for quality … and never compromise 

2. assess candidates objectively… science FTW

• no names before resume screening
• 4 criteria of a Google interview
• general cognitive ability: how well someone can solve problems, how curious they are, and how fast they can pick new things up
• leadership: no titles and management necessary; emergent leadership!
• when they see a problem when they are a member of a team, and they see the problem and step in, help solve the problem but just as importantly as soon as the problem is resolved, they step back out; they are willing to relinquish power
• Googleyness: are they comfortable with ambiguity, do they have intellectual humility (i.e. able to say, "I was wrong" when presented with new data and change their positions), bring something new and different to our mix/organization 
• role-related knowledge: do they actually have skills and knowledge to do the job we’re hiring them for
• provide clear criteria to look for
• define what best, mediocre and bad examples
• structured interviews: consistent set of questions
• situational questions: hypothetical questions ("what would you do, why did you do that, what else would you do, why would you take other actions")
• behavioral questions: describe prior achievements
• "give me an example of an incredibly difficult problem you solved, tell me more"
• what candidates consider challenging or exemplifying that attributes and how to directly relate back to the job 

3. give candidates a reason to join

[lecture] Data Analysis on Clouds by Jun Sup Lee (이준섭, KT/SW개발센터장)

Title	Data Analysis on Clouds
Place	KAIST Dogok Software Grad School Chin’s AMP Hall 103-ho
Time	October 30, 2014 5PM~6PM
Speaker	Jun Sup Lee (이준섭, KT/SW개발센터장)
Organizer	KAIST Software Graduate Program
Focus	KT's cloud solution,

I.       Message

1. impact of disruptive technology: after industrial revolution, many people lost jobs; likewise, after self-driving car, many taxi drivers may lose jobs as well
2. reason behind Google's Map business involvement: Google wanted to know where people live perhaps because the company local marketing piece of ad was missing in its product and revenue stream portfolio
3. data analysis process and examples on clouds
1. general rule of thumb: create summary-> mine data-> select machine learning method -> ?
2. ad display logic: cluster similar behaviors when ads are shown to users-> display similar ads matching the cluster
3. movie recommendation logic: vector -> choose similar users-> recommend similar movies
4. lesson from Melon: need to discern data's end results such as how users would response to product of data analysis before developing data analysis product e.g. users only care for top 10 rankings instead of relevant music to their tastes
4. new lingo: ETL (extract, transform and load)

II.      My Takeaway

1. need to work on jobs that will survive in 10 to 20 years
2. think end results before development

[lecture] 디지털 교육의 현황과 미래 - KnowRe의 미국시장 진출 사례를 중심으로”<-(translation: the present and future of digital education - a focused example on KnowRe's U.S. market launch)

Title	"디지털 교육의 현황과 미래 - KnowRe의 미국시장 진출 사례를 중심으로” (translation: the present and future of digital education - a focused example on KnowRe's U.S. market launch)
Place	KAIST Dogok Software Grad School Chin’s AMP Hall 103-ho
Time	October 23, 2014 5PM~6PM
Speaker	김서준(Simon Seojoon Kim),  노리(KnowRe)/부사장(Co-Founder & Chief Product Officer)
Organizer	KAIST Software Graduate Program
Focus	digital education

I.       Message

1. In math, each problem acts like a stepping stone for the next place
1. “Each problem that I solved became a rule, which served afterwards to solve other problems.”- Descartes
2. finding a pattern: knowledge unit, example and explanation video for each unit, content matrix for entire knowledge unit
1. knowledge unit (interpretive; formulaic: formula; computational)
2. knowledge chain
3. math problem
4. knowledge matrix
3. business development process
1. market research: market penetration in the U.S., blended learning (e.g. 47% in 2014, expecting 98% in 2020)
2. market voice: received feedback at NCTM 2012 Philadelphia
1. positive feedback: met 200 teachers, received positive feedback “want to use at school” from 84% of interviewed teachers
3. hiring: interviewed and found a US rep person at NCTM 2012 Philadelphia
4. investment: K Startup funding -> series A round funding from SoftBank Ventures Korea
5. business type: game company-like business
1. content gathering takes first before anything else
6. recognition
1. education field:  NYC DOE Gap App Challenge (1st place)
2. media: Fast Company, the world’s top 10 most innovative companies in education
7. pilot program: selected 37 out of 150 school applications, receiving 87% satisfaction
8. risk management: dealt with teachers’ concern on “no-teacher needed?” question by providing improved engagement between through dashboard (i.e. check progress status)
4. reason for choosing U.S. market: learned that societal consensus for the solution is important
5. vision for digital edu: being able to provide contents customized for individual students
6. market expansion plan: global market opportunity of B2B (schools) and B2C (students/parents) from the U.S. to East Asia
7. business model: focus on schools in the U.S., direct-consumers in Korea, Japan and China
8. role of class: information sharing and supplemental support from teachers

II.      My Takeaway

1. Like solving a math problem or learning anything, each problem/challenge acts like a stepping stone for the next progress; thus, work hard to master each step as they approach
2. KnowRe's attempt to create a content matrix platform where knowledge of STEM (science, technology, engineering, and math) is broken down to small knowledge unit and each unit is connected to each other can become the next Google's Knowledge Graph initiative to organize the world's information

[info] 정보 패턴 분석=> 연관성 도출=> 의사 결정 활용=> OKR

<source: http://premium.chosun.com/site/data/html_dir/2014/10/19/2014101902729.html?outlink=facebook> 
정보의 패턴을 분석해 연관성을 가져오고, 이를 의사 결정에 활용하는 빅 데이터 활용 좋아요.
1. 미국 샌프란시스코시 범죄 지도: 8년간 발생한 200여 종 범죄로부터 범죄 유형과 발생 지역 분석 => 경찰력 효율적 배치 => 범죄 예측 정확도 70%
2. 구글의 독감 트렌드: 전 세계 이용자 독감 관련 검색 실태 분석 => 해당 국가/지역 실제 독감 창궐 시기 예측 => 독감 예측과 실제 발생 일치
3. 빅 데이터를 활용한 식중독 예방: 12년간 부산,울산,경남 식중독 발생 이력, 원인균, 지역, 발생 음식, 날씨 분석 => 기숙사 유무, 지하수 사용 여부, 쓰레기 소각장 식당 거리 자료에 따른 학교 선정 예방 컨설팅 => 올 상반기에 작년 대비 식중독 환자 수 69.2% 줌

[HCI Trends 02 2014] for inclusive design, be the disabled instead of think disabled

Lesson learned from reading HCI Trends 2014 02



title: 장애인과 UX
author: 문태경 (이언인사이트 수석연구원, moontk@aeoninsight.co.kr)
my takeaway: for inclusive design, people involved with product development need to actually role-play the disabled instead of thinking as a disabled
"내가 장애인이라면 이라는 생각을 갖고 개발하지 말고요, 장애인이 돼서 개발을 하면 쉬울 거예요. 저 사람은 목 밖에 안 움직이니까 이렇게 하면 쉽지 않을까가 아니라, 직접 목만 움직이면서 입에다가 터치 펜을 물고 해 보면 어떤 게 더 편하다, 어떤 게 더 불편하다, 정확하게 알 수 있겠죠." - 지체 장애그룹 FGI 중에서

[Fireside Chat] Real Startup Scene in Silicon Valley

Subject	Real Startup Scene in Silicon Valley
Place	D.CAMP 6th fl.
Time	August 6, 2014 (Wed) 19:00~21:00
Speaker	Sandro Mur (CEO, Bellabeat), Willie Williams (developer, Tsumobi)
Host	AppCenter
Focus	advice on how to make global startup

1. lesson:
1. as a founder
1. need to sell vision and stories to partners, customers, investors, and other people
2. understand everything
3. don’t be afraid because companies fail a lot of times in the beginning
2. lessons from Y Combinator
1. work super hard like 24/7: learn everything, more open, share with people, do everything to survive
2. time to focus: shouldn’t be thinking anything else but your product; talk to customers all the time; focus on your product, customer, and direction
3. biggest challenge
1. hiring good and positive people (e.g. developers)- test them by giving them projects and work with them
2. managing things (e.g. customers)
3. designing UI which follows trends
4. pitching to investors
1. sell your stories: good clean pitch (don’t say too much; always say and show less and say as clear as possible)
5. find similar people who are going through the same process
1. your network grows and you will find existing solutions
6. raising funds
1. wrong
1. give unbounded time
2. right
1. build momentum (while your business is hot and popular): focus one month and then tell other investors about the investments you received from other investors
2. use networks: no need to look for new investors; instead of being introduced, you are already best friends
2. Q&A
1. globalization strategy: test in small scale (e.g. in one country) and spread
2. patent?
1. file as few as possible
2. file for defense
3. what keeps you going?
1. I have a belief that I can change things that no one can
4. why Y Combinator?: mainly for financial needs
3. Announcement
1. in 3 weeks, designers from Uber, Instagram, and Spotify will come and share wisdom
2. in 6 weeks? Growth Hacking
4. Personal takeaway
1. computer is good at recognizing patterns
2. work hard!

[lecture] 글로벌 SW 제품의 성공 조건”<-(translation) Success requirements of software products for global markets

Title	“글로벌 SW 제품의 성공 조건” -       (translation) Success requirements of software products for global markets
Place	KAIST Dogok Software Grad School Chin’s AMP Hall 103-ho
Time	June 5, 2014 5PM~7PM
Speaker	차상균,  서울대 전기정보공학부 교수 (translation) Sang Kyun Cha; Professor at Dept. of Electrical and Computer Engineering, SNU
Organizer	KAIST Software Graduate Program
Focus	disruptive technology

I.       Message

1.       Need to work on disruptive innovation changing the paradigm of markets instead of mere innovation

2.       Difference between dreamers and visionaries

1)      Visionaries can create a roadmap with successful historical background

2)      Dreamers just imagine big with no actions

3.       Strategists vs. sales people

1)      Strategists: Search for customer requirements

4.       Innovator’s Dilemma: Change in fundamentals in technology can disrupt the game of market

1)      Definition of innovation: Changing the current world

2)      Action item: Predict the unforeseen future and its requirements and prepare

5.       Crossing the Chasm by Geoff Moore [book: link]

6.       c.f. SAP was founded in 1972

II.      Takeaway

1.       Take actions in developing on disruptive technologies

[personal UX/UI review] some observations

-. Case: rusted window frame

-. Issue: bad choice of material for the frame

-. Recommendation: use low maintenance required and long-lasting materials for building components

-. Case: Beans and Barnes signs

-. Issue: no inclusion of Korean pronunciation; this can a serious issue for especially first-time customers who would like to search the name and use its services because it takes extra time for them to figure out.

-. Recommendation: include Korean pronunciation of the store name to assist people who can't pronounce the name

[personal UX/UI review] good naming for a government organization

-. case: naming of a government organization

-. positive: the name includes "service" where this place could have been just "community center"; the inclusion of the word service is a perspective changing statement. I don't know the civil servants working in this organization are aware of deep philosophical meaning of their organization naming in English, but I'd like to compliment on the person who translated "주민센터" to potentially remind everyone in the organization go back to basics of its existence. 

[conference] ‘더 나은 웹’ 웹마스터 컨퍼런스 2014 (translation: "The Better Web" Webmaster Conference 2014)

Title	Webmaster Conference 2014
Place	Time Square, Amoris Hall, Seoul Korea
Time	May 22, 2014 9AM~5PM
Speaker	이준영, 김진형, etc.
Organizer	Google, KIPFA
Focus	Open web, responsive design, search-friendly website design

<photo courtesy of Dong-Hwi Lee> 

I.       검색의 진화 (translation: Evolution of Search) [Junyoung Lee, Engineering Manager of Google Search Team]

1.       Lesson

1)      Google Fact: 50,000+ employee, 140+ language support

2)      Websites need to represent all of companies’ corporate activities

3)      Through Knowledge Graph, Google understands users’ intention and context of query

2.       Takeaway

1)      SB needs to develop intelligent search algorithms to identify users’ intention and context and provide relevant biblical results

2)      Display activities on websites

II.      소프트웨어 중심 사회에서의 공공의 역할 (translation: Public sector’s role in software-oriented society) [Jinhyung Kim, head of Software Policy and Research Institute]

1.       Lesson

1)      In software development, understand government policy

2)      In decision making, use data instead of relying on intuition

2.       Takeaway

1)      Consider using disruptive technology (e.g. mobile internet, automation of knowledge work, cloud)

III.     위키피디어와 함께하기 (translation: Ways to use Wikipedia) [ManJai Lee, Professor of Advanced Institutes of Convergence Technology]

1.       Takeaway

1)      Think of ways to use data of Wikipedia commercially due to its BY-SA license

IV.    아름다운 한글, 웹폰트로 널리 이롭게 쓰기 (translation: Beautiful Korean, ways to use Web fonts extensively and effectively) [Jihye Lee, Designer of Google Brand Studio– Interactive]

1.       Lesson

1)      Reasons for recommending web fonts instead of image fonts

①  Texts un-clickable, un-draggable, and untranslatable are hard to read on mobile devices including wearables in the near future

②  Users tend to zoom-in when browsing in mobile and tablet devices

2)      Google Chrome browser will soon to implement WOFF File Format 2.0 which reduces font capacity

3)      Web font source: http://api.mobilis.co.kr/webfonts/

4)      Try Google Web font early access: http://www.google.com/fonts/earlyaccess

2.       Takeaway

1)      As technology progresses (meaning internet speed gets faster in all countries in the world), use Web fonts on websites

V.      공공 웹사이트 혁신하기 (translation: Innovating public websites) [Kyung Geun Ma, Information Planning Dept. of Seoul Metropolitan Government]

1.       Lesson

1)      Goals of Seoul Metropolitan City website

goal category		related technology
1. One source multi-use	1.1. Support multiple devices	Web standardization, HTML5
	1.2. Utilize common contents	Resource concept, single URI
2. Open and share	2.1. Contents share/distribution	RESTful, ATOM/RSS
	2.2. Free copyright	CCL (creative commons license), meta data
3. Governance	3.1. Contents classification/evaluation	Resource concept, meta data
	3.2. Political usage of contents	Connection to web log, promotion method
4. Usability	4.1. Search function	Meta data, SEO
	4.2. Web compatibility	Web standardization
5. Efficiency	5.1. Maintenance capability	Framework, theme
	5.2. Utilization of external resource	Mash-up, open API

2)      Efforts made to create a good website

①  Utilization of open source CMS (e.g. WordPress)

②  Utilization of platform service (e.g. Twitter, YouTube)

③  Copyright reservation of content

④  Establishment of web compatibility

⑤  Configuration of search-friendly environment

3)      UK Government’s 10 Digital Service Design Principles

①  1Start with needs

②  2Do less

③  3Design with data

④  4Do the hard work to make it simple

⑤  5Iterate. Then iterate again.

⑥  6Build for inclusion

⑦  7Understand context

⑧  8Build digital services, not websites

⑨  9Be consistent, not uniform

⑩  10Make things open: it makes things better

2.       Takeaway

1)      Goal of Seoul Metropolitan City website

2)      UK Government’s 10 Digital Service Design Principles

VI.    모두를 위한 디자인 (translation: Design for the public) [Hai Kyung Min, Asia Pacific Team Manager of Google Brand Studio – Interactive]

1.       Lesson

1)      Components of the better Web: easy and fast, secured, anyone, anywhere, virtuous cycle

2)      Design for everyone

①  Understand cultural differences in using images and photos (e.g. thumbs-up may insult people in the Middle East)

②  Grid spaces for languages are different (e.g. western vs. CJK languages)

③  Be careful with line breaks

3)      Design for multi-screen: Recommended to use only one URL

4)      Mobile first: genuinely and seriously think what, why and how to start planning mobile first

①  Available gestures at mobile and tablet: touch, swipe, tilt, shake

②  Sensors at mobile devices: accelerometer, location-based API, voice recognition

5)      Design information first then move to visual: select contents and think how to organize and display them

6)      Re-think design process: use mood board instead of mock-up, review with design guide and prototype; design in browser and review

7)      Understand users: in the U.S. 75% of mobile users use mobile devices not necessarily on the go, but in their bathroom and bed

2.       Takeaway

1)      Think mobile first and plan accordingly

2)      Design information first then move to visual

VII.   Others for SB

1.       Gutenberg’s printing: 1454

2.       Martin Luther’s 95 Theses: 1517