Math in Machine Learning / PCA and SVD with ApplicationsKenji Hiranabe
Math in Machine Learning / PCA and SVD with Applications
機会学習の数学とPCA/SVD
Colab での練習コードつきです.コードはこちら.
https://colab.research.google.com/drive/1YZgZWX5a7_MGA__HV2bybSuJsqkd4XxD?usp=sharing
Graphic Notes on Introduction to Linear AlgebraKenji Hiranabe
Graphic Notes on Introduction to Linear Algebra authored by Prof. Gilbert Strang.
This is an idea for visualization to better understand linear algebra.
If you want a PowerPoint version, feel free to let me know, I'll share it with you.
Math in Machine Learning / PCA and SVD with ApplicationsKenji Hiranabe
Math in Machine Learning / PCA and SVD with Applications
機会学習の数学とPCA/SVD
Colab での練習コードつきです.コードはこちら.
https://colab.research.google.com/drive/1YZgZWX5a7_MGA__HV2bybSuJsqkd4XxD?usp=sharing
Graphic Notes on Introduction to Linear AlgebraKenji Hiranabe
Graphic Notes on Introduction to Linear Algebra authored by Prof. Gilbert Strang.
This is an idea for visualization to better understand linear algebra.
If you want a PowerPoint version, feel free to let me know, I'll share it with you.
This document appears to be discussing different approaches to software design such as "Big Design Upfront", "No Design Upfront", and the "sweet spot" in between. It references several sources on software design including papers by Barry Boehm and Michael Keeling. It also includes graphs showing the relationship between design effort and quality. Overall, the document seems to be exploring different levels of upfront design activities and their impacts.
This document discusses applying agile methods in the automotive industry. It notes the differences between logistics in startups versus large automotive companies. It suggests that agile can be used throughout the automotive organization, from product owners to CxOs to suppliers. Challenges include integrating agile with existing processes and standards in automotive like AUTOSAR and ensuring safety. Emerging technologies like electric vehicles, advanced driver assistance systems, and automated driving require new approaches.
My talk at devLove X June 23.
Around 2004, we were having hard times in propagating Agile in Japan. At that time, I was thinking about how you can use Agile practices for better team work. -- I named it "Project Facilitation".
Nonaka Scrum - The New New Product Development Game, SECI model, The US Marin...Kenji Hiranabe
1. The document summarizes Nonaka's work on knowledge management and organizational patterns that influenced the development of agile and lean methods like Scrum.
2. It discusses Nonaka's SECI model of knowledge conversion and his concept of "phronetic leadership" as well as how his ideas influenced early implementations of Scrum and the Agile Manifesto.
3. Several frameworks are compared that draw from Nonaka's work, including the U.S. Marine Corps' approach to command and control, Toyota's lean production system, and Google's use of self-organizing teams.
This document provides an overview of lean and agile concepts as they relate to software development. It discusses key ideas from influential thinkers like Mary Poppendieck, Jeff Sutherland, Ikujiro Nonaka, and others. Some of the main topics covered include lean software development principles, agile frameworks like Scrum and XP, the SECI model of knowledge creation, and how Toyota's production system and lean manufacturing concepts have been applied to software. The document also references several important books, papers, and models that have shaped agile and lean thinking over the past few decades.
Mob programming and the power of flow agilejapan 2018Kenji Hiranabe
The document is a series of numbered lines dated 7/31/2018 without any other text. It appears to be a placeholder or template for a future document rather than containing any substantive information in its current state.
1. The document discusses concepts from agile software development and lean product development. It references ideas from figures like Jeff Gothelf, William Gibson, and Dee Hock.
2. It emphasizes outcomes over outputs, balancing agility with safety, and creating psychologically safe environments for teams through practices like tailboarding.
3. Key principles discussed include focusing on the customer experience, encouraging contribution from all team members, making iterative improvements through testing, and responding quickly to change.
This document appears to be discussing different approaches to software design such as "Big Design Upfront", "No Design Upfront", and the "sweet spot" in between. It references several sources on software design including papers by Barry Boehm and Michael Keeling. It also includes graphs showing the relationship between design effort and quality. Overall, the document seems to be exploring different levels of upfront design activities and their impacts.
This document discusses applying agile methods in the automotive industry. It notes the differences between logistics in startups versus large automotive companies. It suggests that agile can be used throughout the automotive organization, from product owners to CxOs to suppliers. Challenges include integrating agile with existing processes and standards in automotive like AUTOSAR and ensuring safety. Emerging technologies like electric vehicles, advanced driver assistance systems, and automated driving require new approaches.
My talk at devLove X June 23.
Around 2004, we were having hard times in propagating Agile in Japan. At that time, I was thinking about how you can use Agile practices for better team work. -- I named it "Project Facilitation".
Nonaka Scrum - The New New Product Development Game, SECI model, The US Marin...Kenji Hiranabe
1. The document summarizes Nonaka's work on knowledge management and organizational patterns that influenced the development of agile and lean methods like Scrum.
2. It discusses Nonaka's SECI model of knowledge conversion and his concept of "phronetic leadership" as well as how his ideas influenced early implementations of Scrum and the Agile Manifesto.
3. Several frameworks are compared that draw from Nonaka's work, including the U.S. Marine Corps' approach to command and control, Toyota's lean production system, and Google's use of self-organizing teams.
This document provides an overview of lean and agile concepts as they relate to software development. It discusses key ideas from influential thinkers like Mary Poppendieck, Jeff Sutherland, Ikujiro Nonaka, and others. Some of the main topics covered include lean software development principles, agile frameworks like Scrum and XP, the SECI model of knowledge creation, and how Toyota's production system and lean manufacturing concepts have been applied to software. The document also references several important books, papers, and models that have shaped agile and lean thinking over the past few decades.
Mob programming and the power of flow agilejapan 2018Kenji Hiranabe
The document is a series of numbered lines dated 7/31/2018 without any other text. It appears to be a placeholder or template for a future document rather than containing any substantive information in its current state.
1. The document discusses concepts from agile software development and lean product development. It references ideas from figures like Jeff Gothelf, William Gibson, and Dee Hock.
2. It emphasizes outcomes over outputs, balancing agility with safety, and creating psychologically safe environments for teams through practices like tailboarding.
3. Key principles discussed include focusing on the customer experience, encouraging contribution from all team members, making iterative improvements through testing, and responding quickly to change.
23. ⾃分たちのXPへの道を楽しむ。
“Appreciating Your Way to XP”
Kent Beck, Three Rivers Institute, 訳: 平鍋健児
http://objectclub.jp/community/pf/AppreciatingYourWayToXP
@kakutani の discord コメントにヒントを得て。
24.
25. 1. 最悪の問題を選ぶ。
2. XPを使ってそれを解決する。
3. その問題が「最悪」でなくなったら、これを繰り返す。
—Extreme Programming Explained, 第一版
このやり⽅はXP本の第⼀版から引⽤したものだが、変化を起こすための⼯学
的アプローチだ。すなわち、問題を⾒つけ、それを解決する。
⾃分たちの良いところを認識することからはじめるXP
“Appreciating Your Way to XP”
Kent Beck, Three Rivers Institute 訳: 平鍋健児
http://objectclub.jp/community/pf/AppreciatingYourWayToXP
47. XPは過激さを失ったか
“ちょっと⻑いが、今朝のKent BeckのXPメーリングリストへの投稿を引⽤、要約した
い。このメールは、「XPは第⼆版になって、その過激さを失った」というスレッドへの
回答になっている。”
RE: [XP] Do it by the book
From: Kent Beck
Date: Wed May 2, 2007 1:32 am
XP2nd になってXPは「ダイヤルダウン」した、という意⾒をよく聞く。1stよりソフト
に、柔軟になったといわれるのは嬉しいことだ。2ndが攻撃性を⽋いているのは意図的
だ。ぼくのゴールは、「価値」(value)を基礎にした「原則」(principle)を活⽤すること
で、できるだけアジャイルになること。「実践項⽬」(practice)のチェックリストを
作ってしまっては柔軟性を失ってしまう。実践項⽬は外的要素との重ねあわせだ。価値
と原則に沿って⾏動することで柔軟性が増すが、⾃⾝が意識を持つことが必要だ。よい
考えをよく実践するには、強制に頼ってはいけない。第⼆版では、実践項⽬チェックリ
ストを埋めるより、⼈と周囲の状況により注意を払うように重きを置いている。
XPは、第⼀版の「本の通り」できるかもしれないが、そのやり⽅では、リスペクト、ビ
ジネス全体、説明責任、プロセスと結果に対する責任、の観点が抜ける。「チーム全体
でビジネス価値を⾼めること」は、「⾃分⾃⾝がよいプログラマであること」よりも
ずっと難しい。