16格筆記讀書法
•Download as PPTX, PDF•
2 likes•2,122 views
20170414 在公司內部分享給同事，說明xdite 提的快速讀書方法的做法、原理、和我的嚐試經驗。
Report
Share
Report
Share
Recommended
如果你閱讀，那你一定要知道的「讓閱讀變簡單的3種方法」
如果你閱讀，那你一定要知道的「讓閱讀變簡單的3種方法」
誰說一本書全部都要看完，才叫看書！
別再被這種思考邏輯給限制自己！
翻開書後，開始好興奮，看一陣子之後，就看不下去了！
導致你的書越積越多，遲遲看不完的窘境！你有這樣子的症狀嗎？
其實閱讀是很簡單的！轉換心境、換個方式，從新詮釋你的閱讀思維，讓閱讀這件事情，不是壓力而是從書中得到更多！
黑白書生｜用簡單讀智慧
用全部的誠意為每本書，寫下每一個字/做每一個設計
『訂閱』黑白書生，你的支持是我分享最大的動力
＃黑白書生 ＃黑白講 ＃專業書評 ＃黑白書評
〔黑白書生〕粉絲團：https://goo.gl/O4b9cu 即時分享新知識
〔黑白書生〕部落格：http://www.bwscholars.com 分享文章創作
〔效率實驗室〕粉絲團：https://goo.gl/e0s1El 分享提升效率實驗
關鍵字：黑白書生,效率實驗室,閱讀的簡單分法,增加閱讀效率
李家同《大量閱讀的重要性》
為什麼需要大量的閱讀??
基礎得靠閱讀來奠定，大量閱讀，是基礎教育的起點
每次在基測、學測過後就會開始檢討"現在學生的作文能力越來越下滑?"
但充其量只是在陳述表象，而不去深入探討根本的原因在哪裡?
是不是不只不會作文? 而是連題目都看不懂，或是題目理解錯誤才會答非所問，
造成這種"閱讀障礙"的根本其實就是"缺乏大量的閱讀"
李家同教授近年勤於走訪各地演講，不斷倡導大量閱讀的重要性，閱讀需要練習，不可能憑空學會。
《大量閱讀的重要性》一書則是延續他對基礎人文教育的重視和關懷。
「閱讀應該是不受任何的限制，是隨興自在地看自己想看的書。小朋友的閱讀不夠，國文和作文就不好，連帶的數學也一定不好，
因為抓不到文章的主旨，也看不懂題目。普通常識不可能都來自於課本，一定要大量的閱讀才有助於提升能力。」──李家同
20180717 Introduction of Seamless BLE Connection Migration System (SeamBlue)
(1) SeamBlue is a framework that enables seamless Bluetooth Low Energy (BLE) connection migration for unmodified IoT devices between multiple gateways.
(2) It uses static program analysis to automatically identify the state variables needed to capture a snapshot of the BLE connection state, avoiding manual code inspection.
(3) Upon a device moving out of range, the current gateway extracts the connection information, disseminates it to candidate gateways, and the new gateway can then recreate the connection state and continue serving the device without disrupting the connection.
Recommended
如果你閱讀，那你一定要知道的「讓閱讀變簡單的3種方法」
如果你閱讀，那你一定要知道的「讓閱讀變簡單的3種方法」
誰說一本書全部都要看完，才叫看書！
別再被這種思考邏輯給限制自己！
翻開書後，開始好興奮，看一陣子之後，就看不下去了！
導致你的書越積越多，遲遲看不完的窘境！你有這樣子的症狀嗎？
其實閱讀是很簡單的！轉換心境、換個方式，從新詮釋你的閱讀思維，讓閱讀這件事情，不是壓力而是從書中得到更多！
黑白書生｜用簡單讀智慧
用全部的誠意為每本書，寫下每一個字/做每一個設計
『訂閱』黑白書生，你的支持是我分享最大的動力
＃黑白書生 ＃黑白講 ＃專業書評 ＃黑白書評
〔黑白書生〕粉絲團：https://goo.gl/O4b9cu 即時分享新知識
〔黑白書生〕部落格：http://www.bwscholars.com 分享文章創作
〔效率實驗室〕粉絲團：https://goo.gl/e0s1El 分享提升效率實驗
關鍵字：黑白書生,效率實驗室,閱讀的簡單分法,增加閱讀效率
李家同《大量閱讀的重要性》
為什麼需要大量的閱讀??
基礎得靠閱讀來奠定，大量閱讀，是基礎教育的起點
每次在基測、學測過後就會開始檢討"現在學生的作文能力越來越下滑?"
但充其量只是在陳述表象，而不去深入探討根本的原因在哪裡?
是不是不只不會作文? 而是連題目都看不懂，或是題目理解錯誤才會答非所問，
造成這種"閱讀障礙"的根本其實就是"缺乏大量的閱讀"
李家同教授近年勤於走訪各地演講，不斷倡導大量閱讀的重要性，閱讀需要練習，不可能憑空學會。
《大量閱讀的重要性》一書則是延續他對基礎人文教育的重視和關懷。
「閱讀應該是不受任何的限制，是隨興自在地看自己想看的書。小朋友的閱讀不夠，國文和作文就不好，連帶的數學也一定不好，
因為抓不到文章的主旨，也看不懂題目。普通常識不可能都來自於課本，一定要大量的閱讀才有助於提升能力。」──李家同
20180717 Introduction of Seamless BLE Connection Migration System (SeamBlue)
(1) SeamBlue is a framework that enables seamless Bluetooth Low Energy (BLE) connection migration for unmodified IoT devices between multiple gateways.
(2) It uses static program analysis to automatically identify the state variables needed to capture a snapshot of the BLE connection state, avoiding manual code inspection.
(3) Upon a device moving out of range, the current gateway extracts the connection information, disseminates it to candidate gateways, and the new gateway can then recreate the connection state and continue serving the device without disrupting the connection.
Bade Smells in Code
This document discusses bad smells in code that indicate refactoring may be needed. It defines refactoring as restructuring code without changing its external behavior to improve design, readability, and maintainability. Common bad smells include duplicated code, long or complex methods and classes, unused variables, primitive data types when objects could be used, and code that depends too much on other classes rather than being self-contained. The document provides examples of refactoring techniques to address each smell, such as extracting methods, replacing conditionals with polymorphism, and removing unnecessary dependencies between classes.
Intro To BOOST.Spirit
This document provides tutorials and examples for using Boost Spirit Qi, a C++ parsing library. It demonstrates how to parse numeric values, semantic actions, grammars, and structs. The tutorials include parsing floating point numbers, comma-separated lists, and attaching semantic actions. Examples show parsing complex numbers, adding numbers, parsing into vectors, Roman numerals, and a calculator grammar.
20070514 introduction to test ng and its application for test driven gui deve...
TestNG is a testing framework that uses annotations to make testing more simple and flexible. It allows choosing different testing strategies like unit testing, integration testing, and GUI testing. The document introduces TestNG and its features like configuration methods, test grouping, dependency testing, and parametric testing. It also describes using TestNG-Abbot for test-driven GUI development, with an example of testing an email registration form by separating tests for the model and view.
20060411 face recognition using face arg matching
This document proposes a face recognition method using Face-ARG matching. It represents faces using an Attributed Relational Graph (Face-ARG) that encodes geometric and structural information. It constructs a correspondence graph between a reference and test Face-ARG using partial ARG matching. It then evaluates the stochastic distance between corresponding relation vector spaces to identify faces. The method was tested on the AR face database and was shown to be effective despite imperfect line extraction.
20060411 Analytic Hierarchy Process (AHP)
The Analytic Hierarchy Process (AHP) is a decision-making tool that breaks down complex decisions into a series of pairwise comparisons. It allows decision makers to incorporate both qualitative and quantitative factors. The AHP works by:
1) Computing weights for each decision criterion through pairwise comparisons.
2) Scoring alternatives based on each criterion.
3) Multiplying the weights and scores to obtain overall scores for each alternative.
4) Ranking the alternatives based on their overall scores. Consistency is also checked to ensure reliable results. An example is provided to illustrate the AHP process.
20050713 critical paths for gui regression testing
Critical Paths for GUI Regression Testing. Alexander K. Ames and Haward Jie. Univ. of California, Santa Cruz
20050314 specification based regression test selection with risk analysis
This document describes a specification-based regression test selection technique with risk analysis. It selects targeted tests to cover changes in code or specifications, and safety tests directed by risk analysis. Safety tests are chosen using a risk exposure model factoring probability and cost of faults. Scenarios simulating user profiles are also selected based on their risk exposure covering critical test cases. The approach was evaluated on an IBM project and found effective, cost-efficient, and sensitive to risk. Future work includes determining when to stop testing and implementing the approach in a production environment.
20041113 A Test Generation Tool for Specifications in the Form of State Machine
This document describes a test generation tool for specifications in the form of state machines. The tool automatically generates test cases from finite state machine (FSM) specifications. It uses transition identification approaches like preambles, postambles, transition coverage, and state identification sequences to derive tests. Experiments show that the tool can generate tests for FSMs with up to 200 states and 40,000 transitions within reasonable time frames.
Junit Recipes - Elementary tests (2/2)
The document discusses 10 techniques for testing different types of code elements in JUnit:
1. Testing equals() methods by creating objects with equal and unequal property values.
2. Testing void methods by observing side effects like state changes.
3. Testing constructors by examining exposed internal state or side effects.
4. Testing getters by comparing returned values to expectations.
5. Testing setters by observing side effects like state changes in dependent objects.
6. Testing interfaces by creating test-friendly implementations to cover all possibilities.
7. Testing exception handling by placing code in try/catch blocks and validating exceptions.
8. Testing collections by letting equals() determine equality rather
Junit Recipes - Elementary tests (1/2)
This document discusses testing elementary components in JUnit, including testing equals methods, methods that return nothing, constructors, getters, setters, interfaces, exceptions, collections, large objects, and objects that instantiate other objects. It provides examples and recommendations for each, such as comparing the result of a getter to an expected value, analyzing the side effects of methods that return nothing, and using a "spy" subclass to observe the behavior of a setter. The document is divided into sections for each of these elementary testing scenarios.
Junit Recipes - Intro
The document outlines a book on JUnit recipes for testing Java code. It is divided into three parts that cover the basics of JUnit, testing Java 2 Enterprise Edition (J2EE) applications, and advanced JUnit techniques. The first part introduces fundamentals like unit testing objects in isolation, the structure of writing test cases using the JUnit framework, and assertions. It also describes test-driven development and lists common elementary tests like testing equals methods, getters, setters, exceptions, and complex objects.
20051019 automating regression testing for evolving gui software
The document describes DART (Daily Automated Regression Tester), a framework for automating regression testing of GUI software. DART includes modules for analyzing the GUI, generating test cases, executing tests, and evaluating code coverage. It uses a formal model of the GUI to represent objects, properties, events, and component interactions. Experiments applying DART to several applications showed it could test nightly builds within a night and achieve high code coverage efficiently. The conclusions state DART provides an effective process for smoke testing frequent builds of GUI software.
20060712 automated model based testing of community-driven open-source gui ap...
1. The document proposes a model-based testing approach to test community-driven open-source GUI applications in an automated manner using concentric testing loops.
2. An event-flow graph model is used to represent all possible event sequences in the GUI and generate test cases. Tests are classified into smoke, crash, and comprehensive tests.
3. The approach was evaluated on four open-source applications, detecting bugs that persisted across multiple versions. The results demonstrate that resources can be better utilized through a loop-based testing approach for open-source GUI applications.
20041221 gui testing survey
"Hierarchical GUI Test Case Generation Using Automated Planning"
"Plan Generation for GUI Testing"
20060927 application facades
This document discusses application facades and their use in agile GUI development. It presents an example of using an application facade for a calculator application to keep the view thin and leverage testing. It then provides an example of using facades for a healthcare application, describing how they can encapsulate operations and handle type conversions between tiers. The conclusion emphasizes that facades help separate an application into layers to make the code easier to maintain and test, and allow most of the application to operate without the UI.
20111018 boost and gtest
This document provides an overview and summary of Boost and Google Test (gtest). It discusses key Boost libraries like smart pointers, assign, foreach, and bind. It explains how Boost handles memory management and containers. It also covers the basics of gtest like writing assertions and test fixtures. The document recommends gtest as a lightweight unit testing framework compared to Cppunit.
Data collection for field studies
This document discusses techniques for collecting data during software engineering field studies. It describes both direct techniques that involve direct interaction with participants, such as interviews, questionnaires, and observation. It also covers indirect techniques that collect data through artifacts of the participants' work, such as analyzing documentation, logs, and source code. For each technique, the document discusses advantages, disadvantages, and reporting guidelines to provide context on how the data was collected and analyzed. The goal is to help researchers select the most appropriate techniques and effectively report the results of their studies.
More Related Content
More from Will Shen
Bade Smells in Code
This document discusses bad smells in code that indicate refactoring may be needed. It defines refactoring as restructuring code without changing its external behavior to improve design, readability, and maintainability. Common bad smells include duplicated code, long or complex methods and classes, unused variables, primitive data types when objects could be used, and code that depends too much on other classes rather than being self-contained. The document provides examples of refactoring techniques to address each smell, such as extracting methods, replacing conditionals with polymorphism, and removing unnecessary dependencies between classes.
Intro To BOOST.Spirit
This document provides tutorials and examples for using Boost Spirit Qi, a C++ parsing library. It demonstrates how to parse numeric values, semantic actions, grammars, and structs. The tutorials include parsing floating point numbers, comma-separated lists, and attaching semantic actions. Examples show parsing complex numbers, adding numbers, parsing into vectors, Roman numerals, and a calculator grammar.
20070514 introduction to test ng and its application for test driven gui deve...
TestNG is a testing framework that uses annotations to make testing more simple and flexible. It allows choosing different testing strategies like unit testing, integration testing, and GUI testing. The document introduces TestNG and its features like configuration methods, test grouping, dependency testing, and parametric testing. It also describes using TestNG-Abbot for test-driven GUI development, with an example of testing an email registration form by separating tests for the model and view.
20060411 face recognition using face arg matching
This document proposes a face recognition method using Face-ARG matching. It represents faces using an Attributed Relational Graph (Face-ARG) that encodes geometric and structural information. It constructs a correspondence graph between a reference and test Face-ARG using partial ARG matching. It then evaluates the stochastic distance between corresponding relation vector spaces to identify faces. The method was tested on the AR face database and was shown to be effective despite imperfect line extraction.
20060411 Analytic Hierarchy Process (AHP)
The Analytic Hierarchy Process (AHP) is a decision-making tool that breaks down complex decisions into a series of pairwise comparisons. It allows decision makers to incorporate both qualitative and quantitative factors. The AHP works by:
1) Computing weights for each decision criterion through pairwise comparisons.
2) Scoring alternatives based on each criterion.
3) Multiplying the weights and scores to obtain overall scores for each alternative.
4) Ranking the alternatives based on their overall scores. Consistency is also checked to ensure reliable results. An example is provided to illustrate the AHP process.
20050713 critical paths for gui regression testing
Critical Paths for GUI Regression Testing. Alexander K. Ames and Haward Jie. Univ. of California, Santa Cruz
20050314 specification based regression test selection with risk analysis
This document describes a specification-based regression test selection technique with risk analysis. It selects targeted tests to cover changes in code or specifications, and safety tests directed by risk analysis. Safety tests are chosen using a risk exposure model factoring probability and cost of faults. Scenarios simulating user profiles are also selected based on their risk exposure covering critical test cases. The approach was evaluated on an IBM project and found effective, cost-efficient, and sensitive to risk. Future work includes determining when to stop testing and implementing the approach in a production environment.
20041113 A Test Generation Tool for Specifications in the Form of State Machine
This document describes a test generation tool for specifications in the form of state machines. The tool automatically generates test cases from finite state machine (FSM) specifications. It uses transition identification approaches like preambles, postambles, transition coverage, and state identification sequences to derive tests. Experiments show that the tool can generate tests for FSMs with up to 200 states and 40,000 transitions within reasonable time frames.
Junit Recipes - Elementary tests (2/2)
The document discusses 10 techniques for testing different types of code elements in JUnit:
1. Testing equals() methods by creating objects with equal and unequal property values.
2. Testing void methods by observing side effects like state changes.
3. Testing constructors by examining exposed internal state or side effects.
4. Testing getters by comparing returned values to expectations.
5. Testing setters by observing side effects like state changes in dependent objects.
6. Testing interfaces by creating test-friendly implementations to cover all possibilities.
7. Testing exception handling by placing code in try/catch blocks and validating exceptions.
8. Testing collections by letting equals() determine equality rather
Junit Recipes - Elementary tests (1/2)
This document discusses testing elementary components in JUnit, including testing equals methods, methods that return nothing, constructors, getters, setters, interfaces, exceptions, collections, large objects, and objects that instantiate other objects. It provides examples and recommendations for each, such as comparing the result of a getter to an expected value, analyzing the side effects of methods that return nothing, and using a "spy" subclass to observe the behavior of a setter. The document is divided into sections for each of these elementary testing scenarios.
Junit Recipes - Intro
The document outlines a book on JUnit recipes for testing Java code. It is divided into three parts that cover the basics of JUnit, testing Java 2 Enterprise Edition (J2EE) applications, and advanced JUnit techniques. The first part introduces fundamentals like unit testing objects in isolation, the structure of writing test cases using the JUnit framework, and assertions. It also describes test-driven development and lists common elementary tests like testing equals methods, getters, setters, exceptions, and complex objects.
20051019 automating regression testing for evolving gui software
The document describes DART (Daily Automated Regression Tester), a framework for automating regression testing of GUI software. DART includes modules for analyzing the GUI, generating test cases, executing tests, and evaluating code coverage. It uses a formal model of the GUI to represent objects, properties, events, and component interactions. Experiments applying DART to several applications showed it could test nightly builds within a night and achieve high code coverage efficiently. The conclusions state DART provides an effective process for smoke testing frequent builds of GUI software.
20060712 automated model based testing of community-driven open-source gui ap...
1. The document proposes a model-based testing approach to test community-driven open-source GUI applications in an automated manner using concentric testing loops.
2. An event-flow graph model is used to represent all possible event sequences in the GUI and generate test cases. Tests are classified into smoke, crash, and comprehensive tests.
3. The approach was evaluated on four open-source applications, detecting bugs that persisted across multiple versions. The results demonstrate that resources can be better utilized through a loop-based testing approach for open-source GUI applications.
20041221 gui testing survey
"Hierarchical GUI Test Case Generation Using Automated Planning"
"Plan Generation for GUI Testing"
20060927 application facades
This document discusses application facades and their use in agile GUI development. It presents an example of using an application facade for a calculator application to keep the view thin and leverage testing. It then provides an example of using facades for a healthcare application, describing how they can encapsulate operations and handle type conversions between tiers. The conclusion emphasizes that facades help separate an application into layers to make the code easier to maintain and test, and allow most of the application to operate without the UI.
20111018 boost and gtest
This document provides an overview and summary of Boost and Google Test (gtest). It discusses key Boost libraries like smart pointers, assign, foreach, and bind. It explains how Boost handles memory management and containers. It also covers the basics of gtest like writing assertions and test fixtures. The document recommends gtest as a lightweight unit testing framework compared to Cppunit.
Data collection for field studies
This document discusses techniques for collecting data during software engineering field studies. It describes both direct techniques that involve direct interaction with participants, such as interviews, questionnaires, and observation. It also covers indirect techniques that collect data through artifacts of the participants' work, such as analyzing documentation, logs, and source code. For each technique, the document discusses advantages, disadvantages, and reporting guidelines to provide context on how the data was collected and analyzed. The goal is to help researchers select the most appropriate techniques and effectively report the results of their studies.
More from Will Shen (17)
20070514 introduction to test ng and its application for test driven gui deve...
20070514 introduction to test ng and its application for test driven gui deve...
20050713 critical paths for gui regression testing
20050713 critical paths for gui regression testing
20050314 specification based regression test selection with risk analysis
20050314 specification based regression test selection with risk analysis
20041113 A Test Generation Tool for Specifications in the Form of State Machine
20041113 A Test Generation Tool for Specifications in the Form of State Machine
20051019 automating regression testing for evolving gui software
20051019 automating regression testing for evolving gui software
20060712 automated model based testing of community-driven open-source gui ap...
20060712 automated model based testing of community-driven open-source gui ap...
16格筆記讀書法
- 4. 最常被人問：「請問閱讀速度怎麼練？」 • 普通人：200~600字/分 • 人人從小都有「速讀」能力學 校 • 老師教你一個字一個字讀的方 式，教壞了 • 幾乎所有人都以為讀書該這樣 讀： step1) 用眼睛看 step2) 在 心裡默讀 • 2萬字/分 • 半天生 • 「屏棄掉一個一個字閱讀的方 式，一次看一句或者是一面」。 • 讀書時是沒有「文字翻譯成聲 音」這個機制的。意思就是他 們讀書的方式是「眼腦直譯」。 4
- 5. 速讀能力者也辦不到的事： 記得整本書的內容 • 二十分鐘能看完一本幾百頁的書 大概記得 5 個大重點與其相 關案例 • 大腦能夠承受的資訊上限 3-5 本/天 • 酸民的「速讀無用論」：認為「速讀」並不會帶來實質上的「提 升效益」 • 當有人問我如何學習速讀呢？我給的建議就是：帶著你的問題去看，放棄逐字閱讀。只在一本書 翻解法，當你心中有特定疑問時，你就能快速看 到許多重點並記得這些資訊。 5
- 7. 如何30分鐘讀一本書和做好筆記 7 Step 1 ：找出你最想問這本書的一個問 題 書名 你最想要在書中得到的一個解答 你提出這個問題的動機 Step 2 ：限時 30 分鐘摘出 16 個關鍵字 指開始快速翻閱這本書，記下「最相關 的關鍵字、段落」 Step 3 ：針對這 16 個 關鍵字，整理出 3-5 個重點 Step 4 ：複述心得 拿著這張 A4 筆記，馬 上複述給朋友聽，你在 這本書得到的心得。
- 8. 範例： 8
- 9. 關鍵原因 1/4 -人類的工作記憶區只有 5 格 • 許多人看書時是抱著一個開放的心態， 希望在一本書當中 GET 到許多精髓。 • 但是，人的「工作記憶」只有 5 格。也 就是讀這本書，讀一次的時間內，你不 可能記得超過 5 件事，這是鐵錚錚的人 體限制。 • 一直記關鍵字、一直記關鍵字不要停。 • 不要在找寫關鍵字時還在回想總結以前 的經驗， • 就是快進快出工作記憶區，頭腦零酸爽 負擔感。 9
- 10. 關鍵原因 2/4 - 限制才能帶來效率 • 你得用筆寫，寫在紙上。紙就是你的籃子，人的暫存格 只有 5 格。如果不用筆記，最後看完一本書裡面只有 5 個蘋果而已。 • 書裡面可能有 50 個蘋果，有些蘋果其實不好吃，只有 16 個格子，可以逼讀者記下重點的重點。 • 格子為什麼很小 逼讀者能夠用 1-2 話講清楚這個重點。 • 如果不限制時間，就不會加快效率。 10
- 11. 關鍵原因 3/4 – 帶著問題看書 • 錨定效應 (Anchoring Effect) • 也就是學習時，穿針引線可以 更有效率，當一大堆數據資料 在腦袋瓜裡運轉時，定錨可以 幫助類似資料快速連結，可以 節省學習時間與提高效率，並 且，協助抽象化能力的快速形 成 第一印象是種可以定位的「錨」， 一旦定下來，後面接受的資訊常 常會受到這個「錨」的影響 11
- 12. 關鍵原因 4/4 - 「不能隻字不差的閱讀」感 覺很有罪惡感? • 但，想想當你在用搜尋引擎時，不也是針對茫茫大海只取你要的 一部分資訊嗎？那時候你怎麼沒有罪惡感了？你沒發現，對一本 書「搜索」其實超有效率。 極速讀書方法: 用30分鐘搜尋一個問題的解答 12
- 13. 上千網友的見證 13
- 14. 為什麼極速讀書法會讓人停不下來 (上癮) • 找關鍵字 = 開寶箱： • 現自己有辦法開寶箱，十六個小寶箱，即成三 個大寶箱。看很多不同的書的時候你發現自己 有辦法開連在一起講。 • 手寫關鍵字 = 改變大腦運作速度 • 只抓關鍵字，再用手寫下來，不是用打字 • 大腦運轉的速度降到你的手寫的速度， 輸入等於輸出速度等於你的處理速度 進入專注的狀態 – 心流(flow) • 每個人大腦處理資訊的速度不一，比較笨的人 聽你講話會聽不懂，比較聰明的人就會分心 14 在心流狀態的時候開到變動寶箱 你就會覺得停不下來，就會成癮。
- 15. 小密圈 – 讀書會 • 創建13天, 590人+, 總年費：150+萬(NTD) 15
- 16. 範例：TensorFlow 是如何處理Deep Learning 問題 16
- 17. 範例：神經網路如何描述問題 17