Auto saved by Logseq
This commit is contained in:
parent
d502f095aa
commit
606e486156
|
@ -1 +0,0 @@
|
|||
- LATER 看见面课
|
|
@ -1,3 +0,0 @@
|
|||
- #projects #健身
|
||||
- 5x5 workout
|
||||
- https://www.bodybuilding.com/content/5-best-bodybuilding-programs-to-pack-on-serious-muscle.html
|
|
@ -0,0 +1,357 @@
|
|||
- Todos:
|
||||
- 学习任务
|
||||
- DONE 交区块链作业
|
||||
- DONE [#A] 剪视频
|
||||
SCHEDULED: <2023-03-29 Wed>
|
||||
DEADLINE: <2023-04-06 Thu>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-28 Tue 09:54:49]--[2023-03-28 Tue 09:54:53] => 00:00:04
|
||||
CLOCK: [2023-03-28 Tue 10:42:56]--[2023-03-28 Tue 11:57:08] => 01:14:12
|
||||
CLOCK: [2023-03-28 Tue 12:48:27]--[2023-03-28 Tue 13:45:10] => 00:56:43
|
||||
CLOCK: [2023-03-31 Fri 22:24:12]--[2023-03-31 Fri 23:42:11] => 01:17:59
|
||||
CLOCK: [2023-04-01 Sat 10:42:09]--[2023-04-01 Sat 11:55:33] => 01:13:24
|
||||
:END:
|
||||
- DONE 学 java
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 11:26:38]--[2023-03-27 Mon 14:04:31] => 02:37:53
|
||||
CLOCK: [2023-03-27 Mon 15:54:27]--[2023-03-27 Mon 16:02:50] => 00:08:23
|
||||
CLOCK: [2023-03-27 Mon 16:02:52]--[2023-03-27 Mon 16:02:52] => 00:00:00
|
||||
:END:
|
||||
- DONE 概率论作业
|
||||
SCHEDULED: <2023-04-01 Sat>
|
||||
DEADLINE: <2023-04-01 Sat>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-01 Sat 19:33:00]--[2023-04-01 Sat 22:53:21] => 03:20:21
|
||||
:END:
|
||||
- DONE 17
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-01 Sat 19:33:05]--[2023-04-01 Sat 20:48:19] => 01:15:14
|
||||
:END:
|
||||
- DONE 18 密度改成 1 / 4 pi
|
||||
- DONE 20
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-01 Sat 20:48:22]--[2023-04-01 Sat 20:55:58] => 00:07:36
|
||||
:END:
|
||||
- DONE 22
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-01 Sat 20:55:59]--[2023-04-01 Sat 21:08:03] => 00:12:04
|
||||
:END:
|
||||
- DONE 54
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-01 Sat 21:08:04]--[2023-04-01 Sat 22:53:17] => 01:45:13
|
||||
:END:
|
||||
- DONE 55
|
||||
- DONE 58 b 不做
|
||||
- DONE 59
|
||||
- DONE 复习 java
|
||||
SCHEDULED: <2023-03-28 Tue>
|
||||
- DONE 做 lab
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 18:59:33]--[2023-03-27 Mon 21:51:19] => 02:51:46
|
||||
:END:
|
||||
- DONE 产开选题
|
||||
DEADLINE: <2023-03-30 Thu>
|
||||
- DONE [#A] 复习电路
|
||||
DEADLINE: <2023-03-29 Wed>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-28 Tue 09:52:06]--[2023-03-28 Tue 10:59:57] => 01:07:51
|
||||
:END:
|
||||
- DONE 看课件
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-28 Tue 09:54:34]--[2023-03-28 Tue 10:41:52] => 00:47:18
|
||||
:END:
|
||||
- DONE 做题
|
||||
- DONE [#A] 复习卡氏图
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-29 Wed 10:31:01]--[2023-03-29 Wed 10:31:01] => 00:00:00
|
||||
CLOCK: [2023-03-29 Wed 10:31:02]--[2023-03-29 Wed 16:52:13] => 06:21:11
|
||||
:END:
|
||||
- DONE 预习 lab
|
||||
- DONE 打印资料
|
||||
- 个人任务
|
||||
- DONE 给尧舜天注册帐号 (没注册成功)
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 16:13:04]--[2023-03-27 Mon 16:41:33] => 00:28:29
|
||||
CLOCK: [2023-03-27 Mon 17:58:01]--[2023-03-27 Mon 17:58:01] => 00:00:00
|
||||
:END:
|
||||
- LATER Work on mapping feature in logseq
|
||||
- DONE 洗衣服
|
||||
SCHEDULED: <2023-03-28 Tue>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-28 Tue 08:53:36]--[2023-03-28 Tue 09:37:35] => 00:43:59
|
||||
:END:
|
||||
-
|
||||
- Recurring tasks: [[Habits]]
|
||||
- Daily:
|
||||
- LATER [#B] Read books
|
||||
SCHEDULED: <2023-05-24 Wed .+1d>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 16:47:35]--[2023-03-27 Mon 16:47:51] => 00:00:16
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 16:47]
|
||||
CLOCK: [2023-03-30 Thu 08:04:21]--[2023-03-30 Thu 09:16:49] => 01:12:28
|
||||
* State "DONE" from "LATER" [2023-03-30 Thu 09:16]
|
||||
CLOCK: [2023-04-02 Sun 19:59:18]--[2023-04-02 Sun 20:17:05] => 00:17:47
|
||||
* State "DONE" from "LATER" [2023-04-04 Tue 14:33]
|
||||
* State "DONE" from "LATER" [2023-04-06 Thu 07:33]
|
||||
* State "DONE" from "LATER" [2023-04-10 Mon 18:33]
|
||||
* State "DONE" from "LATER" [2023-04-12 Wed 16:17]
|
||||
* State "DONE" from "LATER" [2023-04-15 Sat 16:00]
|
||||
* State "DONE" from "LATER" [2023-04-15 Sat 20:37]
|
||||
* State "DONE" from "LATER" [2023-04-18 Tue 09:55]
|
||||
* State "DONE" from "LATER" [2023-04-19 Wed 18:10]
|
||||
* State "DONE" from "LATER" [2023-04-21 Fri 15:14]
|
||||
CLOCK: [2023-04-22 Sat 19:10:58]--[2023-04-22 Sat 21:39:19] => 02:28:21
|
||||
* State "DONE" from "NOW" [2023-04-22 Sat 21:39]
|
||||
CLOCK: [2023-04-23 Sun 09:37:33]--[2023-04-23 Sun 10:59:35] => 01:22:02
|
||||
* State "DONE" from "NOW" [2023-04-23 Sun 10:59]
|
||||
* State "DONE" from "LATER" [2023-04-24 Mon 21:39]
|
||||
* State "DONE" from "LATER" [2023-04-26 Wed 22:31]
|
||||
* State "DONE" from "LATER" [2023-04-28 Fri 17:31]
|
||||
CLOCK: [2023-05-06 Sat 20:35:36]--[2023-05-06 Sat 21:40:06] => 01:04:30
|
||||
* State "DONE" from "NOW" [2023-05-06 Sat 21:40]
|
||||
* State "DONE" from "LATER" [2023-05-08 Mon 20:15]
|
||||
* State "DONE" from "LATER" [2023-05-09 Tue 11:13]
|
||||
* State "DONE" from "LATER" [2023-05-10 Wed 21:35]
|
||||
* State "DONE" from "LATER" [2023-05-11 Thu 19:55]
|
||||
* State "DONE" from "LATER" [2023-05-15 Mon 15:43]
|
||||
* State "DONE" from "LATER" [2023-05-20 Sat 20:10]
|
||||
* State "DONE" from "LATER" [2023-05-23 Tue 20:26]
|
||||
:END:
|
||||
- LATER [#B] Memorize vocabulary
|
||||
SCHEDULED: <2023-05-24 Wed .+1d>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 16:48:26]--[2023-03-27 Mon 18:53:54] => 02:05:28
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 18:53]
|
||||
* State "DONE" from "LATER" [2023-04-02 Sun 14:39]
|
||||
* State "DONE" from "LATER" [2023-04-03 Mon 10:30]
|
||||
* State "DONE" from "LATER" [2023-04-06 Thu 22:51]
|
||||
* State "DONE" from "LATER" [2023-04-11 Tue 13:52]
|
||||
* State "DONE" from "LATER" [2023-04-12 Wed 12:29]
|
||||
* State "DONE" from "LATER" [2023-04-13 Thu 21:42]
|
||||
* State "DONE" from "LATER" [2023-04-15 Sat 17:34]
|
||||
CLOCK: [2023-04-17 Mon 09:43:03]--[2023-04-17 Mon 15:57:16] => 06:14:13
|
||||
* State "DONE" from "NOW" [2023-04-17 Mon 15:57]
|
||||
* State "DONE" from "LATER" [2023-04-18 Tue 10:13]
|
||||
CLOCK: [2023-04-23 Sun 11:10:16]--[2023-04-23 Sun 11:28:28] => 00:18:12
|
||||
* State "DONE" from "NOW" [2023-04-23 Sun 11:28]
|
||||
* State "DONE" from "LATER" [2023-04-24 Mon 20:57]
|
||||
* State "DONE" from "LATER" [2023-04-25 Tue 10:57]
|
||||
* State "DONE" from "LATER" [2023-04-26 Wed 22:31]
|
||||
* State "DONE" from "LATER" [2023-04-28 Fri 16:37]
|
||||
* State "DONE" from "LATER" [2023-05-06 Sat 20:35]
|
||||
* State "DONE" from "LATER" [2023-05-07 Sun 09:20]
|
||||
* State "DONE" from "LATER" [2023-05-08 Mon 19:36]
|
||||
CLOCK: [2023-05-09 Tue 09:50:18]--[2023-05-09 Tue 09:52:45] => 00:02:27
|
||||
* State "DONE" from "NOW" [2023-05-09 Tue 09:52]
|
||||
CLOCK: [2023-05-11 Thu 10:13:10]--[2023-05-11 Thu 10:13:11] => 00:00:01
|
||||
* State "DONE" from "NOW" [2023-05-11 Thu 10:13]
|
||||
* State "DONE" from "LATER" [2023-05-15 Mon 15:43]
|
||||
* State "DONE" from "LATER" [2023-05-19 Fri 16:55]
|
||||
* State "DONE" from "LATER" [2023-05-21 Sun 20:59]
|
||||
* State "DONE" from "LATER" [2023-05-23 Tue 20:26]
|
||||
:END:
|
||||
- DONE [#B] Solve one #leetcode Problem
|
||||
SCHEDULED: <2023-05-22 Mon>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 16:56:53]--[2023-03-28 Tue 14:02:38] => 21:05:45
|
||||
CLOCK: [2023-03-28 Tue 14:02:43]--[2023-03-28 Tue 14:24:54] => 00:22:11
|
||||
- State "DONE" from "NOW" [2023-03-28 Tue 14:24]
|
||||
CLOCK: [2023-03-30 Thu 07:39:35]--[2023-03-30 Thu 07:52:53] => 00:13:18
|
||||
* State "DONE" from "NOW" [2023-03-30 Thu 07:52]
|
||||
CLOCK: [2023-03-31 Fri 07:51:59]--[2023-03-31 Fri 08:41:05] => 00:49:06
|
||||
* State "DONE" from "NOW" [2023-03-31 Fri 08:41]
|
||||
CLOCK: [2023-04-02 Sun 09:36:38]--[2023-04-02 Sun 10:35:35] => 00:58:57
|
||||
* State "DONE" from "LATER" [2023-04-02 Sun 10:35]
|
||||
CLOCK: [2023-04-03 Mon 18:56:00]--[2023-04-03 Mon 22:00:42] => 03:04:42
|
||||
* State "DONE" from "NOW" [2023-04-03 Mon 22:00]
|
||||
CLOCK: [2023-04-06 Thu 07:33:36]--[2023-04-06 Thu 07:36:41] => 00:03:05
|
||||
* State "DONE" from "LATER" [2023-04-06 Thu 10:21]
|
||||
* State "DONE" from "LATER" [2023-04-11 Tue 10:35]
|
||||
CLOCK: [2023-04-16 Sun 10:11:02]--[2023-04-17 Mon 09:43:05] => 23:32:03
|
||||
* State "DONE" from "LATER" [2023-04-17 Mon 22:58]
|
||||
* State "DONE" from "LATER" [2023-04-18 Tue 09:55]
|
||||
CLOCK: [2023-04-21 Fri 14:11:20]--[2023-04-21 Fri 14:41:02] => 00:29:42
|
||||
* State "DONE" from "NOW" [2023-04-21 Fri 14:41]
|
||||
* State "DONE" from "LATER" [2023-04-25 Tue 10:46]
|
||||
* State "DONE" from "LATER" [2023-04-28 Fri 16:45]
|
||||
* State "DONE" from "LATER" [2023-05-11 Thu 20:30]
|
||||
* State "DONE" from "LATER" [2023-05-21 Sun 20:59]
|
||||
:END:
|
||||
- Weekly:
|
||||
- LATER [#B] Run in the field three times a week 2/3
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 16:58:41]--[2023-03-27 Mon 19:33:31] => 02:34:50
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 19:33]
|
||||
* State "DONE" from "LATER" [2023-03-28 Tue 19:35]
|
||||
* State "DONE" from "LATER" [2023-03-30 Thu 07:30]
|
||||
* State "DONE" from "LATER" [2023-03-31 Fri 07:52]
|
||||
* State "DONE" from "LATER" [2023-04-02 Sun 09:35]
|
||||
* State "DONE" from "LATER" [2023-04-07 Fri 11:32]
|
||||
* State "DONE" from "LATER" [2023-04-09 Sun 16:57]
|
||||
* State "DONE" from "LATER" [2023-04-11 Tue 12:47]
|
||||
* State "DONE" from "LATER" [2023-04-12 Wed 08:59]
|
||||
* State "DONE" from "LATER" [2023-04-13 Thu 21:42]
|
||||
* State "DONE" from "LATER" [2023-04-14 Fri 08:37]
|
||||
* State "DONE" from "LATER" [2023-04-15 Sat 16:00]
|
||||
* State "DONE" from "LATER" [2023-04-18 Tue 23:31]
|
||||
* State "DONE" from "LATER" [2023-04-19 Wed 22:05]
|
||||
* State "DONE" from "LATER" [2023-04-21 Fri 09:07]
|
||||
* State "DONE" from "LATER" [2023-04-23 Sun 13:31]
|
||||
* State "DONE" from "LATER" [2023-04-24 Mon 20:56]
|
||||
* State "DONE" from "LATER" [2023-04-25 Tue 11:24]
|
||||
* State "DONE" from "LATER" [2023-04-28 Fri 16:18]
|
||||
* State "DONE" from "LATER" [2023-05-06 Sat 20:25]
|
||||
* State "DONE" from "LATER" [2023-05-08 Mon 19:25]
|
||||
* State "DONE" from "LATER" [2023-05-10 Wed 21:35]
|
||||
* State "DONE" from "LATER" [2023-05-11 Thu 19:55]
|
||||
* State "DONE" from "LATER" [2023-05-12 Fri 08:38]
|
||||
CLOCK: [2023-05-19 Fri 17:49:26]--[2023-05-19 Fri 17:49:28] => 00:00:02
|
||||
* State "DONE" from "LATER" [2023-05-19 Fri 17:49]
|
||||
* State "DONE" from "LATER" [2023-05-21 Sun 20:59]
|
||||
:END:
|
||||
-
|
||||
- LATER [#C] Watch movies once a week
|
||||
SCHEDULED: <2023-06-12 Mon .+2d>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 16:59:18]--[2023-03-27 Mon 19:34:08] => 02:34:50
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 19:34]
|
||||
* State "DONE" from "LATER" [2023-04-10 Mon 22:13]
|
||||
* State "DONE" from "LATER" [2023-04-12 Wed 16:00]
|
||||
* State "DONE" from "LATER" [2023-04-14 Fri 08:37]
|
||||
* State "DONE" from "LATER" [2023-04-18 Tue 23:31]
|
||||
* State "DONE" from "LATER" [2023-04-21 Fri 09:07]
|
||||
* State "DONE" from "LATER" [2023-04-22 Sat 19:10]
|
||||
* State "DONE" from "LATER" [2023-04-24 Mon 20:56]
|
||||
* State "DONE" from "LATER" [2023-05-06 Sat 20:25]
|
||||
* State "DONE" from "LATER" [2023-05-08 Mon 19:25]
|
||||
* State "DONE" from "LATER" [2023-05-11 Thu 20:08]
|
||||
* State "DONE" from "LATER" [2023-05-14 Sun 13:15]
|
||||
* State "DONE" from "LATER" [2023-05-19 Fri 17:35]
|
||||
* State "DONE" from "LATER" [2023-06-08 Thu 11:29]
|
||||
* State "DONE" from "LATER" [2023-06-10 Sat 16:37]
|
||||
:END:
|
||||
-
|
||||
-
|
||||
- 每周学习任务
|
||||
- 每周:
|
||||
- 智慧树网课
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 17:22:00]
|
||||
:END:
|
||||
- DONE [#C] 网课每周三次 3/3
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 17:23:09]--[2023-03-27 Mon 17:23:18] => 00:00:09
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 17:23]
|
||||
- State "DONE" from "LATER" [2023-03-27 Mon 17:24]
|
||||
- State "DONE" from "LATER" [2023-03-27 Mon 17:25]
|
||||
- State "DONE" from "LATER" [2023-03-27 Mon 19:27]
|
||||
CLOCK: [2023-03-27 Mon 19:29:22]--[2023-03-27 Mon 19:29:31] => 00:00:09
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 19:29]
|
||||
* State "DONE" from "LATER" [2023-03-28 Tue 19:35]
|
||||
* State "DONE" from "LATER" [2023-03-29 Wed 16:52]
|
||||
* State "DONE" from "LATER" [2023-03-30 Thu 09:16]
|
||||
* State "DONE" from "LATER" [2023-03-31 Fri 07:52]
|
||||
* State "DONE" from "LATER" [2023-04-02 Sun 09:35]
|
||||
* State "DONE" from "LATER" [2023-04-03 Mon 13:31]
|
||||
CLOCK: [2023-04-03 Mon 22:02:50]--[2023-04-04 Tue 09:09:23] => 11:06:33
|
||||
:END:
|
||||
- DONE [#C] 测验每周一次 1/1
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 17:23:12]--[2023-03-27 Mon 19:27:27] => 02:04:15
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 19:27]
|
||||
CLOCK: [2023-03-27 Mon 19:29:26]--[2023-03-27 Mon 19:29:35] => 00:00:09
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 19:29]
|
||||
* State "DONE" from "LATER" [2023-03-29 Wed 18:28]
|
||||
* State "DONE" from "LATER" [2023-03-30 Thu 09:16]
|
||||
* State "DONE" from "LATER" [2023-04-01 Sat 09:25]
|
||||
* State "DONE" from "LATER" [2023-04-02 Sun 09:35]
|
||||
:END:
|
||||
- DONE [#C] 互动每周三次 1/3
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 17:23:16]--[2023-03-27 Mon 19:29:36] => 02:06:20
|
||||
- State "DONE" from "NOW" [2023-03-27 Mon 19:29]
|
||||
* State "DONE" from "LATER" [2023-03-31 Fri 11:16]
|
||||
CLOCK: [2023-04-02 Sun 19:10:30]--[2023-04-02 Sun 19:25:28] => 00:14:58
|
||||
* State "DONE" from "NOW" [2023-04-02 Sun 19:25]
|
||||
* State "DONE" from "LATER" [2023-04-03 Mon 18:49]
|
||||
CLOCK: [2023-04-04 Tue 13:35:09]--[2023-04-04 Tue 13:55:20] => 00:20:11
|
||||
* State "DONE" from "NOW" [2023-04-04 Tue 13:55]
|
||||
* State "DONE" from "LATER" [2023-04-06 Thu 22:51]
|
||||
* State "DONE" from "LATER" [2023-04-11 Tue 16:27]
|
||||
:END:
|
||||
-
|
||||
- [#C] 这几天的书单 [[Book lists]] #excluded_in_query #books
|
||||
- 通识
|
||||
- DONE [#C] 云彩收集者手册
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 19:41:38]
|
||||
CLOCK: [2023-03-27 Mon 19:42:00]--[2023-03-28 Tue 16:19:55] => 20:37:55
|
||||
CLOCK: [2023-03-28 Tue 16:20:29]--[2023-03-31 Fri 07:46:16] => 63:25:47
|
||||
:END:
|
||||
- NOW [#C] 日本料理完全图鉴
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 19:42:14]
|
||||
:END:
|
||||
- 历史
|
||||
- DONE [#C] 二手时间
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-27 Mon 19:42:23]--[2023-04-15 Sat 18:53:54] => 455:11:31
|
||||
CLOCK: [2023-04-15 Sat 18:53:55]--[2023-04-15 Sat 18:53:55] => 00:00:00
|
||||
:END:
|
||||
- 文学
|
||||
- LATER the eternaut
|
||||
- 经典小说
|
||||
- LATER 欧亨利
|
||||
- LATER 莫泊桑
|
||||
- LATER 契诃夫
|
||||
- LATER 奥勃洛莫夫
|
||||
- 爱情小说
|
||||
- LATER Price and prejudice
|
||||
- 哲学
|
||||
- LATER How to be a stoic
|
||||
- DONE [[Amused to Death]]
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-03-31 Fri 07:47:22]
|
||||
CLOCK: [2023-03-31 Fri 07:47:34]--[2023-04-18 Tue 09:54:03] => 434:06:29
|
||||
:END:
|
||||
- DONE [[亲密关系]]
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-15 Sat 18:54:13]--[2023-04-23 Sun 10:52:43] => 183:58:30
|
||||
:END:
|
||||
- DONE [[拥抱逝水年华]]
|
||||
-
|
||||
- Book note [[Book notes]]
|
||||
template:: Book Note
|
||||
collapsed:: true
|
||||
- Metadata:
|
||||
- Time: <% time %>
|
||||
- Page: optional
|
||||
- Content:
|
||||
- This is pretty good
|
||||
-
|
||||
- Daily reflection [[Daily reflections]]
|
||||
template:: Daily reflections
|
||||
collapsed:: true
|
||||
- What I've done
|
||||
- What I've thought #thoughts
|
||||
- Mood
|
||||
-
|
||||
- Cloud collections [[Cloud collections]]
|
||||
template:: Cloud Collections
|
||||
collapsed:: true
|
||||
- Photo
|
||||
- Notes
|
||||
- Metadata
|
||||
- Time
|
||||
- <% time %> <% today %>
|
||||
- Weather
|
||||
- cloudy
|
||||
- Type
|
||||
- Location
|
||||
- Map
|
||||
<iframe src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3049.2920871146916!2d116.28518!3d40.158049999999996!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x35f0fbce3d955439%3A0x767d9f097c49f8eb!2sBupt%20Shahe%20Campus!5e0!3m2!1sen!2sjp!4v1679910773010!5m2!1sen!2sjp" width="600" height="450" style="border:0;" allowfullscreen="" loading="lazy" referrerpolicy="no-referrer-when-downgrade"></iframe>
|
||||
- Coordination
|
||||
- 40.15805,116.28518
|
||||
-
|
||||
- #joke
|
||||
- Gob 林
|
|
@ -0,0 +1,140 @@
|
|||
- DONE Ardour
|
||||
- 怎么录制
|
||||
- Ardour vs. audacity
|
||||
-
|
||||
- Leetcode - Happy Number
|
||||
collapsed:: true
|
||||
- Times:
|
||||
- Time when completed: 12:36
|
||||
- Time taken to complete: I forgot, very quick I suppose
|
||||
- Revisions:
|
||||
- Tags:
|
||||
- Algorithms: #Floyd_s_cycle_finding_algorithm
|
||||
- Difficulty: #difficulty_easy
|
||||
- Platforms: #leetcode
|
||||
- Links:
|
||||
- [link to the problem](https://leetcode.com/problems/happy-number/description/)
|
||||
- Problem:
|
||||
- Write an algorithm to determine if a number `n` is happy.
|
||||
|
||||
A **happy number** is a number defined by the following process:
|
||||
- Starting with any positive integer, replace the number by the sum of the squares of its digits.
|
||||
- Repeat the process until the number equals 1 (where it will stay), or it **loops endlessly in a cycle** which does not include 1.
|
||||
- Those numbers for which this process **ends in 1** are happy.
|
||||
|
||||
Return `true` _if_ `n` _is a happy number, and_ `false` _if not_.
|
||||
- Examples:
|
||||
- ```
|
||||
Example 1:
|
||||
|
||||
Input: n = 19
|
||||
Output: true
|
||||
Explanation:
|
||||
12 + 92 = 82
|
||||
82 + 22 = 68
|
||||
62 + 82 = 100
|
||||
12 + 02 + 02 = 1
|
||||
|
||||
Example 2:
|
||||
|
||||
Input: n = 2
|
||||
Output: false
|
||||
|
||||
```
|
||||
- Constraints:
|
||||
- `1 <= n <= 231 - 1`
|
||||
- Thoughts:
|
||||
- Intuition:
|
||||
- It loops endlessly in a cycle, which means we need to use a cycle detection algorithm, which happens to be the [[Floyd's Cycle Finding Algorithm]].
|
||||
- Approach:
|
||||
- Use the Floyd's cycle finding algorithm, with two variables
|
||||
- when fast == slow, cycle is found
|
||||
- detect if fast is 1, and return values
|
||||
- Solution:
|
||||
- Code
|
||||
- ```java
|
||||
class Solution {
|
||||
private int progress(int n) {
|
||||
int sum = 0;
|
||||
while (n > 0) {
|
||||
sum += (n % 10) * (n % 10);
|
||||
n /= 10;
|
||||
}
|
||||
return sum;
|
||||
}
|
||||
public boolean isHappy(int n) {
|
||||
// loop detection
|
||||
int slow = progress(n);
|
||||
int fast = progress(slow);
|
||||
|
||||
while (slow != fast) {
|
||||
slow = progress(slow);
|
||||
fast = progress(progress(fast));
|
||||
}
|
||||
|
||||
return (fast == 1);
|
||||
}
|
||||
}
|
||||
```
|
||||
-
|
||||
- Daily reflection [[Daily reflections]]
|
||||
collapsed:: true
|
||||
- What I've done
|
||||
- 写学交论文
|
||||
- 音乐 improvising
|
||||
- I met someone, she's gorgeous
|
||||
- What I've thought #thoughts
|
||||
- Improvisation is fun :)
|
||||
- I think I fall in love with someone, I have a strong feeling when she is nearby, and dopamine burst out whenever I talk to her. I don't know if she feel the same (I think to some extent she does. I don't really know, I just follow the flow and enjoy every moment of that). ~~aaand also I erected a lot~~
|
||||
- Mood
|
||||
- Generally excited, but sometimes exhausted from these happy feelings, I deserve a good sleep.
|
||||
-
|
||||
- Todo
|
||||
- DONE Edx 写一篇 blues
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-07 Fri 14:36:18]--[2023-04-07 Fri 16:50:36] => 02:14:18
|
||||
:END:
|
||||
- DONE 概率论作业
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-04-07 Fri 17:31:14]--[2023-04-07 Fri 21:19:06] => 03:47:52
|
||||
:END:
|
||||
- DONE 22, 23, 24, 25, 26, 27, 29
|
||||
- DONE 58, 59
|
||||
-
|
||||
- 乐理学习 #music
|
||||
- LATER 每天学 15 分钟 Open Music Theory [上次学到的地方](https://viva.pressbooks.pub/openmusictheory/chapter/aspn/)
|
||||
SCHEDULED: <2023-05-16 Tue .+1d>
|
||||
:LOGBOOK:
|
||||
- State "DONE" from "LATER" [2023-04-07 Fri 16:50]
|
||||
- State "DONE" from "LATER" [2023-04-07 Fri 16:52]
|
||||
* State "DONE" from "LATER" [2023-04-10 Mon 22:49]
|
||||
* State "DONE" from "LATER" [2023-04-11 Tue 23:35]
|
||||
CLOCK: [2023-04-12 Wed 09:16:56]--[2023-04-12 Wed 09:44:02] => 00:27:06
|
||||
* State "DONE" from "LATER" [2023-04-12 Wed 09:44]
|
||||
* State "DONE" from "LATER" [2023-04-18 Tue 23:31]
|
||||
* State "DONE" from "LATER" [2023-04-21 Fri 09:30]
|
||||
CLOCK: [2023-04-23 Sun 15:18:42]--[2023-04-23 Sun 15:18:43] => 00:00:01
|
||||
* State "DONE" from "NOW" [2023-04-23 Sun 15:18]
|
||||
* State "DONE" from "LATER" [2023-04-26 Wed 22:31]
|
||||
* State "DONE" from "LATER" [2023-05-08 Mon 20:47]
|
||||
CLOCK: [2023-05-09 Tue 09:52:58]--[2023-05-09 Tue 10:01:36] => 00:08:38
|
||||
* State "DONE" from "NOW" [2023-05-09 Tue 10:01]
|
||||
CLOCK: [2023-05-09 Tue 10:11:30]--[2023-05-09 Tue 10:11:31] => 00:00:01
|
||||
CLOCK: [2023-05-11 Thu 10:14:15]--[2023-05-11 Thu 11:16:14] => 01:01:59
|
||||
* State "DONE" from "NOW" [2023-05-11 Thu 11:16]
|
||||
* State "DONE" from "LATER" [2023-05-15 Mon 16:23]
|
||||
:END:
|
||||
- LATER 每天 5 分钟 Ear training [Teoria](https://www.teoria.com/en/exercises/)
|
||||
SCHEDULED: <2023-05-12 Fri .+1d>
|
||||
:LOGBOOK:
|
||||
- State "DONE" from "LATER" [2023-04-07 Fri 23:31]
|
||||
* State "DONE" from "LATER" [2023-04-11 Tue 16:41]
|
||||
* State "DONE" from "LATER" [2023-04-12 Wed 15:07]
|
||||
CLOCK: [2023-04-21 Fri 14:41:07]--[2023-04-21 Fri 14:41:09] => 00:00:02
|
||||
* State "DONE" from "LATER" [2023-04-25 Tue 11:33]
|
||||
* State "DONE" from "LATER" [2023-04-26 Wed 22:31]
|
||||
* State "DONE" from "LATER" [2023-05-08 Mon 20:48]
|
||||
CLOCK: [2023-05-09 Tue 10:01:48]--[2023-05-09 Tue 10:10:01] => 00:08:13
|
||||
* State "DONE" from "LATER" [2023-05-09 Tue 10:10]
|
||||
* State "DONE" from "LATER" [2023-05-11 Thu 20:06]
|
||||
:END:
|
|
@ -23,6 +23,7 @@
|
|||
:END:
|
||||
- LATER Block 1
|
||||
- DONE DBMS
|
||||
collapsed:: true
|
||||
- Relational Database: A database that organizes data into tables with rows and columns, maintaining relationships between tables using keys.
|
||||
- Table: A collection of related data organized into rows (also called records) and columns (also called fields).
|
||||
- Row/Record: A single set of data in a table, representing a specific instance or entity.
|
||||
|
@ -40,6 +41,7 @@
|
|||
- Database Schema: The structure or blueprint of a database, defining the tables, fields, relationships, and constraints.
|
||||
- Database Management System (DBMS): Software that provides an interface to interact with databases, managing their creation, modification, and retrieval.
|
||||
- LATER Forming queries
|
||||
collapsed:: true
|
||||
- DONE Review relational algebra https://www.geeksforgeeks.org/introduction-of-relational-algebra-in-dbms/
|
||||
- LATER review lab2
|
||||
- LATER SQL join
|
||||
|
@ -114,52 +116,122 @@
|
|||
- Boyce-Codd Normal Form (BCNF): BCNF is a stricter form of 3NF that ensures that each determinant in a table is a candidate key. In other words, BCNF ensures that _each non-key attribute is dependent only on the candidate key._
|
||||
- Fourth Normal Form (4NF): 4NF is a further refinement of BCNF that ensures that _a table does not contain any multi-valued dependencies._
|
||||
- Fifth Normal Form (5NF): 5NF is the highest level of normalization and involves decomposing a table into smaller tables to _remove data redundancy and improve data integrity._
|
||||
- LATER Block 4
|
||||
- DONE Block 4
|
||||
- DONE Distributed DBMS
|
||||
collapsed:: true
|
||||
- DONE client server arch
|
||||
collapsed:: true
|
||||
- Computers (client) connected over wired or wireless local area network (LAN)
|
||||
- The database itself and the DBMS are stored on a central device called the database server, which is also connected to the network.
|
||||
- Distributed Database
|
||||
collapsed:: true
|
||||
- A logically interrelated collection of shared data (and a description of this data), physically spread over a computer network.
|
||||
- Distributed DBMS
|
||||
collapsed:: true
|
||||
- Software system that permits the management of the distributed database and makes the distribution transparent to users.
|
||||
- the key issues
|
||||
collapsed:: true
|
||||
- Fragmentation
|
||||
- Allocation
|
||||
- Replication
|
||||
- importance and different types of fragmentation
|
||||
collapsed:: true
|
||||
- Horizontal
|
||||
- Vertical
|
||||
- Mixed
|
||||
- different types of transparency
|
||||
collapsed:: true
|
||||
- Distribution Transparency: The database feels as a single, logical entity
|
||||
- Transaction Transparency: Ensures that all distributed transactions maintain distributed database’s integrity and consistency.
|
||||
- Performance Transparency: must perform as if it were a centralized DBMS.
|
||||
- advantages and disadvantages of distributed databases
|
||||
- LATER XML
|
||||
- DONE XML
|
||||
collapsed:: true
|
||||
- XML definition and basic concepts
|
||||
collapsed:: true
|
||||
- eXtensible Markup Language
|
||||
- A meta-language (i.e. a language for describing other languages) that
|
||||
enables designers to create their own customised tags to provide
|
||||
functionality not available with HTML.
|
||||
- Relational model versus XML
|
||||
- SQL
|
||||
- is a special-purpose programming language
|
||||
- You can: manage data in a relational databases.
|
||||
- XML
|
||||
- is a markup specification language
|
||||
- You can: design ways of describing information (text or data), usually for storage,
|
||||
transmission, or processing by a program (you can use it in combination with a
|
||||
programming language).
|
||||
- It says nothing about what you should do with the data (although your choice of
|
||||
element names may hint at what they are for).
|
||||
collapsed:: true
|
||||
- SQL
|
||||
collapsed:: true
|
||||
- is a special-purpose programming language
|
||||
- You can: manage data in a relational databases.
|
||||
- XML
|
||||
collapsed:: true
|
||||
- is a markup specification language
|
||||
- You can: design ways of describing information (text or data), usually for storage, transmission, or processing by a program (you can use it in combination with a programming language).
|
||||
- It says nothing about what you should do with the data (although your choice of element names may hint at what they are for).
|
||||
- Well-formed XML, Valid XML
|
||||
collapsed:: true
|
||||
- Adheres to basic structural requirements - Single root element
|
||||
- Matched tags, proper nesting
|
||||
- Unique attributes within elements
|
||||
- DTD, XSD
|
||||
- LATER Data Mining
|
||||
- LATER NoSQL
|
||||
- LATER Terms in: [chatGPT](https://chat.openai.com/c/db2ea8df-3bd0-4404-98ae-266afdd8fec1)
|
||||
collapsed:: true
|
||||
- DTD: Defines the valid syntax of an XML document
|
||||
- XSD: a more comprehensive method of defining content model of
|
||||
an XML document.
|
||||
- DONE Data Mining
|
||||
collapsed:: true
|
||||
- concept
|
||||
collapsed:: true
|
||||
- The process of extracting valid, previously unknown, comprehensible,
|
||||
and actionable information from large databases and using it to make
|
||||
crucial business decisions.
|
||||
- different applications
|
||||
collapsed:: true
|
||||
- Retail / Marketing
|
||||
- Banking
|
||||
- Insurance
|
||||
- Medicine
|
||||
- basic techniques
|
||||
collapsed:: true
|
||||
- predictive modelling,
|
||||
collapsed:: true
|
||||
- uses observations to form a model of the important characteristics of some
|
||||
phenomenon
|
||||
- database segmentation,
|
||||
collapsed:: true
|
||||
- Uses unsupervised learning to discover homogeneous subpopulations in a database to improve the accuracy of the profiles.
|
||||
- link analysis,
|
||||
collapsed:: true
|
||||
- Establishing links, called associations, between the individual
|
||||
records, or sets of records, in a database.
|
||||
- deviation detection.
|
||||
collapsed:: true
|
||||
- Identifies outliers, which express deviation from some previously
|
||||
known expectation and norm.
|
||||
- DONE NoSQL
|
||||
collapsed:: true
|
||||
- the motivation for NoSQL
|
||||
collapsed:: true
|
||||
- By giving up ACID constraints, one can achieve
|
||||
much higher performance and scalability.
|
||||
- explain the concepts of NoSQL
|
||||
collapsed:: true
|
||||
- NoSQL databases (aka "not only SQL") are non-tabular databases and store
|
||||
data differently than relational tables. NoSQL databases come in a
|
||||
variety of types based on their data model. The main types are document,
|
||||
key-value, wide-column, and graph. They provide flexible schemas and
|
||||
scale easily with large amounts of data and high user loads.
|
||||
- explain the application areas of NoSQL
|
||||
collapsed:: true
|
||||
- NoSQL is an alternative, non-traditional DB technology to be
|
||||
used in large scale environments where (ACID) transactions are not a priority.
|
||||
- CAP theorem:
|
||||
collapsed:: true
|
||||
- There are 3 main properties for distributed management:
|
||||
1. Consistency → A data item has the same value at the same time (to
|
||||
ensure coherency).
|
||||
2. Availability → Data is available, even if a server is down.
|
||||
3. Partition Tolerance → A query must have an answer, even if the system
|
||||
is partitioned (unless there is a global failure).
|
||||
- DONE Terms in: [chatGPT](https://chat.openai.com/c/db2ea8df-3bd0-4404-98ae-266afdd8fec1)
|
||||
- LATER Exercises
|
||||
- LATER past year exercise 1
|
||||
- LATER past year exercise 2
|
||||
- LATER past year exercise 3
|
||||
- Exercises
|
||||
- Exercises
|
|
@ -0,0 +1,238 @@
|
|||
- [[学习任务]]
|
||||
- DONE 背产开
|
||||
- DONE 下载课件
|
||||
- LATER 写思维导图
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-01 Thu 17:00:59]--[2023-06-01 Thu 17:01:01] => 00:00:02
|
||||
:END:
|
||||
- LATER 看数据库 {{renderer :todomaster}}
|
||||
id:: 647bf024-fa40-4786-9770-e16da8b57f0f
|
||||
- DONE 课件
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-01 Thu 17:01:28]--[2023-06-01 Thu 17:01:30] => 00:00:02
|
||||
CLOCK: [2023-06-01 Thu 17:01:41]--[2023-06-01 Thu 17:38:19] => 00:36:38
|
||||
:END:
|
||||
- DONE Transactions
|
||||
- DONE Distributed DMBSs
|
||||
- DONE XML
|
||||
- DONE Data Mining
|
||||
- DONE NoSQL
|
||||
- LATER Theory
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-04 Sun 16:27:23]--[2023-06-04 Sun 16:54:55] => 00:27:32
|
||||
:END:
|
||||
- LATER Block 1
|
||||
- DONE DBMS
|
||||
collapsed:: true
|
||||
- Relational Database: A database that organizes data into tables with rows and columns, maintaining relationships between tables using keys.
|
||||
- Table: A collection of related data organized into rows (also called records) and columns (also called fields).
|
||||
- Row/Record: A single set of data in a table, representing a specific instance or entity.
|
||||
- Column/Field: A specific attribute or data element within a table.
|
||||
- Primary Key: A unique identifier for each row/record in a table. It ensures the integrity and uniqueness of the data.
|
||||
- Foreign Key: A field in one table that refers to the primary key in another table, establishing a relationship between the two tables.
|
||||
- Relationship: The connection between tables based on common data values, such as primary and foreign keys.
|
||||
- Normalization: The process of organizing and structuring a database design to eliminate redundancy and improve data integrity.
|
||||
- Index: A data structure that improves the retrieval speed of data from a database table by creating a quick reference to the location of the data.
|
||||
- Query: A request for data or information from a database, usually written using Structured Query Language (SQL).
|
||||
- SQL (Structured Query Language): A programming language used to manage and manipulate relational databases. It allows you to create, modify, and retrieve data from databases.
|
||||
- CRUD Operations: An acronym for Create, Read, Update, and Delete operations, which are the basic operations used to manage data in a database.
|
||||
- ACID (Atomicity, Consistency, Isolation, Durability): A set of properties that guarantee the reliability and integrity of database transactions.
|
||||
- Data Integrity: The accuracy, consistency, and reliability of data stored in a database.
|
||||
- Database Schema: The structure or blueprint of a database, defining the tables, fields, relationships, and constraints.
|
||||
- Database Management System (DBMS): Software that provides an interface to interact with databases, managing their creation, modification, and retrieval.
|
||||
- DONE Relational Algrbra
|
||||
- LATER Forming sql queries
|
||||
collapsed:: true
|
||||
- DONE Review relational algebra https://www.geeksforgeeks.org/introduction-of-relational-algebra-in-dbms/
|
||||
- LATER review lab2
|
||||
- LATER SQL join
|
||||
- LATER Block 2
|
||||
- LATER designing ER diagram
|
||||
- DONE Block 3
|
||||
collapsed:: true
|
||||
- DONE DB transaction management
|
||||
- DONE ACID (Atomicity, Consistency, Isolation, Durability): A set of properties that guarantee the reliability and integrity of database transactions.
|
||||
- Atomicity: The property that ensures a transaction is treated as a single, indivisible unit of work. It either executes all its operations successfully or rolls back to the initial state if any operation fails.
|
||||
- Consistency: The property that ensures a transaction transforms the database from one consistent state to another consistent state. It maintains data integrity and adheres to defined business rules.
|
||||
- Isolation: The property that ensures concurrent transactions do not interfere with each other. Each transaction operates in isolation until it completes, preventing interference or conflicts.
|
||||
- Durability: The property that ensures committed changes made by a transaction are permanently saved and will survive any subsequent system failures or crashes.
|
||||
- DONE Concurrency control
|
||||
- DONE Meaning of serialisability.
|
||||
- DONE How locking can ensure serialisability.
|
||||
- Locking achieves serializability by using locks to control access to
|
||||
shared resources (e.g., database objects like tables or rows) and
|
||||
prevent conflicts between concurrent transactions.
|
||||
- DONE 2PL
|
||||
- In the 2PL protocol, transactions acquire and release locks on database
|
||||
objects (e.g., tables, rows) in two distinct phases: the growing phase
|
||||
and the shrinking phase.
|
||||
- DONE Deadlock and how it can be resolved.
|
||||
- A deadlock is a situation in which two or more transactions are unable
|
||||
to proceed because each is waiting for a resource held by the other,
|
||||
resulting in a circular dependency and a system halt. It is a form of
|
||||
resource contention that can occur in concurrent systems, including
|
||||
database management systems.
|
||||
- DONE How timestamping can ensure serialisability.
|
||||
- By using transaction timestamps and enforcing the read and write
|
||||
validation checks, concurrency control mechanisms can ensure that
|
||||
transactions are executed in a way that maintains data consistency and
|
||||
serializability.
|
||||
- DONE Recovery Control
|
||||
- DONE Some causes of database failure.
|
||||
- System crashes, resulting in loss of main memory.
|
||||
- Power failures
|
||||
- Disk crashes, resulting in loss of parts of secondary storage.
|
||||
- Application software errors.
|
||||
- Natural physical disasters.
|
||||
- User mistakes.
|
||||
- Sabotage.
|
||||
- DONE Purpose of transaction log file.
|
||||
- Contains information about all updates to
|
||||
database:
|
||||
- Transaction records.
|
||||
- Checkpoint records.
|
||||
- Often used for other purposes (for example, auditing).
|
||||
- For autiding
|
||||
- DONE Purpose of checkpointing.
|
||||
- When failure occurs, redo all transactions that
|
||||
committed since the checkpoint and undo all
|
||||
transactions active at time of crash.
|
||||
- DONE Normalization
|
||||
background-color:: yellow
|
||||
- DONE Functional dependencies [g4g](https://www.geeksforgeeks.org/types-of-functional-dependencies-in-dbms/)
|
||||
- In a relational database management, functional dependency is a concept
|
||||
that specifies the relationship between two sets of attributes where one
|
||||
attribute determines the value of another attribute. It is denoted as **X → Y**, where the attribute set on the left side of the arrow, **X** is called **Determinant** , and **Y** is called the **Dependent**.
|
||||
- DONE BCNF vs. 3NF
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-01 Thu 17:38:55]--[2023-06-01 Thu 17:38:56] => 00:00:01
|
||||
:END:
|
||||
- DONE kinds of NF [tutorial](https://www.geeksforgeeks.org/normal-forms-in-dbms/)
|
||||
- First Normal Form (1NF): This is the most basic level of
|
||||
normalization. In 1NF, each table cell should contain _only a single value, and each column should have a unique name_. The first normal form helps to eliminate duplicate data and simplify queries.
|
||||
- Second Normal Form (2NF): 2NF eliminates redundant data by requiring that each _non-key attribute_ be dependent on the primary key. This means that _each column should be directly related to the primary key_, and not to other
|
||||
columns.
|
||||
- Third Normal Form (3NF): 3NF builds on 2NF by requiring
|
||||
that _all non-key attributes are independent of each other._ This means that each column should be directly related to the primary key, and not to any other columns in the same table.
|
||||
- Boyce-Codd Normal Form (BCNF): BCNF is a stricter form of 3NF that ensures that each determinant in a table is a candidate key. In other words, BCNF ensures that _each non-key attribute is dependent only on the candidate key._
|
||||
- Fourth Normal Form (4NF): 4NF is a further refinement of BCNF that ensures that _a table does not contain any multi-valued dependencies._
|
||||
- Fifth Normal Form (5NF): 5NF is the highest level of normalization and involves decomposing a table into smaller tables to _remove data redundancy and improve data integrity._
|
||||
- DONE Block 4
|
||||
- DONE Distributed DBMS
|
||||
collapsed:: true
|
||||
- DONE client server arch
|
||||
collapsed:: true
|
||||
- Computers (client) connected over wired or wireless local area network (LAN)
|
||||
- The database itself and the DBMS are stored on a central device called the database server, which is also connected to the network.
|
||||
- Distributed Database
|
||||
collapsed:: true
|
||||
- A logically interrelated collection of shared data (and a description of this data), physically spread over a computer network.
|
||||
- Distributed DBMS
|
||||
collapsed:: true
|
||||
- Software system that permits the management of the distributed database and makes the distribution transparent to users.
|
||||
- the key issues
|
||||
collapsed:: true
|
||||
- Fragmentation
|
||||
- Allocation
|
||||
- Replication
|
||||
- importance and different types of fragmentation
|
||||
collapsed:: true
|
||||
- Horizontal
|
||||
- Vertical
|
||||
- Mixed
|
||||
- different types of transparency
|
||||
collapsed:: true
|
||||
- Distribution Transparency: The database feels as a single, logical entity
|
||||
- Transaction Transparency: Ensures that all distributed transactions maintain distributed database’s integrity and consistency.
|
||||
- Performance Transparency: must perform as if it were a centralized DBMS.
|
||||
- advantages and disadvantages of distributed databases
|
||||
- DONE XML
|
||||
collapsed:: true
|
||||
- XML definition and basic concepts
|
||||
collapsed:: true
|
||||
- eXtensible Markup Language
|
||||
- A meta-language (i.e. a language for describing other languages) that
|
||||
enables designers to create their own customised tags to provide
|
||||
functionality not available with HTML.
|
||||
- Relational model versus XML
|
||||
collapsed:: true
|
||||
- SQL
|
||||
collapsed:: true
|
||||
- is a special-purpose programming language
|
||||
- You can: manage data in a relational databases.
|
||||
- XML
|
||||
collapsed:: true
|
||||
- is a markup specification language
|
||||
- You can: design ways of describing information (text or data), usually for storage, transmission, or processing by a program (you can use it in combination with a programming language).
|
||||
- It says nothing about what you should do with the data (although your choice of element names may hint at what they are for).
|
||||
- Well-formed XML, Valid XML
|
||||
collapsed:: true
|
||||
- Adheres to basic structural requirements - Single root element
|
||||
- Matched tags, proper nesting
|
||||
- Unique attributes within elements
|
||||
- DTD, XSD
|
||||
collapsed:: true
|
||||
- DTD: Defines the valid syntax of an XML document
|
||||
- XSD: a more comprehensive method of defining content model of
|
||||
an XML document.
|
||||
- DONE Data Mining
|
||||
collapsed:: true
|
||||
- concept
|
||||
collapsed:: true
|
||||
- The process of extracting valid, previously unknown, comprehensible,
|
||||
and actionable information from large databases and using it to make
|
||||
crucial business decisions.
|
||||
- different applications
|
||||
collapsed:: true
|
||||
- Retail / Marketing
|
||||
- Banking
|
||||
- Insurance
|
||||
- Medicine
|
||||
- basic techniques
|
||||
collapsed:: true
|
||||
- predictive modelling,
|
||||
collapsed:: true
|
||||
- uses observations to form a model of the important characteristics of some
|
||||
phenomenon
|
||||
- database segmentation,
|
||||
collapsed:: true
|
||||
- Uses unsupervised learning to discover homogeneous subpopulations in a database to improve the accuracy of the profiles.
|
||||
- link analysis,
|
||||
collapsed:: true
|
||||
- Establishing links, called associations, between the individual
|
||||
records, or sets of records, in a database.
|
||||
- deviation detection.
|
||||
collapsed:: true
|
||||
- Identifies outliers, which express deviation from some previously
|
||||
known expectation and norm.
|
||||
- DONE NoSQL
|
||||
collapsed:: true
|
||||
- the motivation for NoSQL
|
||||
collapsed:: true
|
||||
- By giving up ACID constraints, one can achieve
|
||||
much higher performance and scalability.
|
||||
- explain the concepts of NoSQL
|
||||
collapsed:: true
|
||||
- NoSQL databases (aka "not only SQL") are non-tabular databases and store
|
||||
data differently than relational tables. NoSQL databases come in a
|
||||
variety of types based on their data model. The main types are document,
|
||||
key-value, wide-column, and graph. They provide flexible schemas and
|
||||
scale easily with large amounts of data and high user loads.
|
||||
- explain the application areas of NoSQL
|
||||
collapsed:: true
|
||||
- NoSQL is an alternative, non-traditional DB technology to be
|
||||
used in large scale environments where (ACID) transactions are not a priority.
|
||||
- CAP theorem:
|
||||
collapsed:: true
|
||||
- There are 3 main properties for distributed management:
|
||||
1. Consistency → A data item has the same value at the same time (to
|
||||
ensure coherency).
|
||||
2. Availability → Data is available, even if a server is down.
|
||||
3. Partition Tolerance → A query must have an answer, even if the system
|
||||
is partitioned (unless there is a global failure).
|
||||
- DONE Terms in: [chatGPT](https://chat.openai.com/c/db2ea8df-3bd0-4404-98ae-266afdd8fec1)
|
||||
- LATER Exercises
|
||||
- LATER past year exercise 1
|
||||
- LATER past year exercise 2
|
||||
- LATER past year exercise 3
|
||||
- Exercises
|
|
@ -0,0 +1,56 @@
|
|||
- [[学习任务]]
|
||||
- LATER 概率论 {{renderer :todomaster}}
|
||||
id:: 647bf024-41f1-45e7-afaf-f49026e826d6
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-03 Sat 16:47:39]--[2023-06-03 Sat 16:47:40] => 00:00:01
|
||||
:END:
|
||||
- LATER 学积分
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-03 Sat 17:05:07]--[2023-06-03 Sat 17:05:08] => 00:00:01
|
||||
CLOCK: [2023-06-03 Sat 21:07:06]--[2023-06-03 Sat 21:07:07] => 00:00:01
|
||||
CLOCK: [2023-06-03 Sat 21:07:17]--[2023-06-03 Sat 21:07:18] => 00:00:01
|
||||
:END:
|
||||
- DONE 网课
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-03 Sat 21:07:14]--[2023-06-03 Sat 21:07:20] => 00:00:06
|
||||
CLOCK: [2023-06-03 Sat 21:07:21]--[2023-06-03 Sat 21:07:22] => 00:00:01
|
||||
:END:
|
||||
- LATER 写题(作业,对答案)
|
||||
- LATER 总复习, 考试6.19,杰克6.8
|
||||
- LATER 看完网课和串讲
|
||||
- LATER 写思维导图
|
||||
- LATER 做题
|
||||
- DONE 区块链:实验报告
|
||||
- DONE java,下周小测 [qm website](https://qmplus.qmul.ac.uk/mod/page/view.php?id=2178228)
|
||||
SCHEDULED: <2023-06-07 Wed>
|
||||
- DONE 课件
|
||||
- DONE lab
|
||||
- DONE lab6
|
||||
- DONE lab7
|
||||
- DONE PDP quiz
|
||||
SCHEDULED: <2023-06-15 Thu>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-04 Sun 16:18:08]--[2023-06-04 Sun 16:27:03] => 00:08:55
|
||||
:END:
|
||||
-
|
||||
- Daily reflection [[Daily reflections]]
|
||||
collapsed:: true
|
||||
- What I've done
|
||||
- 早上看数据库
|
||||
- 下午看概率论,看了点书
|
||||
- 晚上荒野大镖客,看完概率论和数据库
|
||||
- 发现洗的衣服忘拿了
|
||||
- What I've thought #thoughts
|
||||
- [[情感]]
|
||||
- 这几天没有睡好,有点抑郁,一方面是因为生了病没睡好,但主要是因为我的异性关系没有处理好。现在就很能共情[[老残游记]]里面的恋爱场景,一旦相隔远了没有消息,在床上翻来覆去睡不着的场景:一会觉得对方是好得极好,一会又觉得对方好像一无是处。我跟她也hang out了很多次了也进行了不少自我表露,但是那天我们突然就不再联系。
|
||||
- 过去和现状:现在回忆起来,当时我是提出餐厅约会受拒,心情不好也顺便推掉了study date(不过她也没有如此的打算,和室友一起),后来遇见她也是跟着室友一起,会跟我打招呼,但是我几次找她,她都借故推脱,再之后就没有了联系。直到最近她主动跟我找话,但是因为之前她拒绝的时候同时拒绝了study date的主要工具,我也没有办法继续找借口交往。到现在我们在群聊等公众场合互相避让,不回复互相的信息。
|
||||
- 抑郁的原因:
|
||||
- 我被拒绝
|
||||
- 我感觉被操纵,她对我的情感表露不真诚。感觉她和我的交往有很多套路性的元素,就像主动拒绝study date,故意秒回,故作高冷。这些方法在统计学学上只会降低对异性的吸引力。
|
||||
- 之前通过线上途径交往十分不理想,人的需求不能得到及时满足,因为她会故意晚回我的消息(这一点不完全有把握,是因为看见她会秒回别人的消息
|
||||
- 一直挂着没有联系,这一方面是因为二和三,一方面也是因为话题被她切断,没有办法
|
||||
- 怎么办
|
||||
- 到现在已经没什么主动办法,因为聊天的线索被切断,其他活动型的date她大概率不会接受,因为快要期末了
|
||||
- 唯一的办法是一直憋着不表示,不明确拒绝她也不主动接近她,先让她急起来,主动放弃这些套路,然后再跟随着flow来
|
||||
- 如果一周没有进展的话,我就应该主动放弃,尽量回避不能再这样互相消耗了
|
||||
- Mood
|
|
@ -1,4 +0,0 @@
|
|||
- [[学习任务]]
|
||||
- Test timetable
|
||||
- ![2023-06-09-13-21-19.jpeg](../assets/2023-06-09-13-21-19.jpeg)
|
||||
-
|
|
@ -84,7 +84,7 @@
|
|||
- LATER 整理错题
|
||||
- LATER [[学交]] {{renderer :todomaster}}
|
||||
SCHEDULED: <2023-06-13 Tue>
|
||||
- LATER 看格式要求 *Follow the ABC (Abstract Body Conclusion) Format for all Letters/Memos*
|
||||
- DONE 看格式要求 *Follow the ABC (Abstract Body Conclusion) Format for all Letters/Memos*
|
||||
- DONE Job application letter
|
||||
- Cover letter (application letter)
|
||||
- #+BEGIN_VERSE
|
||||
|
@ -113,7 +113,7 @@
|
|||
Sincerely,
|
||||
[Your name]
|
||||
#+END_VERSE
|
||||
- LATER Academic
|
||||
- DONE Academic
|
||||
- DONE research proposal
|
||||
- Format
|
||||
- #+BEGIN_VERSE
|
||||
|
@ -157,20 +157,17 @@
|
|||
a list of references to key articles and texts discussed within your research proposal
|
||||
a selection of sources appropriate to the proposed research
|
||||
#+END_VERSE
|
||||
- LATER academic paper
|
||||
- DONE academic paper
|
||||
- DONE abstract
|
||||
collapsed:: true
|
||||
- Major Types of Abstract - Descriptive Abstracts
|
||||
collapsed:: true
|
||||
- ● Short -uaually less than 120 words.
|
||||
- ● Includes:
|
||||
collapsed:: true
|
||||
- ● purpose of the paper/work (objectives)
|
||||
- ● metho used
|
||||
- ● scope of the paper/work
|
||||
- ● introducing the subject.
|
||||
- ● Doesn’t include:
|
||||
collapsed:: true
|
||||
- ● results, conclusions and recommendations
|
||||
- It aims to provide the reader with brief summaries (1-2 sentences) of each of the sections of the paper.
|
||||
- ● A descriptive abstract summarizes the main points of a document without
|
||||
|
@ -179,10 +176,8 @@
|
|||
what you would find in the document's table of contents.
|
||||
- ● An outline of your work
|
||||
- •Major Types of Abstract - Informative Abstracts
|
||||
collapsed:: true
|
||||
- ● Fairly short - from 250 words to a page or more.
|
||||
- ● Include:
|
||||
collapsed:: true
|
||||
- ● purpose of the work/paper (research background /objectives)
|
||||
- ● method used
|
||||
- ● scope of the work
|
||||
|
@ -193,6 +188,7 @@
|
|||
conclusion, contribution and vovelty that can be drawn from these
|
||||
results.
|
||||
- DONE introduction
|
||||
collapsed:: true
|
||||
- a clear sense of purpose,
|
||||
thorough understanding of reader needs, and
|
||||
close attention to correct formats.
|
||||
|
@ -230,11 +226,12 @@
|
|||
depending on your field. For example, a physics research paper might
|
||||
emphasize methodology. An English journal article might highlight the
|
||||
overview.
|
||||
- LATER conclusion
|
||||
- - Presenting the last word on the issues you raised in your paper.
|
||||
- Summarizing your thoughts and conveying the larger implications of your study.
|
||||
- Demonstrating the importance of your ideas.
|
||||
- Introducing possible new or expanded ways of thinking about the research problem.
|
||||
- DONE conclusion
|
||||
collapsed:: true
|
||||
- Presenting the last word on the issues you raised in your paper.
|
||||
- Summarizing your thoughts and conveying the larger implications of your study.
|
||||
- Demonstrating the importance of your ideas.
|
||||
- Introducing possible new or expanded ways of thinking about the research problem.
|
||||
- DONE Report
|
||||
- Informal
|
||||
- DONE letter report
|
|
@ -0,0 +1,128 @@
|
|||
- [[学习任务]]
|
||||
-
|
||||
- Daily reflection [[Daily reflections]]
|
||||
- What I've done
|
||||
- Morning: Workout
|
||||
- Afternoon: Review [[产品开发]] and [[Java]]
|
||||
- Night: Review 数电 学交
|
||||
- What I've thought #thoughts
|
||||
- Mood
|
||||
-
|
||||
- [[产品开发]]
|
||||
collapsed:: true
|
||||
- ## Topic 6 - 10
|
||||
- ## Topic 6 - Phase 1: Concept Development 概念开发
|
||||
id:: 6482bafb-b96b-44c3-834b-8b4966c1dc0c
|
||||
collapsed:: true
|
||||
- What is Concept Development? 概念开发是什么
|
||||
- The needs of the target market are identified
|
||||
Alternative product concepts are generated and
|
||||
evaluated 需求
|
||||
One or more concepts are selected for further
|
||||
development and testing 多种概念被生成,经过挑选后选择其中一个
|
||||
A concept is a description of the form, function
|
||||
and features of a product 概念是一个产品的描述,功能和特性
|
||||
Evaluation and screening criteria are used to aid
|
||||
in the selection 评估和测试可以辅助选择(screen = test)
|
||||
Usually accompanied by a set of specifications, an
|
||||
analysis of competitive products and an economic
|
||||
justification for the project 伴随着来自个方面的要求,与竞争对手的比较和分析,还有经济方面的考虑(能不能赚钱)
|
||||
- This can be concluded as 图解如下
|
||||
- ![image.png](../assets/image_1686289806889_0.png)
|
||||
- #### Identify Customer Needs 用户需求是什么
|
||||
- to understand customers needs,
|
||||
then to effectively communicate them to the
|
||||
development team 和研发队伍沟通
|
||||
The output of this step is:
|
||||
Customer need statements organised in a
|
||||
hierarchical list, with importance weightings
|
||||
for many or all of the needs 把用户的需求整理成加权列表
|
||||
- #### Establishing target specifications 确立规格要求
|
||||
- 1. Prepare the list of metrics, i.e. the technical or
|
||||
manufacturing features of the product based on
|
||||
the customer needs 准备一些数据的列表
|
||||
- 2. Collect competitive benchmarking information 竞争对手的产品性能
|
||||
- 3. Set ideal and marginally acceptable target values 理想的和可接受的要求
|
||||
- 4. Reflect on the results and the process 通过结果和进一步完善
|
||||
- #### Concept generation 想一个概念
|
||||
- Steps:
|
||||
- external search 在外面搜索
|
||||
- creative problem solving within the team, and 团队灵机一动
|
||||
- systematic exploration of the various solution
|
||||
fragments the team generates 系统地寻找解决方法
|
||||
- The result of this activity is usually a set of 10-20
|
||||
concepts – each is typically represented by a sketch
|
||||
and a brief descriptive text 产生 10-20 个概念
|
||||
- ![image.png](../assets/image_1686289726119_0.png)
|
||||
- #### Concept selection 选一两个出来
|
||||
- the activity in which various
|
||||
product concepts are analysed and sequentially
|
||||
eliminated to identify the most promising
|
||||
concept(s)
|
||||
- ![image.png](../assets/image_1686289907417_0.png){:height 564, :width 688}
|
||||
- There are 5 stages to the screening and
|
||||
evaluation process: 用以下方式选择好的概念
|
||||
- 1. Initial screen - The key evaluation criteria given in the table on the
|
||||
previous slides can be developed further using a
|
||||
scoring model or weighted checklist 用之前的要求测试
|
||||
- 2. Customer screen - An informal discussion with customers to
|
||||
explain a concept 和客户沟通
|
||||
- 3. Technical screen 在科技实现上咨询第一方和第三方的专家
|
||||
- informal technical discussions with experts
|
||||
- extensive analysis by a 3 rd party
|
||||
- 4. Final screen 最终测试
|
||||
- Involves the use of screening models and computer assessment programs
|
||||
- 5. Business analysis 看下赚不赚钱
|
||||
- preliminary marketing plans,
|
||||
- technical plans,
|
||||
- financial reviews and
|
||||
- projected budgets
|
||||
- #### Concept testing 测试
|
||||
- There are 7 steps to this process
|
||||
- 1. Define the purpose of the concept test 定义测试的目的
|
||||
- 2. Choose a survey population 选问卷调查的目标对象
|
||||
- 3. Choose a survey format 格式
|
||||
- 4. Communicate the concept 和目标对象沟通这个概念
|
||||
- 5. Measure customer response 客户怎么想
|
||||
- 6. Interpret the results 分析结果
|
||||
- 7. Reflect on the results and process 用结果改进
|
||||
- #### Setting final specifications 最终规格
|
||||
Target specifications are revisited after a concept has been selected and tested
|
||||
- #### Project planning 计划
|
||||
- The final activity of concept development
|
||||
- Steps:
|
||||
- creates a detailed development schedule 产品开发时间线
|
||||
- devises a strategy to minimise development time and 定一个计划
|
||||
- identifies the resources required to complete the project 需求是什么
|
||||
- #### Economic analysis
|
||||
- 拿出去卖亏不亏钱
|
||||
- #### Benchmarking & modelling
|
||||
- 和竞争对手比较,品质行不行
|
||||
- ## 往年题考点
|
||||
- ### Prototypes (2019)
|
||||
- Physical prototype, (5 marks) (2019)
|
||||
- Analytical prototype, (5 marks) (2019)
|
||||
- Comprehensive prototype. (5 marks) (2019)
|
||||
- ### Costs (2019)
|
||||
- Component costs, (5 marks) (2019)
|
||||
- Support costs, (5 marks) (2019)
|
||||
- Indirect allocations as part of Overhead costs. (5 marks) (2019)
|
||||
- ### New products and New product development (2019, 2018)
|
||||
- #### Booz, Allen & Hamilton (1982) Classification Scheme (2019)
|
||||
- Repositioning (4 marks) (2019)
|
||||
- four (4) elements through which products can be differentiated (2019)
|
||||
- the five alternatives that are open to the firm ( 2018)
|
||||
- kinds of new products identified by Booz Allen and Hamilton ( 2018)
|
||||
- four elements where values can be added to the basic or ‘core’ product to augment its appeal ( 2018)
|
||||
- Product life cycle (2019)
|
||||
- #### prototyping ( 2018)
|
||||
- three phases of prototyping ( 2018)
|
||||
- uses of prototypes ( 2018)
|
||||
- ### system-level design (2019)
|
||||
- product architecture (2019)
|
||||
- key characteristics of modular and integral architecture. (2019)
|
||||
- three (3) main types of modular architecture. (2019)
|
||||
- ### IP ( 2018)
|
||||
- the concept ( 2018)
|
||||
- what sort of intellectual property copyright can protect and what form of protection it gives. ( 2018)
|
||||
- benefits and limitations of using patents ( 2018)
|
|
@ -1,660 +0,0 @@
|
|||
- Daily reflection [[Daily reflections]]
|
||||
id:: 64856c09-6826-4ed3-b21e-380d43ea95a6
|
||||
- What I've done
|
||||
- 上午看[[学交]],写[[数据库]]题
|
||||
- What I've thought #thoughts
|
||||
- Mood
|
||||
-
|
||||
- [[产品开发]]
|
||||
- ## Topic 7: Innovation
|
||||
id:: 64857305-2925-485f-9aed-e15511b42149
|
||||
collapsed:: true
|
||||
- ### Definition of Innovation
|
||||
Innovation is the process of creating something new that adds value to society. It can involve developing new products, services, processes, or business models. Innovation can be driven by a variety of factors, such as technological advances, changes in consumer preferences, or shifts in the competitive landscape.
|
||||
- ### Types of Innovation
|
||||
collapsed:: true
|
||||
There are different types of innovation, including:
|
||||
- Radical innovation: involves creating something entirely new that disrupts existing markets or creates new ones.
|
||||
- Incremental innovation: involves making small improvements to existing products or processes.
|
||||
- Disruptive innovation: involves creating a new product or service that initially serves a niche market but eventually disrupts the existing market.
|
||||
- Sustaining innovation: involves making improvements to existing products or processes that help maintain a company's competitive position.
|
||||
- ### Models of Innovation
|
||||
collapsed:: true
|
||||
Innovation can follow different models, such as:
|
||||
- Linear model: involves a sequential process of research, development, and commercialization.
|
||||
- Cyclical model: involves a continuous process of feedback and iteration.
|
||||
- Open innovation: involves collaborating with external partners to develop new products or services.
|
||||
- ### Characteristics of Innovative Companies
|
||||
collapsed:: true
|
||||
Innovative companies share certain characteristics, such as:
|
||||
- A willingness to take risks and experiment with new ideas.
|
||||
- A focus on customer needs and preferences.
|
||||
- A culture that encourages creativity, collaboration, and learning.
|
||||
- A commitment to continuous improvement and innovation.
|
||||
- ### Strategies for Fostering a Culture of Innovation
|
||||
collapsed:: true
|
||||
Companies can foster a culture of innovation by:
|
||||
- Providing resources, such as funding, time, and expertise, to support innovation initiatives.
|
||||
- Encouraging collaboration and cross-functional teams.
|
||||
- Rewarding creativity and risk-taking.
|
||||
- Creating a supportive and inclusive work environment.
|
||||
- ### Examples of Innovative Companies and Products
|
||||
collapsed:: true
|
||||
There are many examples of innovative companies and products, such as:
|
||||
- Apple: known for its innovative products, such as the iPhone and iPad.
|
||||
- Tesla: known for its innovative electric vehicles and renewable energy solutions.
|
||||
- Sinclair C5: an innovative electric vehicle developed in the 1980s that was ahead of its time.
|
||||
- ### Further Resources
|
||||
The PDF provides links to further resources for learning about innovation, such as a video and short videos about new inventions. These resources can help individuals and companies stay up-to-date on the latest trends and developments in innovation and product development.
|
||||
- ## Topic 7 PDF 概述
|
||||
collapsed:: true
|
||||
本 PDF 文件提供了创新和产品开发的概述。它涵盖了创新的基本原则、创新的类型、创新的模型以及什么使一个创新型公司。
|
||||
- ## 涵盖的主题
|
||||
collapsed:: true
|
||||
- 创新的定义
|
||||
- 创新的类型(根本性、渐进性、破坏性、维持性)
|
||||
- 创新的模型(线性、循环、开放式创新)
|
||||
- 创新型公司的特点
|
||||
- 培养创新文化的策略
|
||||
- 创新型公司和产品的例子
|
||||
- 进一步阅读的资源(包括一个视频和关于新发明的短视频)
|
||||
- ## 主要观点
|
||||
collapsed:: true
|
||||
- 创新是创造新的、对社会有价值的东西的过程。
|
||||
- 有不同类型的创新,包括根本性、渐进性、破坏性和维持性。
|
||||
- 创新可以遵循不同的模型,如线性、循环或开放式创新。
|
||||
- 创新型公司共享某些特点,如愿意冒险、关注客户需求和鼓励实验和学习的文化。
|
||||
- 公司可以通过提供资源、鼓励协作和奖励创造力来培养创新文化。
|
||||
- 创新型公司和产品的例子包括苹果、特斯拉和辛克莱 C5 电动车。
|
||||
- 进一步了解创新的资源包括一个视频和关于新发明的短视频。
|
||||
- ### 创新的定义
|
||||
创新是创造新的、对社会有价值的东西的过程。它可以涉及开发新产品、服务、流程或商业模式。创新可以由各种因素驱动,如技术进步、消费者偏好的变化或竞争格局的转变。
|
||||
- ### 创新的类型
|
||||
collapsed:: true
|
||||
有不同类型的创新,包括:
|
||||
- 根本性创新:涉及创造全新的东西,打破现有市场或创建新市场。
|
||||
- 渐进性创新:涉及对现有产品或流程进行小幅改进。
|
||||
- 破坏性创新:涉及创建一个最初服务于利基市场但最终打破现有市场的新产品或服务。
|
||||
- 维持性创新:涉及对现有产品或流程进行改进,以帮助维持公司的竞争地位。
|
||||
- ### 创新的模型
|
||||
collapsed:: true
|
||||
创新可以遵循不同的模型,如:
|
||||
- 线性模型:涉及研究、开发和商业化的顺序过程。
|
||||
- 循环模型:涉及反馈和迭代的持续过程。
|
||||
- 开放式创新:涉及与外部合作伙伴合作开发新产品或服务。
|
||||
- ### 创新型公司的特点
|
||||
collapsed:: true
|
||||
创新型公司共享某些特点,如:
|
||||
- 愿意冒险和尝试新想法。
|
||||
- 关注客户需求和偏好。
|
||||
- 鼓励创造力、协作和学习的文化。
|
||||
- 致力于持续改进和创新。
|
||||
- ### 培养创新文化的策略
|
||||
collapsed:: true
|
||||
公司可以通过以下方式培养创新文化:
|
||||
- 提供资源,如资金、时间和专业知识,支持创新项目。
|
||||
- 鼓励协作和跨职能团队。
|
||||
- 奖励创造力和冒险精神。
|
||||
- 创造一个支持性和包容性的工作环境。
|
||||
- ### 创新型公司和产品的例子
|
||||
collapsed:: true
|
||||
有许多创新型公司和产品的例子,如:
|
||||
- 苹果:以其创新产品,如 iPhone 和 iPad 而闻名。
|
||||
- 特斯拉:以其创新的电动汽车和可再生能源解决方案而闻名。
|
||||
- 辛克莱 C5:一款在 1980 年代开发的创新电动车,领先于其时代。
|
||||
- ### 进一步资源
|
||||
本 PDF 文件提供了进一步了解创新的资源链接,如一个视频和关于新发明的短视频。这些资源可以帮助个人和公司了解创新和产品开发的最新趋势和发展。
|
||||
- ## Topic 8: Digital Transofrmation and Digital Products
|
||||
id:: 64857305-a186-4927-890d-607f66d97f95
|
||||
collapsed:: true
|
||||
- Digital Transformation
|
||||
collapsed:: true
|
||||
- Terms
|
||||
collapsed:: true
|
||||
- **Digitisation** is the process of converting information from analog to digital.
|
||||
- **Digitalisation** is the process of using digitised information to make established ways of working simpler and more efficient.
|
||||
- **Digital transformation** is the process of using digital technologies to create new — or modify existing — business processes, culture, and customer experiences to meet changing business and market requirements
|
||||
- **Types** of Digital transformation
|
||||
collapsed:: true
|
||||
- **Process Transformation** – aims to process such as data, analytics, AI, and any process that can work towards lowering costs and driving operational efficiency in the business.
|
||||
- **Business Model Transformation** – aims to make fundamental changes in how a business or organization runs which can include personnel, processes, and technology.
|
||||
- **Domain Transformation** - This area offers a great opportunity to move into a new domain or area that a business may not have explored before by acquiring new technologies.
|
||||
- **Cultural/Organizational Transformation** -
|
||||
This is about redefining mindsets, processes, capabilities and skills for a digital world. It’s about driving digital transformation forward through growth initiatives that are grounded in a new culture and way of thinking.
|
||||
- **Guidelines** for a successful Digital
|
||||
collapsed:: true
|
||||
Transformation
|
||||
- Understand your technology
|
||||
- Embrace Cultural Change
|
||||
- Consider a new digital business model
|
||||
- Digital upskilling
|
||||
- Ensure Collaboration
|
||||
- Top Management Support
|
||||
- Digital Product
|
||||
collapsed:: true
|
||||
- Characteristics
|
||||
collapsed:: true
|
||||
- no physical form, exist only in the digital realm,
|
||||
- _intangible_ items delivered _electronically_,
|
||||
- anything that can be _downloaded_ and _used digitally_ can be considered a digital product,
|
||||
- sold online or through brick-and-mortar retailers,
|
||||
- can be easily updated or modified to keep up with changing technology and trends because they're intangible,
|
||||
- often come with a license that allows a customer to use them in unlimited ways.
|
||||
- Will everything become digital?
|
||||
collapsed:: true
|
||||
- In practice, most products and experiences they are part of are _hybrid_.
|
||||
- **Why** digital products?
|
||||
collapsed:: true
|
||||
- Customer happiness is how you win in business. Modern customer expectations are being driven by largely digital technology and digital innovations.
|
||||
- Low investment, (potentially) high returns
|
||||
- More profitable than physical goods
|
||||
- No inventory, shipping or rent hassle
|
||||
- Automated delivery for passive income
|
||||
- Serve a niche at scale
|
||||
- Digital products offer unique ways to communicate directly with the customers.
|
||||
- Digital Project Development
|
||||
collapsed:: true
|
||||
- Phase 1. **Discovery**: the process of identifying the problem to be
|
||||
solved, making sure the problem is worth solving, and
|
||||
envisioning the solution to that problem.
|
||||
- Phase 2. **Ideate**: The goal is to brainstorm possible solutions to the
|
||||
problem identified in the discovery phase, creating a
|
||||
strategy for how to build a product that will solve that
|
||||
problem.
|
||||
- Phase 3. **Test**: The testing phase is all about gathering data,
|
||||
refining and improving your idea, and gathering more data
|
||||
until you have a sharp idea. The testing phase should
|
||||
involve at least four steps, known as the lean validation
|
||||
process
|
||||
- Phase 4. **Execute**: This stage aims to develop the“most
|
||||
valuable player” namely the _Minimum Viable
|
||||
Product (MVP)._
|
||||
- Phase 5. **Launch**: Once your MVP is ready to go, it’s time to launch. A
|
||||
digital product launch usually means putting the MVP
|
||||
on the market and giving customers their first crack at
|
||||
your solution.
|
||||
- Phase 6. **Grow**: As refine the digital product into its final form, based on
|
||||
the feedback from the MVP launch, it’s time to consider
|
||||
the growth or scaling phase.
|
||||
- Digital Project Management
|
||||
collapsed:: true
|
||||
- Terms
|
||||
collapsed:: true
|
||||
- **Digital Project Manager**: the glue that brings
|
||||
together many facets of a successful digital product—
|
||||
customers, design, engineering, operations, sales,
|
||||
marketing, finance, compliance, legal, and more.
|
||||
- **Project Team for Digital Products**:
|
||||
collapsed:: true
|
||||
A project team for digital product is made up of:
|
||||
- **Developers or engineers** – the people who will code, test and deploy the digital application that will be used by customers.
|
||||
- **Experts in customer or user experience** who focus on how the product and associated services will be used by the customer, and who create the user interface, services and other interactions with the customers
|
||||
- **Sales and marketing experts**, who will actually get customers to use the product.
|
||||
- mistakes to avoid
|
||||
collapsed:: true
|
||||
- Having the _wrong data_
|
||||
- _Resistance_ from staff
|
||||
- Underestimate _costs_
|
||||
- A lack of _commitment_
|
||||
- A lack of _skills_
|
||||
- ## 主题 8
|
||||
collapsed:: true
|
||||
- 数字化转型
|
||||
collapsed:: true
|
||||
- 术语
|
||||
collapsed:: true
|
||||
- **数字化** 是将信息从模拟形式转换为数字形式的过程。
|
||||
- **数字化** 是利用数字化的信息使现有的工作方式更简单、更高效的过程。
|
||||
- **数字化转型** 是利用数字技术来创建新的或修改现有的业务流程、文化和客户体验,以满足不断变化的业务和市场需求的过程。
|
||||
- 数字化转型的**类型**
|
||||
collapsed:: true
|
||||
- **流程转型** - 旨在通过数据、分析、人工智能以及任何可以降低成本并提高业务运营效率的流程来实现。
|
||||
- **商业模式转型** - 旨在对企业或组织的运营进行根本性改变,包括人员、流程和技术。
|
||||
- **领域转型** - 这个领域为企业提供了进入新领域或领域的机会,通过获取新技术来实现。
|
||||
- **文化/组织转型** - 这涉及到重新定义数字世界中的思维方式、流程、能力和技能。通过以新的文化和思维方式为基础的增长举措,推动数字化转型的进程。
|
||||
- 实现成功数字化转型的**指南**
|
||||
collapsed:: true
|
||||
- 了解您的技术
|
||||
- 接受文化变革
|
||||
- 考虑新的数字商业模式
|
||||
- 数字技能提升
|
||||
- 确保合作
|
||||
- 高层管理支持
|
||||
- 数字产品
|
||||
collapsed:: true
|
||||
- 特点
|
||||
collapsed:: true
|
||||
- 无实体形态,只存在于数字领域
|
||||
- *无形*产品通过*电子方式*交付
|
||||
- 任何可以*下载*和*数字使用*的物品都可以被视为数字产品
|
||||
- 在线销售或通过实体零售商销售
|
||||
- 可以轻松更新或修改以跟上技术和趋势的变化,因为它们是无形的
|
||||
- 通常附带许可证,允许客户以无限的方式使用它们
|
||||
- 所有事物都会变成数字吗?
|
||||
collapsed:: true
|
||||
- 实际上,大多数产品和体验都是*混合型*的。
|
||||
- **为什么**选择数字产品?
|
||||
collapsed:: true
|
||||
- 客户的幸福感是赢得业务的关键。现代客户的期望主要受数字技术和数字创新的推动。
|
||||
- 投资低,(可能)回报高
|
||||
- 比实体商品更具盈利能力
|
||||
- 无需库存、物流或租金麻烦
|
||||
- 自动化交付实现被动收入
|
||||
- 以规模服务于细分市场
|
||||
- 数字产品提供了与客户直接沟通的独特方式。
|
||||
- 数字项目开发
|
||||
collapsed:: true
|
||||
- 第一阶段 **发现**:识别待解决的问题,确保问题值得解决,并构想解决问题的方案。
|
||||
- 第二阶段 **构思**:目标是对发现阶段确定的问题进行头脑风暴,创建构建解决该问题的产品的策略。
|
||||
- 第三阶段 **测试**:测试阶段涉及收集数据、完善和改进您的想法,并收集更多数据,直到您拥有一个清晰的想法。测试阶段应包括至少四个步骤,即精益验证过程。
|
||||
- 第四阶段 **执行**:这个阶段旨在开发最有价值的产品,即*最小可行产品 (MVP)*。
|
||||
- 第五阶段 **发布**:一旦您的 MVP 准备就绪,就可以发布了。数字产品的发布通常意味着将 MVP 推向市场,让客户首次体验您的解决方案。
|
||||
- 第六阶段 **增长**:在根据 MVP 发布的反馈对数字产品进行最终形态的改进时,是考虑增长或扩展阶段的时候。
|
||||
- 数字项目管理
|
||||
collapsed:: true
|
||||
- 术语
|
||||
collapsed:: true
|
||||
- **数字项目经理**:他们将许多方面成功地融合在一起,包括客户、设计、工程、运营、销售、市场营销、财务、合规性、法律等等。
|
||||
- **数字产品项目团队**:数字产品项目团队由以下成员组成:
|
||||
collapsed:: true
|
||||
- **开发人员或工程师** - 负责编码、测试和部署将由客户使用的数字应用程序的人员。
|
||||
- **用户体验专家** - 关注产品和相关服务如何被客户使用,并创建与客户的界面、服务和其他交互。
|
||||
- **销售和市场营销专家** - 将实际使客户使用产品。
|
||||
- 需要避免的错误
|
||||
collapsed:: true
|
||||
- 使用*错误的数据*
|
||||
- 员工*抵触*
|
||||
- 低估*成本*
|
||||
- 缺乏*承诺*
|
||||
- 缺乏*技能*
|
||||
- ## Topic 2: Project Management
|
||||
id:: 648581e7-cc5c-4514-9c2a-0b6af4adc5bb
|
||||
collapsed:: true
|
||||
- **Define** what is project management
|
||||
collapsed:: true
|
||||
- For all but the simplest products, product development involves many people completing many different tasks.
|
||||
- is the activity of planning and coordinating resources and tasks to achieve these goals.
|
||||
- Two Phases of **PM**
|
||||
collapsed:: true
|
||||
- Project planning involves scheduling the project tasks and determining resource requirements. The project plan is first laid out during the concept development phase, although it is a dynamic entity and continues to evolve throughout the development process.
|
||||
- Project execution, sometimes called project control, involves coordinating and facilitating the myriad tasks required to complete the project in the face of inevitable unanticipated events and the arrival of new information. Execution is just as important as planning; Many teams fail because they do not remain focused on their goals for the duration of the project.
|
||||
- **Project Planning**: Understand and represent different tasks in projects
|
||||
collapsed:: true
|
||||
- Sequential, Parallel, and Coupled Tasks
|
||||
collapsed:: true
|
||||
- ![image.png](../assets/image_1686471430664_0.png)
|
||||
- The Design Structure Matrix
|
||||
collapsed:: true
|
||||
- **Definition**: A useful tool for representing and analysing
|
||||
task dependencies is the design structure matrix
|
||||
(DSM).
|
||||
- Working:
|
||||
collapsed:: true
|
||||
- A project task is assigned to a row and a corresponding column.
|
||||
- The rows and columns are named and ordered identically, although generally only the rows list the complete names of the tasks. Each task is defined by a row of the matrix.
|
||||
- We represent a task’s dependencies by placing marks in the columns to indicate the other tasks (columns) on which it depends.
|
||||
- ![image.png](../assets/image_1686471695984_0.png)
|
||||
- Reading across a row reveals all of the tasks whose output is required to perform the task corresponding to the row.
|
||||
- Reading down a column reveals which tasks receive information from the task corresponding to the column.
|
||||
- The diagonal cells are usually filled in with dots or the task labels, simply to separate the upper and lower triangles of the matrix and to facilitate tracing dependencies.
|
||||
- Gantt Chart
|
||||
collapsed:: true
|
||||
- Features:
|
||||
collapsed:: true
|
||||
- Gantt charts show how the work is broken down into a set of activities
|
||||
- They show the scheduling of these activities as a series of horizontal bands against a series of vertical lines representing dates
|
||||
- ![image.png](../assets/image_1686471844454_0.png)
|
||||
- They can be used to show dependencies between activities
|
||||
- They can be used to measure progress on a project or compare planned production with actual production
|
||||
- PERT Charts
|
||||
collapsed:: true
|
||||
- PERT (program evaluation and review technique) charts explicitly represent both dependencies and timing, in effect combining some of the information contained in the DSM and Gantt chart.
|
||||
- ![image.png](../assets/image_1686471880938_0.png)
|
||||
- The Critical Path
|
||||
collapsed:: true
|
||||
- The _dependencies_ among the tasks in a PERT chart, some of which may be arranged sequentially and some of which may be arranged in parallel, lead to the concept of a critical path.
|
||||
- The _critical path_ is the longest chain of dependent events. This is the single sequence of tasks whose combined required times define the minimum possible completion time for the entire set of tasks.
|
||||
- Undertake a baseline project plan
|
||||
collapsed:: true
|
||||
- **Definition**: project plan is the roadmap for the remaining development effort. The plan is important in coordinating the remaining tasks and in estimating the required development resources and development time.
|
||||
- Do project scheduling
|
||||
collapsed:: true
|
||||
- Methods:
|
||||
collapsed:: true
|
||||
- Contract Book
|
||||
- Project Task List
|
||||
- Team staffing & Organisation
|
||||
- Project Schedule
|
||||
- Project Budget
|
||||
- Project Risk Plan
|
||||
- Modifying the baseline plan
|
||||
- Accelerate projects
|
||||
collapsed:: true
|
||||
- Product development time is often the dominant concern in project planning and execution. There are a set of guidelines for accelerating product development projects.
|
||||
- **Execute** projects
|
||||
collapsed:: true
|
||||
- Smooth execution of even a well-planned project requires careful attention. Three problems of project execution are particularly important: 1. What mechanisms can be used to coordinate tasks? 2. How can project status be assessed? and 3. What actions can the team take to correct for undesirable deviations from the project plan?
|
||||
- ## 主题 2
|
||||
collapsed:: true
|
||||
- **定义** 什么是项目管理
|
||||
collapsed:: true
|
||||
- 对于除了最简单的产品以外,产品开发涉及到许多人完成许多不同的任务。
|
||||
- 项目管理是规划和协调资源和任务以实现这些目标的活动。
|
||||
- **PM** 的两个阶段
|
||||
collapsed:: true
|
||||
- 项目规划涉及安排项目任务并确定资源需求。项目计划首先在概念开发阶段制定,尽管它是一个动态实体,并在整个开发过程中不断演变。
|
||||
- 项目执行,有时称为项目控制,涉及协调和促进完成项目所需的各种任务,面对必然发生的意外事件和新信息的到来。执行与规划同样重要;许多团队失败是因为在整个项目的持续时间内没有保持对目标的专注。
|
||||
- **项目规划**:理解和代表项目中的不同任务
|
||||
collapsed:: true
|
||||
- 顺序、并行和耦合任务
|
||||
collapsed:: true
|
||||
- ![image.png](../assets/image_1686471430664_0.png)
|
||||
- 设计结构矩阵
|
||||
collapsed:: true
|
||||
- **定义**:用于表示和分析任务依赖关系的有用工具是设计结构矩阵(DSM)。
|
||||
- 工作原理:
|
||||
collapsed:: true
|
||||
- 一个项目任务分配给一行和相应的列。
|
||||
- 行和列的命名和顺序相同,尽管通常只有行列出任务的完整名称。每个任务由矩阵的一行定义。
|
||||
- 我们通过在列中放置标记来表示任务的依赖关系,以指示其所依赖的其他任务(列)。
|
||||
- ![image.png](../assets/image_1686471695984_0.png)
|
||||
- 横向读取一行可以看到所有需要完成与该行对应任务相关的任务的输出。
|
||||
- 纵向读取一列可以看到哪些任务接收来自与该列对应的任务的信息。
|
||||
- 对角线的单元格通常填充有点或任务标签,仅用于分隔矩阵的上三角形和下三角形,并便于追踪依赖关系。
|
||||
- 甘特图
|
||||
collapsed:: true
|
||||
- 特点:
|
||||
collapsed:: true
|
||||
- 甘特图展示了工作如何被分解为一系列活动。
|
||||
- 它们以一系列垂直线表示日期,以一系列水平带表示这些活动的调度。
|
||||
- ![image.png](../assets/image_1686471844454_0.png)
|
||||
- 它们可以用于显示活动之间的依赖关系。
|
||||
- 它们可以用于衡量项目的进展或比较计划生产与实际生产情况。
|
||||
- PERT 图
|
||||
collapsed:: true
|
||||
- PERT(程序评估和审查技术)图明确表示依赖关系和时间,实际上结合了 DSM 和甘特图中包含的一些信息。
|
||||
- ![image.png](../assets/image_1686471880938_0.png)
|
||||
- 关键路径
|
||||
collapsed:: true
|
||||
- PERT 图中任务之间的依赖关系,其中一些可能按顺序安排,一些可能并行安排,导致关键路径的概念。
|
||||
- 关键路径是最长的一系列依赖事件。这是一系列任务的单一序列,其组合所需的时间定义了整个任务集合的最短可能完成时间。
|
||||
- 进行基准项目计划
|
||||
collapsed:: true
|
||||
- **定义**:项目计划是剩余开发工作的路线图。该计划在协调剩余任务和估计所需的开发资源和开发时间方面非常重要。
|
||||
- 进行项目调度
|
||||
collapsed:: true
|
||||
- 方法:
|
||||
collapsed:: true
|
||||
- 合同书
|
||||
- 项目任务列表
|
||||
- 团队配备和组织
|
||||
- 项目进度表
|
||||
- 项目预算
|
||||
- 项目风险计划
|
||||
- 修改基准计划
|
||||
- 加速项目
|
||||
collapsed:: true
|
||||
- 产品开发时间通常是项目规划和执行中最主要的关注点。有一套加速产品开发项目的指南。
|
||||
- **执行** 项目
|
||||
collapsed:: true
|
||||
- 即使是一个精心计划的项目,顺利执行也需要仔细注意。项目执行的三个重要问题是:
|
||||
1. 可以使用哪些机制来协调任务?
|
||||
2. 如何评估项目状态?
|
||||
3. 团队可以采取哪些行动来纠正与项目计划不符的不良偏差?
|
||||
- ## Topic 3: Opportunity Identification
|
||||
collapsed:: true
|
||||
- Opportunity, definition and types
|
||||
- Definition:
|
||||
- an idea for a new product
|
||||
- It is a product description in an embryonic form
|
||||
- a newly sensed need,
|
||||
- a newly discovered technology,
|
||||
- a rough match between a need and a possible solution
|
||||
- It can be thought of as a hypothesis about how value might be created
|
||||
- Type
|
||||
- Ansoff’s growth matrix
|
||||
![image.png](../assets/image_1686473366617_0.png)
|
||||
- Market penetration
|
||||
logseq.order-list-type:: number
|
||||
- **Opportunities** can exist within a business’s existing
|
||||
markets through increasing the volume of sales
|
||||
of existing products
|
||||
- market development
|
||||
logseq.order-list-type:: number
|
||||
- **Opportunities** are said to exist for a business’s
|
||||
products through making them available to new
|
||||
markets
|
||||
- e.g. using existing products in new
|
||||
geographical markets
|
||||
- e.g. selling your existing products to a new age
|
||||
group of customers
|
||||
- product development
|
||||
logseq.order-list-type:: number
|
||||
- **Opportunities**: offering new or improved products to
|
||||
logseq.order-list-type:: number
|
||||
existing markets
|
||||
- diversification
|
||||
logseq.order-list-type:: number
|
||||
- **Opportunities**: Moving into new markets, potentially with a base
|
||||
logseq.order-list-type:: number
|
||||
from your existing product knowledge or
|
||||
diversification through acquisition of other
|
||||
companies
|
||||
- Risk
|
||||
- The element of risk _increases the further the strategy moves away from known quantities_ the existing product and the existing market
|
||||
- **Product development** (requiring, in effect, a new product) and market extension (a new market) involve a greater risk than market penetration
|
||||
- **Diversification** (both new products and new markets) generally carries the greatest risk of all
|
||||
- Opportunity identification process
|
||||
- Establish **a charter**
|
||||
- A **charter** articulates **the goals of the organisation**
|
||||
(in relation to NPD) and establishes the **boundary
|
||||
conditions for an innovation effort.** Charters can be
|
||||
termed as mission statement for a new product.
|
||||
- Generate and sense **many opportunities**
|
||||
- Focus has to be both on **internal** and **external** sources of raw opportunities. Some of these are generated:
|
||||
- Internally
|
||||
- R&D department
|
||||
- Externally
|
||||
- customer
|
||||
- competitive product
|
||||
- sales forces
|
||||
- collab. with universities
|
||||
- investors
|
||||
- distribution partners
|
||||
- other partner companies
|
||||
- Sense opportunities: Where do they come from?
|
||||
- Passively
|
||||
- Proactively
|
||||
- Document **frustrations** and **complaints** that current **customers** experience with existing products
|
||||
- Interview lead users, with attention devoted to
|
||||
- **innovations** by these users and
|
||||
- **modifications** these users may have
|
||||
made to existing products
|
||||
- **trends**
|
||||
- Systematically gather suggestions from **current customers**
|
||||
- **Competitors**
|
||||
- **Transfer** emerging tech.
|
||||
- **R&D**: _Research_ and _Development_
|
||||
- **Definition**: to develop new knowledge and apply scientific or engineering knowledge to connect the knowledge in one field to that in others
|
||||
- Roles:
|
||||
- **Discovering and developing** new technologies Improving understanding of the technology in existing products
|
||||
- **Improving and strengthening** understanding of technologies used in manufacturing
|
||||
- **Understanding research results** from universities and other research institutions
|
||||
- Areas:
|
||||
- R&D for existing businesses
|
||||
- R&D for new businesses
|
||||
- R&D for exploratory research
|
||||
- **Screen** opportunities
|
||||
- Purpose:
|
||||
- to eliminate any opportunities that are **unlikely to result in the creation of value**,
|
||||
- to focus attention on the opportunities **worthy of further investigation**
|
||||
- **not to** pick the _single best opportunity_!
|
||||
- Approach:
|
||||
- Web-based **surveys**
|
||||
- Workshops with **multi-voting**: collaborative sessions or meetings where participants engage in a voting process to prioritize or make decisions on various options or ideas.
|
||||
- Develop **promising opportunities**
|
||||
- Details
|
||||
- customer interviews,
|
||||
- testing of existing products,
|
||||
- concept generation,
|
||||
- quick prototypes,
|
||||
- estimates of market sizes and growth rates.
|
||||
- Goal
|
||||
- resolve the greatest uncertainty surrounding each one at the lowest cost in time and money.
|
||||
- Select **exceptional opportunities**
|
||||
- Goal
|
||||
- select a few that warrant a significant investment in product development.
|
||||
- Approach:**Real-Win-Worth-it**
|
||||
- **Real**: Is the opportunity real?
|
||||
- **Win**: Can you win with this opportunity?
|
||||
- **Worth** It: Is it worth doing?
|
||||
- **Reflect** on the result and process.
|
||||
Ask the following questions:
|
||||
- **How many** of the opportunities identified came from internal sources versus external sources?
|
||||
- Did we consider **dozens or hundreds** of opportunities?
|
||||
- Was the innovation charter **too narrowly focused**?
|
||||
- Were our filtering criteria **biased**, or largely based on the best possible estimates of eventual product success?
|
||||
- Are the resulting opportunities **exciting** to the team?
|
||||
-
|
||||
- ## 主题 3:机会识别
|
||||
collapsed:: true
|
||||
- 机会的定义和类型
|
||||
- 定义:
|
||||
- 一种新产品的构想
|
||||
- 它是一个初步形式的产品描述
|
||||
- 新发现的需求
|
||||
- 新发现的技术
|
||||
- 需求和可能解决方案之间的初步匹配
|
||||
- 可以将其视为关于如何创造价值的假设
|
||||
- 类型
|
||||
- 安索夫增长矩阵
|
||||
![image.png](../assets/image_1686473366617_0.png)
|
||||
- 市场渗透
|
||||
- **机会**存在于企业现有市场中,通过增加现有产品的销售量来实现
|
||||
- 市场开发
|
||||
- 通过将产品面向新市场使得**机会**出现于企业的产品中
|
||||
- 例如,在新的地理市场中使用现有产品
|
||||
- 例如,将现有产品销售给新的客户群体
|
||||
- 产品开发
|
||||
- **机会**:向现有市场提供新产品或改进的产品
|
||||
- 多元化
|
||||
- **机会**:进入新市场,可能基于现有产品知识或通过收购其他公司进行多元化
|
||||
- 风险
|
||||
- 风险元素与策略偏离已知量(现有产品和现有市场)的程度成正比
|
||||
- 与市场渗透相比,**产品开发**(实际上需要新产品)和市场扩展(新市场)涉及更大的风险
|
||||
- **多元化**(新产品和新市场)通常带有最大的风险
|
||||
- 机会识别过程
|
||||
- 制定**章程**
|
||||
- **章程**表达了组织(与 NPD 有关)的目标,并为创新工作设定了边界条件。章程可以被视为新产品的使命陈述。
|
||||
- 生成和发现**众多机会**
|
||||
- 需要关注内部和外部的机会来源。其中一些是通过以下方式生成的:
|
||||
- 内部生成
|
||||
- 研发部门
|
||||
- 外部生成
|
||||
- 客户
|
||||
- 竞争产品
|
||||
- 销售团队
|
||||
- 与大学合作
|
||||
- 投资者
|
||||
- 分销合作伙伴
|
||||
- 其他合作伙伴公司
|
||||
- 感知机会:它们从何而来?
|
||||
- 被动感知
|
||||
- 主动感知
|
||||
- 记录现有产品的当前客户所经历的**挫折**和**投诉**
|
||||
- 与领先用户进行访谈,关注这些用户的**创新**以及他们对现有产品的**修改**
|
||||
- 趋势
|
||||
- 系统地收集来自**现有客户**的建议
|
||||
- **竞争对手**
|
||||
- **转移**新兴技术
|
||||
- **研究与开发(R&D)**
|
||||
- **定义**:开发新知识并应用科学或工程知识,将一领域的知识与其他领域相连接
|
||||
- 角色:
|
||||
- **发现和开发**新技术,提高对现有产品中技术的理解
|
||||
- 改进和加强对制造中使用技术的理解
|
||||
- 理解来自大学和其他研究机构的研究结果
|
||||
- 领域:
|
||||
- 现有业务的研发
|
||||
- 新业务的研发
|
||||
- 探索性研究的研发
|
||||
- **筛选**机会
|
||||
- 目的:
|
||||
- 淘汰不太可能创造价值的机会
|
||||
- 将注意力集中在值得进一步调查的机会上
|
||||
- 不是选择*最佳机会*!
|
||||
- 方法:
|
||||
- 基于网络的调查
|
||||
- 带有**多元投票**的工作坊:参与者进行投票以对各种选项或想法进行优先排序或决策的协作会议或会议。
|
||||
- 开发**有前途的机会**
|
||||
- 细节:
|
||||
- 客户访谈
|
||||
- 对现有产品进行测试
|
||||
- 概念生成
|
||||
- 快速原型
|
||||
- 估计市场规模和增长率
|
||||
- 目标:
|
||||
- 以最低的时间和金钱成本解决每个机会周围最大的不确定性
|
||||
- 选择**杰出的机会**
|
||||
- 目标:
|
||||
- 选择几个值得在产品开发中进行重大投资的机会
|
||||
- 方法:**真实-胜利-值得**
|
||||
- **真实**:机会是真实的吗?
|
||||
- **胜利**:能够赢得这个机会吗?
|
||||
- **值得**:值得去做吗?
|
||||
- **反思**结果和过程。
|
||||
提出以下问题:
|
||||
- 机会识别中有多少机会来自内部来源和外部来源?
|
||||
- 我们是否考虑了数十个还是数百个机会?
|
||||
- 创新章程是否过于狭隘?
|
||||
- 我们的筛选标准是否存在偏见,或者主要基于对最终产品成功的最佳估计?
|
||||
- 结果的机会是否激发团队的激情?
|
||||
- ## Topic 5: Identify Customer Needs (Preliminary of Concept Development)
|
||||
- **Market Research** for NPD (New Product Development)
|
||||
collapsed:: true
|
||||
- **Definition**: the function that links the consumer, customer
|
||||
and public to the marketer through information
|
||||
– information used
|
||||
- **Goal**:
|
||||
- to identify and define marketing opportunities and problems;
|
||||
- to generate, refine and evaluate marketing actions;
|
||||
- to monitor marketing performance;
|
||||
- to improve understanding of the marketing process
|
||||
- When to use it?
|
||||
![image.png](../assets/image_1686475631266_0.png)
|
||||
- **Gather** raw **data** from customers
|
||||
logseq.order-list-type:: number
|
||||
- **Interviews**: One or more development team members discuss with a single customer
|
||||
- **Focus groups**: A moderator facilitates a two-hour discussion with a group of 8 or 12 customers
|
||||
- **Observing** the product in use
|
||||
- **Surveys**: direct mail or web-based questionnaires;
|
||||
- **Interpret** the raw **data** in terms of customer needs
|
||||
logseq.order-list-type:: number
|
||||
- The data gathered in Step 1 then has to be used to
|
||||
express the customers’ needs in terms of what the
|
||||
product has to do, not in terms of how it might do
|
||||
- Use positive, not negative phrasing
|
||||
- Express the needs as attributes of the product
|
||||
- Organize **the needs** into a hierarchy of needs
|
||||
logseq.order-list-type:: number
|
||||
- Structure the needs into
|
||||
l Must-haves – “I wont buy without”
|
||||
l Delighters – “What an unexpected treat”
|
||||
l Linear Satisfiers – “The more the merrier”
|
||||
l Neutrals – “No big deal”
|
||||
This is the Kano classification
|
||||
Consumer needs can be very elusive
|
||||
Intuitions are often wrong
|
||||
- Establish the **relative importance** of the needs
|
||||
logseq.order-list-type:: number
|
||||
- Measuring preference is central to market research
|
||||
- **Reflect** on the results and the process
|
||||
logseq.order-list-type:: number
|
||||
- Questions to ask:
|
||||
- Have we interacted with all important customers in
|
||||
our target market?
|
||||
- Can we see the latent needs of customers beyond
|
||||
our current product range?
|
||||
- Can we further involve any of the customers in our
|
||||
product development?
|
||||
- Did we involve the right people in our organisation?
|
||||
- Can we improve our process?
|
|
@ -0,0 +1,5 @@
|
|||
- Daily reflection [[Daily reflections]]
|
||||
- What I've done
|
||||
- 上午看[[学交]],写[[数据库]]题
|
||||
- What I've thought #thoughts
|
||||
- Mood
|
|
@ -2,6 +2,8 @@
|
|||
id:: 64856c09-6826-4ed3-b21e-380d43ea95a6
|
||||
- What I've done
|
||||
- 上午看[[学交]],写[[数据库]]题
|
||||
- 下午看[[产品开发]]
|
||||
- 晚上看数电和毛概
|
||||
- What I've thought #thoughts
|
||||
- Mood
|
||||
-
|
||||
|
@ -402,6 +404,7 @@
|
|||
2. 如何评估项目状态?
|
||||
3. 团队可以采取哪些行动来纠正与项目计划不符的不良偏差?
|
||||
- ## Topic 3: Opportunity Identification
|
||||
id:: 648594af-3833-4991-a4c2-2e9c8430a122
|
||||
collapsed:: true
|
||||
- Opportunity, definition and types
|
||||
- Definition:
|
||||
|
@ -609,12 +612,15 @@
|
|||
- 我们的筛选标准是否存在偏见,或者主要基于对最终产品成功的最佳估计?
|
||||
- 结果的机会是否激发团队的激情?
|
||||
- ## Topic 5: Identify Customer Needs (Preliminary of Concept Development)
|
||||
id:: 64859157-dc41-453d-95ea-39e2280ea735
|
||||
collapsed:: true
|
||||
- **Market Research** for NPD (New Product Development)
|
||||
collapsed:: true
|
||||
- **Definition**: the function that links the consumer, customer
|
||||
and public to the marketer through information
|
||||
– information used
|
||||
- **Goal**:
|
||||
collapsed:: true
|
||||
- to identify and define marketing opportunities and problems;
|
||||
- to generate, refine and evaluate marketing actions;
|
||||
- to monitor marketing performance;
|
||||
|
@ -623,12 +629,14 @@
|
|||
![image.png](../assets/image_1686475631266_0.png)
|
||||
- **Gather** raw **data** from customers
|
||||
logseq.order-list-type:: number
|
||||
collapsed:: true
|
||||
- **Interviews**: One or more development team members discuss with a single customer
|
||||
- **Focus groups**: A moderator facilitates a two-hour discussion with a group of 8 or 12 customers
|
||||
- **Observing** the product in use
|
||||
- **Surveys**: direct mail or web-based questionnaires;
|
||||
- **Interpret** the raw **data** in terms of customer needs
|
||||
logseq.order-list-type:: number
|
||||
collapsed:: true
|
||||
- The data gathered in Step 1 then has to be used to
|
||||
express the customers’ needs in terms of what the
|
||||
product has to do, not in terms of how it might do
|
||||
|
@ -636,25 +644,73 @@
|
|||
- Express the needs as attributes of the product
|
||||
- Organize **the needs** into a hierarchy of needs
|
||||
logseq.order-list-type:: number
|
||||
- Structure the needs into
|
||||
l Must-haves – “I wont buy without”
|
||||
l Delighters – “What an unexpected treat”
|
||||
l Linear Satisfiers – “The more the merrier”
|
||||
l Neutrals – “No big deal”
|
||||
This is the Kano classification
|
||||
Consumer needs can be very elusive
|
||||
Intuitions are often wrong
|
||||
collapsed:: true
|
||||
- **Structure** the needs into
|
||||
collapsed:: true
|
||||
- **Must-haves** – *“I wont buy without”*
|
||||
- **Delighters** – *“What an unexpected treat”*
|
||||
- **Linear Satisfiers** – *“The more the merrier”*
|
||||
- **Neutrals** – *“No big deal”*
|
||||
- This is the *Kano* classification
|
||||
- Consumer needs can be very **elusive**
|
||||
- **Intuitions** are often wrong
|
||||
- Establish the **relative importance** of the needs
|
||||
logseq.order-list-type:: number
|
||||
- Measuring preference is central to market research
|
||||
collapsed:: true
|
||||
- Measuring **preference** is central to market research
|
||||
- **Reflect** on the results and the process
|
||||
logseq.order-list-type:: number
|
||||
collapsed:: true
|
||||
- Questions to ask:
|
||||
- Have we interacted with all important customers in
|
||||
collapsed:: true
|
||||
- Have we interacted with all **important customers** in
|
||||
our target market?
|
||||
l Can we see the latent needs of customers beyond
|
||||
- Can we see the **latent needs** of customers beyond
|
||||
our current product range?
|
||||
l Can we further involve any of the customers in our
|
||||
- Can we **further involve** any of the customers in our
|
||||
product development?
|
||||
l Did we involve the right people in our organisation?
|
||||
l Can we improve our process?
|
||||
- Did we involve the **right people** in our organisation?
|
||||
- Can we **improve** our process?
|
||||
- ## 第五主题:识别顾客需求(概念开发的初步阶段)
|
||||
collapsed:: true
|
||||
- **NPD(新产品开发)的市场调研**
|
||||
- **定义**:通过信息将消费者、顾客和公众与营销人员联系起来的功能
|
||||
- **目标**:
|
||||
- 识别和定义市场营销机会和问题;
|
||||
- 生成、改进和评估市场营销行动;
|
||||
- 监测市场营销绩效;
|
||||
- 提高对市场营销过程的理解
|
||||
- 何时使用?
|
||||
![image.png](../assets/image_1686475631266_0.png)
|
||||
- 从顾客那里收集原始数据
|
||||
logseq.order-list-type:: number
|
||||
- **面谈**:一个或多个开发团队成员与单个顾客讨论
|
||||
- **焦点小组**:一个主持人与8至12位顾客进行两小时的讨论
|
||||
- 观察产品的使用情况
|
||||
- **调查**:直邮或基于网络的问卷调查;
|
||||
- 将原始数据解读为顾客需求
|
||||
logseq.order-list-type:: number
|
||||
- 然后,必须使用在步骤1中收集到的数据来表达顾客的需求,而不是以产品如何满足需求的方式来表达
|
||||
- 使用积极的、而非消极的措辞
|
||||
- 将需求表达为产品的属性
|
||||
- 将需求组织成层次结构
|
||||
logseq.order-list-type:: number
|
||||
- 将需求分为以下部分:
|
||||
- **必备项** - “如果没有这个,我就不会购买”
|
||||
- **惊喜项** - “真是个意外的惊喜”
|
||||
- **线性满足项** - “越多越好”
|
||||
- **中立项** - “无关紧要”
|
||||
- 这是*Kano*分类
|
||||
- 消费者需求可能非常难以捉摸
|
||||
- 直觉经常是错误的
|
||||
- 确定需求的**相对重要性**
|
||||
logseq.order-list-type:: number
|
||||
- 测量**偏好**是市场调研的核心
|
||||
- **反思**结果和过程
|
||||
logseq.order-list-type:: number
|
||||
- 需要问的问题:
|
||||
- 我们是否与目标市场中的所有**重要顾客**进行了互动?
|
||||
- 我们能否看到顾客在我们当前产品范围之外的**潜在需求**?
|
||||
- 我们能否在产品开发中**进一步吸引**任何顾客的参与?
|
||||
- 我们是否在组织中吸引了**合适的人员**?
|
||||
- 我们能否改进我们的流程?
|
|
@ -0,0 +1,2 @@
|
|||
- [[Shopping lists]]
|
||||
- 卡其裤 chicos
|
|
@ -210,7 +210,7 @@
|
|||
[?block :block/scheduled ?d]
|
||||
[?block :block/deadline ?d])
|
||||
[(> ?d ?start)]
|
||||
[(<= ?d ?next)]]
|
||||
[(< ?d ?next)]]
|
||||
:inputs [:56d :today]
|
||||
:collapsed? false}
|
||||
]}
|
||||
|
@ -255,7 +255,7 @@
|
|||
:ref/linked-references-collapsed-threshold 50
|
||||
|
||||
;; Favorites to list on the left sidebar
|
||||
:favorites []
|
||||
:favorites ["Contents"]
|
||||
|
||||
;; any number between 0 and 1 (the greater it is the faster the changes of the next-interval of card reviews) (default 0.5)
|
||||
;; :srs/learning-fraction 0.5
|
|
@ -201,22 +201,18 @@
|
|||
[(< ?d ?next)]]
|
||||
:inputs [:today :7d-after]
|
||||
:collapsed? false}
|
||||
{ :query [:find (pull ?b [*])
|
||||
:in $ ?today ?tomorrow
|
||||
:where
|
||||
[?b :block/marker ?m]
|
||||
(not [(contains? #{"DONE", "CANCELED"} ?m)])
|
||||
[(get-else $ ?b :block/scheduled ?tomorrow) ?scheduled]
|
||||
[(get-else $ ?b :block/deadline ?tomorrow) ?deadline]
|
||||
(or
|
||||
[(contains? #{"NOW", "DOING"} ?m)]
|
||||
[(<= ?scheduled ?today)]
|
||||
[(<= ?deadline ?today)])]
|
||||
:inputs [:today 99990101]
|
||||
:result-transform (fn [result]
|
||||
(sort-by (fn [h]
|
||||
(get-in h [:block/scheduled])) result))
|
||||
:breadcrumb-show? false}
|
||||
{:title "⚠️ OVERDUE"
|
||||
:query [:find (pull ?block [*])
|
||||
:in $ ?start ?next
|
||||
:where
|
||||
(task ?block #{"NOW" "LATER" "TODO" "DOING"})
|
||||
(or
|
||||
[?block :block/scheduled ?d]
|
||||
[?block :block/deadline ?d])
|
||||
[(> ?d ?start)]
|
||||
[(< ?d ?next)]]
|
||||
:inputs [:56d :today]
|
||||
:collapsed? false}
|
||||
]}
|
||||
|
||||
;; Add your own commands to slash menu to speedup.
|
||||
|
@ -259,7 +255,7 @@
|
|||
:ref/linked-references-collapsed-threshold 50
|
||||
|
||||
;; Favorites to list on the left sidebar
|
||||
:favorites []
|
||||
:favorites ["Contents"]
|
||||
|
||||
;; any number between 0 and 1 (the greater it is the faster the changes of the next-interval of card reviews) (default 0.5)
|
||||
;; :srs/learning-fraction 0.5
|
||||
|
@ -358,7 +354,7 @@
|
|||
:file/name-format :triple-lowbar
|
||||
:graph/settings {:journal? true, :orphan-pages? false, :excluded-pages? false, :builtin-pages? true}
|
||||
:publishing/all-pages-public? false
|
||||
:feature/enable-flashcards? false
|
||||
:feature/enable-flashcards? true
|
||||
:feature/enable-whiteboards? true
|
||||
|
||||
;; specify the format of the filename for journal files
|
|
@ -0,0 +1,31 @@
|
|||
- # Stuff in this note
|
||||
- ### Personal
|
||||
- ### Task management [[tasks]]
|
||||
- [[Personal Tasks]]
|
||||
- [[Shopping lists]]
|
||||
- [[Learning Logseq]]
|
||||
- [[学习任务]]
|
||||
- [[总复习]]
|
||||
- [[School notes]]
|
||||
- 2023
|
||||
- [[概率论]]
|
||||
- [[产品开发]]
|
||||
- [[Java]]
|
||||
- [[数据库]]
|
||||
- ### Reflections
|
||||
- [[Daily reflections]]
|
||||
- #thoughts
|
||||
- ### Reviews
|
||||
- #music
|
||||
- #books
|
||||
- #movies
|
||||
- #food
|
||||
- ### Cloud collections [[Cloud collections]]
|
||||
- ### Personal growth
|
||||
- [[Habits]]
|
||||
- [[GPT notes]]
|
||||
- #健身
|
||||
- ### Coding
|
||||
- ### OJ notes #coding_problems
|
||||
- Leetcode notes #leetcode
|
||||
- ### Projects [[projects]]
|
|
@ -0,0 +1,62 @@
|
|||
file:: [section_2.2_1686907456219_0.pdf](../assets/section_2.2_1686907456219_0.pdf)
|
||||
file-path:: ../assets/section_2.2_1686907456219_0.pdf
|
||||
|
||||
- The Definition of Distribution Function
|
||||
ls-type:: annotation
|
||||
hl-page:: 3
|
||||
hl-color:: blue
|
||||
id:: 648c2a50-7acf-4cd5-b075-d0e970e114a4
|
||||
- The Properties of Distribution Function
|
||||
ls-type:: annotation
|
||||
hl-page:: 4
|
||||
hl-color:: blue
|
||||
id:: 648c2a73-3961-4723-90e8-5f160bb18e0d
|
||||
- [:span]
|
||||
ls-type:: annotation
|
||||
hl-page:: 4
|
||||
hl-color:: yellow
|
||||
id:: 648c2a88-3d0f-47d2-be44-21df002a1def
|
||||
hl-type:: area
|
||||
hl-stamp:: 1686907527770
|
||||
- [:span]
|
||||
ls-type:: annotation
|
||||
hl-page:: 7
|
||||
hl-color:: yellow
|
||||
id:: 648c2abf-5c5e-4af9-9e13-bb566f3206e8
|
||||
hl-type:: area
|
||||
hl-stamp:: 1686907580838
|
||||
- [:span]
|
||||
ls-type:: annotation
|
||||
hl-page:: 9
|
||||
hl-color:: yellow
|
||||
id:: 648c2b26-e92d-43f7-b8e1-60b51a2b5268
|
||||
hl-type:: area
|
||||
hl-stamp:: 1686907685844
|
||||
- A random variable is said to be of discrete type if the number of different values it can take is finite or countably infinite.
|
||||
ls-type:: annotation
|
||||
hl-page:: 17
|
||||
hl-color:: yellow
|
||||
id:: 648c2be0-787e-4e1f-8d0c-b859f0d08383
|
||||
hl-stamp:: 1686907879808
|
||||
- We call X a continuous random variable if there is a function f defined for all x ∈ R and having the following properties:
|
||||
ls-type:: annotation
|
||||
hl-page:: 25
|
||||
hl-color:: yellow
|
||||
id:: 648c2c54-b536-40ba-8191-ef1aeb2be0b9
|
||||
- The Distribution Function of Function of a Random Variable
|
||||
ls-type:: annotation
|
||||
hl-page:: 35
|
||||
hl-color:: blue
|
||||
id:: 648c2c9a-fcca-43e3-94a6-466f52131b48
|
||||
- we can assert that if X is a random variable, then Y := g(X) = g(X(ω)), where g is a real-valued function defined on the real line, is a random variable as well
|
||||
ls-type:: annotation
|
||||
hl-page:: 35
|
||||
hl-color:: yellow
|
||||
id:: 648c2d05-82d4-472f-901c-b362852e2a3a
|
||||
- [:span]
|
||||
ls-type:: annotation
|
||||
hl-page:: 40
|
||||
hl-color:: yellow
|
||||
id:: 648c2de1-d9a7-4760-bb4f-beec4b41102c
|
||||
hl-type:: area
|
||||
hl-stamp:: 1686908384666
|
File diff suppressed because it is too large
Load diff
File diff suppressed because it is too large
Load diff
2608
logseq/bak/pages/总复习2023t1/2023-06-16T10_40_41.427Z.android.md
Normal file
2608
logseq/bak/pages/总复习2023t1/2023-06-16T10_40_41.427Z.android.md
Normal file
File diff suppressed because it is too large
Load diff
2730
logseq/bak/pages/总复习2023t1/2023-06-16T12_34_22.179Z.android.md
Normal file
2730
logseq/bak/pages/总复习2023t1/2023-06-16T12_34_22.179Z.android.md
Normal file
File diff suppressed because it is too large
Load diff
792
pages/总复习2023t1.sync-conflict-20230613-135128-FGMY57F.md
Normal file
792
pages/总复习2023t1.sync-conflict-20230613-135128-FGMY57F.md
Normal file
|
@ -0,0 +1,792 @@
|
|||
- [[总复习2023t1]] {{renderer :todomaster}}
|
||||
title:: 总复习2023t1
|
||||
- DONE [[Java]] {{renderer :todomaster}}
|
||||
collapsed:: true
|
||||
SCHEDULED: <2023-06-12 Mon>
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-09 Fri 15:09:23]--[2023-06-09 Fri 16:26:51] => 01:17:28
|
||||
:END:
|
||||
- DONE lab
|
||||
- DONE 写 lab8
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-09 Fri 15:06:46]--[2023-06-09 Fri 16:26:50] => 01:20:04
|
||||
:END:
|
||||
- DONE (考前)复习 labs
|
||||
collapsed:: true
|
||||
- DONE [#A] 从 t14 复制过来
|
||||
- 1
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- 2
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- 3
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- 4
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- 5
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- 6
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- 7
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-10 Sat 21:08:02]--[2023-06-10 Sat 21:08:03] => 00:00:01
|
||||
:END:
|
||||
- DONE 课件
|
||||
collapsed:: true
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-12 Mon 10:47:42]--[2023-06-12 Mon 14:12:02] => 03:24:20
|
||||
:END:
|
||||
- DONE 看 revision (java file IO 可以考前再看一遍)
|
||||
collapsed:: true
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-12 Mon 11:40:14]--[2023-06-12 Mon 12:58:33] => 01:18:19
|
||||
:END:
|
||||
- DONE [#A] Review past exam papers
|
||||
- DONE java file IO
|
||||
collapsed:: true
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-09 Fri 16:44:33]--[2023-06-09 Fri 17:13:37] => 00:29:04
|
||||
:END:
|
||||
- DONE Buffered Reader / Writer
|
||||
- DONE File objects
|
||||
- DONE GUI (自学不考)
|
||||
collapsed:: true
|
||||
- DONE Graphics Classes: Color, Font, FontMetrics, JLabel
|
||||
- StringBuffer vs. StringBuilder
|
||||
- String is immutable whereas StringBuffer and StringBuilder are mutable classes.
|
||||
- StringBuffer is thread-safe and synchronized whereas StringBuilder is not. That’s why StringBuilder is faster than StringBuffer.
|
||||
- String concatenation operator (+) internally uses StringBuffer or StringBuilder class.
|
||||
- For String manipulations in a non-multi threaded environment, we should use StringBuilder else use StringBuffer class.
|
||||
- DONE 题
|
||||
- DONE 看 qm 上错题 [gradeplus](https://qmplus.qmul.ac.uk/grade/report/user/index.php?id=21582)
|
||||
- DONE this 的用法
|
||||
collapsed:: true
|
||||
- In Java, the `this` keyword is a reference to the current object within a non-static method or constructor. It represents the instance of the class on which the method or constructor is being called.
|
||||
- When a class is instantiated to create an object, that object has its own set of instance variables and methods. The `this` keyword allows you to refer to those instance variables and methods from within the class itself. It is primarily used to differentiate between instance variables and parameters or local variables that have the same name.
|
||||
- Here are a few common uses of the `this` keyword in Java:
|
||||
collapsed:: true
|
||||
- Accessing instance variables: You can use `this` to access or modify the instance variables of the current object. For example, `this.variableName` refers to the instance variable `variableName` of the current object.
|
||||
- Invoking constructors: In a constructor, `this` can be used to invoke another constructor in the same class. It is useful for constructor chaining, where one constructor calls another constructor to initialize the object.
|
||||
- Passing the current object as a parameter: Sometimes, you may need to pass the current object as an argument to another method. In such cases, you can use `this` to pass a reference to the current object.
|
||||
- Returning the current object: A method can use `this` to return the current object. This is often used in method chaining, where multiple method calls are chained together on the same object.
|
||||
- It's important to note that `this` can only be used within non-static contexts, as it refers to the current instance of the class. Static methods and variables do not belong to any specific instance, so `this` cannot be used inside them.
|
||||
- Overall, the `this` keyword provides a way to refer to the current object and access its members, helping to avoid naming conflicts and make the code more readable.
|
||||
- DONE Past exam papers
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-11 Sun 21:37:16]--[2023-06-12 Mon 12:58:29] => 15:21:13
|
||||
CLOCK: [2023-06-12 Mon 14:12:05]--[2023-06-12 Mon 17:55:24] => 03:43:19
|
||||
:END:
|
||||
- DONE Access Modifiers
|
||||
- DONE Javadoc tags and modifiers [tutorial](https://www.tutorialspoint.com/java/java_documentation.htm)
|
||||
- Syntax:
|
||||
- ```java
|
||||
// This is a single line comment
|
||||
|
||||
/*
|
||||
* This is a regular multi-line comment
|
||||
*/
|
||||
|
||||
/**
|
||||
* This is a Javadoc
|
||||
*/
|
||||
```
|
||||
- @throws ExceptionType reason
|
||||
- DONE Garbage collection
|
||||
collapsed:: true
|
||||
- **The working:** Java garbage collection is an automatic process. Automatic garbage
|
||||
collection is the process of looking at heap memory, identifying which
|
||||
objects are in use and which are not, and deleting the unused objects.
|
||||
An in-use object, or a referenced object, means that some part of your
|
||||
program still maintains a pointer to that object. An unused or
|
||||
unreferenced object is no longer referenced by any part of your program.
|
||||
So the memory used by an unreferenced object can be reclaimed. The
|
||||
programmer does not need to mark objects to be deleted explicitly. The
|
||||
garbage collection implementation lives in the JVM.
|
||||
- **Eligibility for garbage collection:** An object is said to be eligible for GC(garbage collection) if it is unreachable.
|
||||
- DONE ==THREE main concepts when doing GUI programming in Java==
|
||||
- **Component**: An object that the user can see on the screen and can also
|
||||
interact with
|
||||
- **Container**: A component that can hold other components
|
||||
- **Event**: An action triggered by the user
|
||||
- Designing a GUI involves creating components, putting them into containers, and
|
||||
arranging for the program to respond to events (e.g. responding to mouse clicks).
|
||||
- DONE ==Review Java File IO==
|
||||
- DONE Exception Terms
|
||||
- java.lang.ArrayIndexOutOfBoundsException:
|
||||
- IOException
|
||||
- ArithmeticException
|
||||
- NegativeArraySizeException
|
||||
- ArrayStoreException
|
||||
- LATER four fundamental OOP concepts.
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-12 Mon 14:12:16]--[2023-06-12 Mon 14:12:18] => 00:00:02
|
||||
:END:
|
||||
- inheritance
|
||||
- Inheritance in Java is **a concept that acquires the properties from one class to other classes**
|
||||
- polymorphism
|
||||
-
|
||||
- encapsulation
|
||||
- Encapsulation in Java is a mechanism of **wrapping the data** (variables) and code acting on the data (methods) together as a single unit. In encapsulation, the variables of a class will be hidden from other classes, and can be accessed only through the methods of their current class. Therefore, it is also known as **data hiding**.
|
||||
- abstraction.
|
||||
- Data **abstraction** is the process **of hiding certain details** and showing only essential information to the user.
|
||||
- Abstraction can be achieved with either **abstract classes** or
|
||||
[**interfaces**](https://www.w3schools.com/java/java_interface.asp) (which you will learn more about in the next chapter).
|
||||
- Overloading vs. overriding
|
||||
- When two or more methods in the same class have the same method name but different parameters, this is called overloading. In contrast, overriding occurs when two methods have the same name and parameters
|
||||
- Interface
|
||||
- DONE 毛概 {{renderer :todomaster}}
|
||||
collapsed:: true
|
||||
SCHEDULED: <2023-06-13 Tue>
|
||||
- DONE 看笔记
|
||||
- DONE 做题
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-11 Sun 09:51:00]--[2023-06-11 Sun 09:51:01] => 00:00:01
|
||||
:END:
|
||||
- DONE 整理错题
|
||||
deck:: 2023t1/Mao
|
||||
- 在1978年的关于真理标准问题的⼤讨论中,邓⼩平指出,关于真理标准问题的讨论实质就在于( {{c1 b}} ). #flashcard
|
||||
id:: 6486eb88-490a-45f2-b393-89192dd5ea52
|
||||
A.是否坚持⻢列主义、⽑泽东思想
|
||||
B.是否坚持实践是==检验真理==的唯⼀标准
|
||||
C.是否坚持解放思想、实事求是
|
||||
D.是否坚持中国共产党的领导
|
||||
- 创新包括各⽅⾯的创新,如理论创新、技术创新、制度创新等,其中在各项创新中处于先导地位的是 ( {{c1 b}})#flashcard
|
||||
extra:: 社会主义主打一个空想
|
||||
id:: 6486eba2-9d71-4e27-a8f8-96947c0beda6
|
||||
A.科技创新
|
||||
B.理论创新
|
||||
C.⽂化创新
|
||||
D.⽣产关系创新
|
||||
- id:: 6486ebb8-4319-4e33-a901-221546ac6b28
|
||||
4. 党的思想路线的实质和核⼼是( {{c1 c}} )#flashcard
|
||||
A.⽣产关系适合⽣产⼒ B.理论联系实际
|
||||
C.实事求是 D.在实践中检验真理和发展真理
|
||||
- extra:: 三个有利于:改革得失
|
||||
id:: 6486ebbd-9c15-48d3-a273-aad64d4fadb2
|
||||
5. 实事求是思想路线的根本体现是 ( {{c1 a}} )#flashcard
|
||||
A.尊重群众、尊重实践
|
||||
B.⼀切从群众中来
|
||||
C.解放思想
|
||||
D.“三个有利于”
|
||||
- 4.中国共产党在新⺠主主义⾰命领导权问题上有着深刻认识,党认为实现对⾰命的领导权的根本
|
||||
id:: 6486ebe6-ea17-4b3d-a855-1a992863e0e2
|
||||
保证是( {{c1 c}} )。 #flashcard
|
||||
A.动员全⺠开展武装⽃争 B.建⽴最⼴泛的⼈⺠统⼀战线
|
||||
C.加强中国共产党的建设 D.扩⼤⾰命的影响⼒和控制⼒
|
||||
- extra:: a: 抢国民党
|
||||
id:: 6486ebf2-991b-43fa-9baf-c2e94eec3230
|
||||
1. 建国初期我国社会主义国营经济建⽴的主要途径是( {{c1 a}} )#flashcard
|
||||
A. 没收官僚资本 B. 没收帝国主义在华企业
|
||||
C. 剥夺封建地主阶级的财产 D. 赎买⺠族资产阶级的财产
|
||||
- extra:: 学苏联
|
||||
id:: 6486ebf5-ecb6-49f4-a22e-156de99c617c
|
||||
2. 20世纪50年代,⽑泽东提出,中国⼯业化道路的问题主要是指 ( {{c1 c}} ) #flashcard
|
||||
A.优先发展重⼯业的问题
|
||||
B.将落后的农业国建设成为先进的⼯业国的问题
|
||||
C.重⼯业、轻⼯业和农业的发展关系问题
|
||||
D.建⽴独⽴的⽐较完整的⼯业体系问题
|
||||
- extra:: b反右运动 c文革 d从来没有
|
||||
id:: 6486ec08-5315-4ddc-ad39-f87b1acf36ec
|
||||
3. 社会主义改造基本完成后,我国国家政治⽣活的主题是 ( {{c1 b}} ) #flashcard
|
||||
A.集中⼒量发展社会⽣产⼒
|
||||
B.正确处理⼈⺠内部⽭盾
|
||||
C.进⾏思想战线上的社会主义⾰命
|
||||
D.加强社会主义⺠主与法制建设
|
||||
- extra:: 创新性方法:学苏联自由派
|
||||
id:: 6486ec0b-b934-4f4a-b0ff-31c39c44e74d
|
||||
4. 我国在资本主义⼯商业进⾏社会主义改造实践中⼀个创新性办法是对⺠族资产阶级( {{c1 a}} ) #flashcard
|
||||
A.和平赎买
|
||||
B.剥夺⽣产资料 C.公私合营
|
||||
D.⽣活上给出路
|
||||
- extra:: 十大关系指出要多快好省建设社会主义基本思想
|
||||
id:: 6486ec0e-3678-4e3c-95cc-a1eae493c278
|
||||
5. ⽑泽东在《论⼗⼤关系》中提出我国社会主义建设必须围绕的⼀个基本⽅针是 ( {{c1 c}} ) #flashcard
|
||||
A.发展⽣产⼒,把我国尽快地从落后的农业国变为先进的⼯业国
|
||||
B.正确处理⽆产阶级同资产阶级的⽭盾
|
||||
C.调动⼀切积极因素,为社会主义事业服务
|
||||
D.彻底消灭剥削制度,继续肃清反⾰命残余势⼒
|
||||
- 1.社会主义的**根本**原则是( {{c1 a}} ) #flashcard
|
||||
extra:: 根本原则
|
||||
id:: 6486f101-7de3-4d01-81fa-f33ca1ce5395
|
||||
A. 坚持以公有制为主体,实现共同富裕 B.扩⼤改⾰开放,增强综合国⼒
|
||||
C.实⾏按劳分配,改善⼈⺠⽣活 D. 不断发展⽣产,增加社会财富
|
||||
- id:: 6486f11d-fd1f-4050-b693-1d9e61525db2
|
||||
3. 新时期的解放思想,关键就是对建设中国特⾊社会主义的⾸要的基本理论问题的重新认识,这就
|
||||
是( {{c1 d}} ) #flashcard
|
||||
A.什么是实事求是
|
||||
B. 怎样建设党
|
||||
C.什么是⻢克思主义
|
||||
D. 什么是社会主义
|
||||
- 5.坚持四项基本原则的核⼼是 ( {{c1 c}} ) #flashcard
|
||||
id:: 6486f139-1b96-4fa2-801d-e6af909be90c
|
||||
extra:: 共产党要独裁,别人都不行
|
||||
A.坚持社会主义道路 B.坚持⼈⺠⺠主专政
|
||||
C.坚持共产党的领导 D.坚持⻢列主义、⽑泽东思想
|
||||
- 3.社会主义初级阶段与新⺠主主义社会在经济基础⽅⾯的本质区别在于( {{c1 a}} )#flashcard
|
||||
extra:: d: 不谈这些
|
||||
id:: 6486f1db-f09d-45d5-982e-8a6d36c88ec0
|
||||
A. 是否存在多种所有制经济
|
||||
B. ⾮公有制经济是否成为社会主义经济的必要补充
|
||||
C. 国有经济是否起主导作⽤
|
||||
D. 公有制经济是否成为社会经济的主体
|
||||
- 2.正确处理改⾰、发展、稳定三者关系的重要结合点是( {{c1 b}} )#flashcard
|
||||
id:: 6486f20e-62ee-4487-855d-9fbfe95e4d8f
|
||||
A.把改⾰的⼒度、发展的速度和社会可以承受的程度统⼀结合起来
|
||||
B.不断改善⼈⺠⽣活
|
||||
C.在社会政治稳定中推进改⾰和发展
|
||||
D.靠深化和继续发展解决改⾰和发展中产⽣的新问题和新⽭盾
|
||||
- 5.经过30多年的对外开放,我国形成了全⽅位、多层次、宽领域的对外开放格局。所谓全⽅位就是
|
||||
指( {c1 a})#flashcard
|
||||
extra:: 全方位:a; 多层次:合作框架, 宽领域:跨越政治
|
||||
id:: 6486f242-b267-4c28-825a-62182abcfbfe
|
||||
A.不论对资本主义国家还是社会主义国家,对发达国家还是发展中国家都实⾏开放政策
|
||||
B. 根据各地区的实际和特点,通过经济特区、沿海开放城市、经济技术开发区等不同开放程度的
|
||||
各种形式,形成全国范围的对外开放
|
||||
C.⽴⾜我国国情,对国际商品市场、国际资本市场、国际技术市场和国际劳务市场的开放
|
||||
D. 坚持“引进来”和“⾛出去”相结合
|
||||
- 1.我国现阶段公有制的主要实现形式是( {{c1 a}} )#flashcard
|
||||
id:: 6486f2b8-2ef5-461f-a6da-6dcae1737aa8
|
||||
extra:: b: 农村银行
|
||||
A. 股份制
|
||||
B.股份合作制 C.租赁、承包制
|
||||
D.国家独资经济
|
||||
- id:: 6486fb7d-2914-45c7-99a3-81afc94e8c1a
|
||||
3. 国有经济在国⺠经济中的主导作⽤主要表现在 ( {{c1 c}} ) #flashcard
|
||||
A.国有资产在社会总资产中占有量的优势
|
||||
B.国有经济能控制垄断性⾏业
|
||||
C.国有经济对国⺠经济的==控制⼒==
|
||||
D.国有经济在国⺠经济中占主体地位
|
||||
- extra:: 领导利益优先
|
||||
id:: 6486fb9c-3ec3-4817-a455-38bfcc043e24
|
||||
4. 在收⼊分配过程中,⽆论是⿎励⼀部分地区、⼀部分⼈先富起来,还是注重社会公平,其实质都
|
||||
是( {{c1 b}} ) #flashcard
|
||||
extra:: 领导利益优先
|
||||
id:: 6486fb9c-3ec3-4817-a455-38bfcc043e24
|
||||
A.维护最⼴⼤⼈⺠的根本利益B.如何妥善协调各⽅⾯的利益关系问题
|
||||
C.兼顾不同⽅⾯群众的利益D.效率优先、兼顾公平
|
||||
- 1.新⺠主主义⾰命初期,⽑泽东⽐较了中外资产阶级⾰命的性质后,提出中国⾰命胜利后,应该建⽴的国家政权形式是 ( {{c1 b}} ). #flashcard
|
||||
extra:: 共产党约等于革命民众
|
||||
id:: 6486fbcf-fce9-47eb-9471-93bb3fdbca43
|
||||
A. ⼈⺠⺠主专政的国家
|
||||
B. 各⾰命⺠众合作统治的国家
|
||||
C. ⺠主联合政府的国家
|
||||
D. 以⼯农为主的⼯农⺠主政权
|
||||
- 2.中国共产党和各⺠主党派合作的政治基础是 ( {{c1 c}} ). #flashcard
|
||||
extra:: 四项基本原则不允许争议,指“社会主义”,“民主”,“共产党独裁”,“马列毛思想”不允许反对
|
||||
id:: 6486fc44-9b33-4eb1-bbc0-fc00aa42ed6c
|
||||
A. 中国共产党和各⺠主党派全作的政治基础是
|
||||
B. 遵循“⻓期共存,互相监督,肝胆相照,荣辱与共”的⽅针
|
||||
C. 坚持四项基本原则
|
||||
D. 中国共产党是执政党,⺠主党派是参政党
|
||||
- 5.社会主义⺠主政治的**本质**是 ( {{c1 a}} ). #flashcard
|
||||
id:: 6486fcfb-2262-48e4-96dc-24b0ca4087e3
|
||||
extra:: 红二代当家作主最重要
|
||||
A. ⼈⺠当家作主
|
||||
B. ⼈⺠⺠主专政
|
||||
C. ⼈⺠代表⼤会制度
|
||||
D. ⼈⺠参与国家管理
|
||||
- extra:: 共产党最爱吹的金句
|
||||
id:: 6486fe1f-1d2e-46de-8616-a9bb174c3ade
|
||||
4. 社会主义道德建设的核⼼是( {{c1 d}} ). #flashcard
|
||||
A. 爱国主义
|
||||
B. 集体主义
|
||||
C. 社会主义
|
||||
D. 为⼈⺠服务
|
||||
- id:: 6486fe3b-fd24-4e3f-980d-d02c66e3fe18
|
||||
5. 社会主义道德建设的核⼼是( {{c1 a}} ). #flashcard
|
||||
A. 为⼈⺠服务
|
||||
B. 集体主义
|
||||
C 诚实可信
|
||||
D 爱国主义
|
||||
- id:: 64870181-4942-41c3-9f04-54ccd35a73ad
|
||||
1. 社会主义和谐社会的核⼼价值是( {{c1 d}} ). #flashcard
|
||||
A. 以⼈为本
|
||||
B. 以⺠为本
|
||||
C 社会公平
|
||||
D 公平和正义
|
||||
- 2 我国社会保障制度的基本⽬标是( {{c1 a}} ). #flashcard
|
||||
extra:: 竟然是和其他所有国家一样
|
||||
id:: 648701b2-ad29-4bd5-9160-bcf973aaeb51
|
||||
A. 保证⼈们最基本的⽣活需要
|
||||
B. 使劳动者⽣活⽔平不断提⾼
|
||||
C. 保证劳动者充分就业
|
||||
D. 实现共同富裕
|
||||
- extra::
|
||||
id:: 648702a3-ce36-474c-8427-ba505b748de2
|
||||
5. “⼗⼀五”规划根本⽬的是以⼈为本,执政为⺠,其含义( {{c1 c}} ). #flashcard
|
||||
A. 不断推进⼈的全⾯发展
|
||||
B. 不断推进共同富裕
|
||||
C. 不断满⾜⼈⺠的物质⽂化⽣活需要
|
||||
D. 不断创造共同富裕的物质基础
|
||||
- extra:: 因为是假想敌,所以想要统一
|
||||
id:: 648702cb-b4d4-470c-b1c3-187aa64ba582
|
||||
2. 台湾问题的核⼼是( {{c1 a}} ). #flashcard
|
||||
A. 祖国统⼀
|
||||
B. ⼀国两制
|
||||
C. ⼀国两政府
|
||||
D. “三通”
|
||||
- id:: 6487034e-025b-4a2e-9bee-ba856180c7cd
|
||||
1. 和平与发展是时代的主题,和平与发展的核⼼问题是( {{c1 a}} ). #flashcard
|
||||
A. 南北问题
|
||||
B. .维护世界和平问题
|
||||
C. 反对霸权主义、强权政治问题
|
||||
D. 建⽴国际经济政治新秩序问题
|
||||
- id:: 648704bb-1b44-4b7a-9b56-4f8ee1e102f0
|
||||
4. 中国外交政策的基本**⽬标**是( {{c1 b}} ). #flashcard
|
||||
A. 提⾼中国的国际地位
|
||||
B. 维护世界和平,促进⼈类共同繁荣和发展
|
||||
C. 反对霸权主义和强权政治
|
||||
D. 实现全⼈类的解放
|
||||
- extra:: 是全球的南北
|
||||
id:: 648704ff-5743-4233-9a16-3c196737e5aa
|
||||
1. 和平与发展是时代的主题,**和平与发展**的核⼼问题是( {{c1 a}} ). #flashcard
|
||||
A. 南北问题
|
||||
B. .维护世界和平问题
|
||||
C. 反对霸权主义、强权政治问题
|
||||
D. 建⽴国际经济政治新秩序问题
|
||||
- extra:: 美国=霸权主义,反对美国来维护世界和平
|
||||
id:: 64870507-34f9-422d-b543-727494bcc448
|
||||
3. 当前维护世界和平的根本途径是( {{c1 c}} ). #flashcard
|
||||
A. 实⾏有效裁军和军控
|
||||
B. 发挥联合国的维和作⽤
|
||||
C. 反对霸权主义和强权政治
|
||||
D. 加强国际⼲预
|
||||
- extra:: 民族资产阶级最后被收购了
|
||||
id:: 64870715-f684-48d8-894c-ad2bddd5f912
|
||||
1. 中国新⺠主主义⾰命时期的统⼀战线包含着两个联盟。其中基本的、主要的联盟是( {{c1 b}} ). #flashcard
|
||||
A. ⼯⼈阶级同城市⼩资产阶级的联盟
|
||||
B. 以⼯农联盟为主体的⼯⼈阶级同农⺠、⼩资产阶级等其他劳动⼈⺠的联盟
|
||||
C. 以⼯农联盟为主体的⼯⼈阶级同农⺠、⼩资产阶级和⺠族资产阶级的联盟
|
||||
D. ⼯⼈阶级同可以合作的⾮劳动⼈⺠的联盟
|
||||
- extra:: 共产党你是会恶心人的
|
||||
id:: 64870745-dadb-467b-a90c-33a99cb70f54
|
||||
3. 我国新时期爱国统⼀战线从根本上说,是( {{c1 b}} ). #flashcard
|
||||
A. 爱国主义性质的
|
||||
B. 政治联盟性质的
|
||||
C. 社会主义性质的
|
||||
D. ⼈⺠⺠主性质的
|
||||
- extra:: 硬背吧
|
||||
id:: 648707a6-6088-409d-a3d1-5666d23c5af7
|
||||
4. 新时期我国爱国主义的主题是( {{c1 a}} ). #flashcard
|
||||
A. 建设有中国特⾊社会主义
|
||||
B. 实现国家统⼀
|
||||
C. 加强⺠族团结
|
||||
D. 增强⼈⺠凝聚⼒
|
||||
- extra:: 重点是体制
|
||||
id:: 648707f5-4cc3-43f4-9709-34f99e05481e
|
||||
1. ⼗六届四中全会指出,提⾼党的执政能⼒的核⼼是( {{c1 d}} ). #flashcard
|
||||
A. 加强党的领导
|
||||
B. 改善党的领导体制
|
||||
C. 建设⾼素质的⼲部队伍
|
||||
D. 保持党和⼈⺠群众的⾎⾁关系
|
||||
- extra:: 共产党纯变态
|
||||
id:: 648708c8-b45f-48b3-bb42-4dff84cbea23
|
||||
3. 政党区别于其他政治团体的根本标志是( {{c1 a}} ). #flashcard
|
||||
A. 政党是阶级⽃争发展到⼀定历史阶段的产物
|
||||
B. 政党同国家政权紧密联系
|
||||
C. 政党有⾃⼰的纲领
|
||||
D. 政党有⾃⼰的奋⽃⽬标
|
||||
- id:: 6487090c-61e8-44ed-81a4-f3e07e1a8731
|
||||
4. ⼀个政党在社会历史进程中是否起促进作⽤,取决于该党是否( {{c1 b}} ). #flashcard
|
||||
A. 取得执政地位
|
||||
B. 代表先进⽣产⽅式
|
||||
C. 维护⽆产阶级利益
|
||||
D. 符合统治阶级的需要
|
||||
- LATER [[学交]] {{renderer :todomaster}}
|
||||
collapsed:: true
|
||||
SCHEDULED: <2023-06-13 Tue>
|
||||
- DONE 看格式要求 _Follow the ABC (Abstract Body Conclusion) Format for all Letters/Memos_
|
||||
- DONE Job application letter
|
||||
- Cover letter (application letter)
|
||||
- #+BEGIN_VERSE
|
||||
[Your name]
|
||||
[Your address]
|
||||
[Your city, state and zip code]
|
||||
|
||||
[Date]
|
||||
|
||||
[Hiring manager's name]
|
||||
[Hiring manager's title]
|
||||
[Company name]
|
||||
[Company address]
|
||||
[Company city, state and zip code]
|
||||
|
||||
Dear [Hiring manager's name],
|
||||
|
||||
I'm writing to express my interest in the position of [job title] at [company]. [Explain how you heard about the job and name your contact if you were referred by someone within the company.] I believe my [skills and qualifications] make me an ideal fit for this job.
|
||||
|
||||
[Use the second paragraph to elaborate on how you would help the company. Reference specific campaigns or projects when possible.]
|
||||
|
||||
[Use the third paragraph to summarize your key qualifications. Elaborate on your most important accomplishments and include details that you were unable to provide in the more concise format of your resume.]
|
||||
|
||||
[Use the fourth paragraph to briefly explain why you want to work for this company. Mention the additional documents included with your cover letter, and express your excitement about moving forward in the hiring process.]
|
||||
|
||||
Sincerely,
|
||||
[Your name]
|
||||
|
||||
#+END_VERSE
|
||||
- DONE Academic
|
||||
- DONE research proposal
|
||||
- Format
|
||||
- #+BEGIN_VERSE
|
||||
Your proposal should include the following:
|
||||
|
||||
1. TITLE
|
||||
|
||||
Your title should give a clear indication of your proposed research approach or key question
|
||||
|
||||
2. BACKGROUND AND RATIONALE
|
||||
|
||||
You should include:
|
||||
|
||||
the background and issues of your proposed research
|
||||
identify your discipline
|
||||
a short literature review
|
||||
a summary of key debates and developments in the field
|
||||
|
||||
3. RESEARCH QUESTION(S)
|
||||
|
||||
You should formulate these clearly, giving an explanation as to what problems and issues are to be explored and why they are worth exploring 4. RESEARCH METHODOLOGY
|
||||
|
||||
You should provide an outline of:
|
||||
|
||||
the theoretical resources to be drawn on
|
||||
the research approach (theoretical framework)
|
||||
the research methods appropriate for the proposed research
|
||||
a discussion of advantages as well as limits of particular approaches and methods
|
||||
|
||||
5. PLAN OF WORK & TIME SCHEDULE
|
||||
|
||||
You should include an outline of the various stages and corresponding time lines for developing and implementing the research, including writing up your thesis.
|
||||
|
||||
For full-time study your research should be completed within three years, with writing up completed in the fourth year of registration.
|
||||
|
||||
For part-time study your research should be completed within six years, with writing up completed by the eighth year. 6. BIBLIOGRAPHY
|
||||
|
||||
You should include:
|
||||
|
||||
a list of references to key articles and texts discussed within your research proposal
|
||||
a selection of sources appropriate to the proposed research
|
||||
|
||||
#+END_VERSE
|
||||
- DONE academic paper
|
||||
- DONE abstract
|
||||
- Major Types of Abstract - Descriptive Abstracts
|
||||
- ● Short -uaually less than 120 words.
|
||||
- ● Includes:
|
||||
- ● purpose of the paper/work (objectives)
|
||||
- ● metho used
|
||||
- ● scope of the paper/work
|
||||
- ● introducing the subject.
|
||||
- ● Doesn’t include:
|
||||
- ● results, conclusions and recommendations
|
||||
- It aims to provide the reader with brief summaries (1-2 sentences) of each of the sections of the paper.
|
||||
- ● A descriptive abstract summarizes the main points of a document without
|
||||
providing any analysis or interpretation, simply describing what the document
|
||||
contains. It is typically very short and doesn't provide any information beyond
|
||||
what you would find in the document's table of contents.
|
||||
- ● An outline of your work
|
||||
- •Major Types of Abstract - Informative Abstracts
|
||||
- ● Fairly short - from 250 words to a page or more.
|
||||
- ● Include:
|
||||
- ● purpose of the work/paper (research background /objectives)
|
||||
- ● method used
|
||||
- ● scope of the work
|
||||
- ● results / findings
|
||||
- ● conclusions and recommendations
|
||||
- ● contributions, novelty (optional)
|
||||
- It focuses on providing the results of the research and describing the
|
||||
conclusion, contribution and vovelty that can be drawn from these
|
||||
results.
|
||||
- DONE introduction
|
||||
- a clear sense of purpose,
|
||||
thorough understanding of reader needs, and
|
||||
close attention to correct formats.
|
||||
- Research paper introductions are always unique.
|
||||
After all, research is original by definition. However, they often
|
||||
contain six essential items. These are:
|
||||
- **An overview of the topic.**Start with a general overview of
|
||||
your topic. Narrow the overview until you address your paper’s specific
|
||||
subject. Then, mention questions or concerns you had about the case.
|
||||
Note that you will address them in the publication.
|
||||
- **Prior research.**Your introduction is the place to review
|
||||
other conclusions on your topic. Include both older scholars and modern
|
||||
scholars. This background information shows that you are aware of prior
|
||||
research. It also introduces past findings to those who might not have
|
||||
that expertise.
|
||||
- **A rationale for your paper.**Explain why your topic needs to
|
||||
be addressed right now. If applicable, connect it to current issues.
|
||||
Additionally, you can show a problem with former theories or reveal a
|
||||
gap in current research. No matter how you do it, a good rationale will
|
||||
interest your readers and demonstrate why they must read the rest of
|
||||
your paper.
|
||||
- **Describe the methodology you used.**Recount your processes to
|
||||
make your paper more credible. Lay out your goal and the questions you
|
||||
will address. Reveal how you conducted research and describe how you
|
||||
measured results. Moreover, explain why you made key choices.
|
||||
- **A thesis statement.**Your main introduction should end with a
|
||||
thesis statement. This statement summarizes the ideas that will run
|
||||
through your entire research article. It should be straightforward and
|
||||
clear.
|
||||
- **An outline.**Introductions often conclude with an outline.
|
||||
Your layout should quickly review what you intend to cover in the
|
||||
following sections. Think of it as a roadmap, guiding your reader to the
|
||||
end of your paper.
|
||||
- These six items are emphasized more or less,
|
||||
depending on your field. For example, a physics research paper might
|
||||
emphasize methodology. An English journal article might highlight the
|
||||
overview.
|
||||
- DONE conclusion
|
||||
- Presenting the last word on the issues you raised in your paper.
|
||||
- Summarizing your thoughts and conveying the larger implications of your study.
|
||||
- Demonstrating the importance of your ideas.
|
||||
- Introducing possible new or expanded ways of thinking about the research problem.
|
||||
- DONE Report
|
||||
- Informal
|
||||
- DONE letter report
|
||||
- Format
|
||||
- #+BEGIN_VERSE
|
||||
This form is used in the case of brief and informal reports. Its main parts are:
|
||||
|
||||
Heading;
|
||||
Date;
|
||||
Address;
|
||||
Salutation;
|
||||
Body;
|
||||
Complimentary close;
|
||||
Signature.
|
||||
|
||||
The body of the letter can be divided into the following parts:
|
||||
|
||||
Introduction: Here the writer states the problem.
|
||||
Findings: Here the finding of the investigation are presented.
|
||||
Recommendation: After the findings, recommendations are given in the last paragraph of the body.
|
||||
|
||||
The sample is given below to give an idea about the structure of a report.
|
||||
#+END_VERSE
|
||||
- Sample
|
||||
- ```text
|
||||
Opex Apparel Ltd.
|
||||
(A house for best Garments)
|
||||
Dhanmondi, Dhaka
|
||||
|
||||
25th, May 2021
|
||||
|
||||
Managing Director
|
||||
Opex Apparel Ltd.
|
||||
Dhanmondi, Dhaka.
|
||||
|
||||
Ref: Negligence of duty by the staff in our Uttara Showroom.
|
||||
|
||||
Dear Sir,
|
||||
|
||||
In accordance with” your instructions, I personally visited our Uttara
|
||||
showroom to look into its functioning. I made some investigation and
|
||||
therefore submitting my report hereunder. <abstract, introduction>
|
||||
|
||||
A number of worthy customers purchased some exclusive garments
|
||||
but found some problems with fitting after purchase. They tried their
|
||||
best to return the garments but failed because there was no
|
||||
attendant to take the complaint and providing the change. As a
|
||||
result, they made a phone call to our complaint department and filed
|
||||
complaints regarding this issue. <findings>
|
||||
|
||||
In our Uttara branch, there is only one attendant named Mr. Saker to
|
||||
handle the after-sales service. He has been found to be irregular for
|
||||
the last three (3) months. As a result, our customers are getting
|
||||
dissatisfaction causing a decrease in our sales. In this age of
|
||||
competition, losing customers means “Red Alert to the business.
|
||||
|
||||
I have no hesitation to recommend that Mr. Saker may be served
|
||||
with a notice and a really efficient and active man may be sent there
|
||||
for proper functioning. <recommendation>
|
||||
|
||||
I hope that quick action will be taken based on my recommendation
|
||||
for the betterment of our company.<close>
|
||||
|
||||
Yours faithfully
|
||||
|
||||
M. A Khan Secretary
|
||||
```
|
||||
- DONE memo report
|
||||
- Format
|
||||
- Abstract
|
||||
- Clear statement of memo's purpose
|
||||
Outline of main parts of memo
|
||||
- Body
|
||||
- Supporting points, with strong points at the beginning and/or end
|
||||
Frequent use of short paragraphs or listed items
|
||||
Absolute clarity about what memo has to do with reader
|
||||
Tactful presentation of any negative news
|
||||
- Conclusion
|
||||
- Clear statement of what step should occur next
|
||||
Another effort to retain goodwill and cooperation of readers
|
||||
- Sample:
|
||||
- ```text
|
||||
MEMORANDUM
|
||||
|
||||
DATE:
|
||||
|
||||
TO:
|
||||
|
||||
FROM:
|
||||
|
||||
SUBJECT:
|
||||
|
||||
I'm writing to inform you that [statement, reason for writing memo].
|
||||
|
||||
As our company continues to grow … [evidence or reason to support your opening
|
||||
paragraph].
|
||||
|
||||
Please let me know if you have any questions. In the meantime, I'd appreciate your
|
||||
cooperation as [official business information] takes place.
|
||||
```
|
||||
- Formal
|
||||
- DONE Letter Text Combination Form
|
||||
- Types
|
||||
- proposal: A proposal report is a document that outlines a plan or suggestion for a
|
||||
particular project, initiative, or course of action. It is typically
|
||||
prepared by an individual or a team who wants to propose a specific
|
||||
idea, action, or solution to a problem. The purpose of a proposal report
|
||||
is to convince the intended audience that the proposed plan is viable,
|
||||
beneficial, and worth pursuing.
|
||||
- feasibility: A feasibility report determines the outcome of a proposed solution by analyzing all relevant factors.
|
||||
- progress: A progress report is a document that provides an update on the status,
|
||||
achievements, and ongoing activities of a project, task, or initiative.
|
||||
It is typically prepared on a regular basis, such as weekly, monthly, or
|
||||
quarterly, to inform stakeholders about the progress made toward
|
||||
established goals and objectives.
|
||||
- evaluation: An evaluation report is a document that assesses and analyzes the
|
||||
performance, effectiveness, or impact of a project, program, policy, or
|
||||
initiative. It provides an in-depth examination and critique of the
|
||||
subject being evaluated, based on specific criteria and objectives.
|
||||
- problem analysis: A problem analysis report is a document that examines and analyzes a specific problem or issue in depth. It aims to identify the root causes
|
||||
of the problem, understand its impact, and propose potential solutions
|
||||
or recommendations.
|
||||
- recommendation: Recommendation reports, also known as justification reports, propose a specific idea to the reader and provide evidence to support the
|
||||
recommendation.
|
||||
- Template
|
||||
- ```text
|
||||
Report on [topic of the report]
|
||||
Submitted on [date of submission]
|
||||
Summary or Abstract
|
||||
[This summarizes the contents of the report, including your main findings and
|
||||
overall conclusion.]
|
||||
Introduction
|
||||
[This provides insight into the purpose of the report.]
|
||||
Background
|
||||
[This section provides background information for the reader to understand the
|
||||
context of the remaining content.]
|
||||
Methodology
|
||||
[This section explains to the reader what method you followed to gather your
|
||||
findings and make your conclusions. For example, describe if you're using
|
||||
qualitative or quantitative methods in your research.]
|
||||
Findings
|
||||
[Present your findings based on your research.]
|
||||
Conclusions
|
||||
The main issues we found were as follows:
|
||||
[Outline the main issues to address based on your findings.]
|
||||
Recommendations
|
||||
To address these central issues, we recommend the following steps:
|
||||
[Offer clear recommendations of actions based on your findings and conclusions
|
||||
to help solve the problem.]
|
||||
Appendix
|
||||
[List any references used for your research, including articles, papers, or other
|
||||
sources. You can also include any reference materials, such as surveys, tables,
|
||||
charts, or diagrams referenced in your report.]
|
||||
```
|
||||
- LATER 写几篇试试手
|
||||
- LATER 数电 {{renderer :todomaster}}
|
||||
SCHEDULED: <2023-06-14 Wed>
|
||||
- DONE 看 block4
|
||||
collapsed:: true
|
||||
- SI bytes:
|
||||
![image.png](../assets/image_1686315189766_0.png)
|
||||
- LATER 做往年题
|
||||
- LATER Review slides
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-11 Sun 20:05:19]--[2023-06-11 Sun 21:37:27] => 01:32:08
|
||||
:END:
|
||||
- DONE Tutorial 1
|
||||
collapsed:: true
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-11 Sun 20:06:12]--[2023-06-11 Sun 21:13:20] => 01:07:08
|
||||
:END:
|
||||
- DONE Base conversion
|
||||
- Integer
|
||||
- Digits
|
||||
- DONE LSB, MSB
|
||||
- DONE ==2's complement==
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-11 Sun 20:24:32]
|
||||
CLOCK: [2023-06-11 Sun 20:24:34]--[2023-06-11 Sun 20:32:57] => 00:08:23
|
||||
:END:
|
||||
- convert to 2's complement (negative numbers)
|
||||
- Invert the bits of that representation
|
||||
logseq.order-list-type:: number
|
||||
- add 1
|
||||
logseq.order-list-type:: number
|
||||
- convert from 2's complement (negative numbers)
|
||||
- subtract 1
|
||||
logseq.order-list-type:: number
|
||||
- invert the bits of that representation
|
||||
logseq.order-list-type:: number
|
||||
- or:
|
||||
- invert bits
|
||||
logseq.order-list-type:: number
|
||||
- add 1
|
||||
logseq.order-list-type:: number
|
||||
- Subtraction with 2's complement
|
||||
- DONE Floating point formats
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-11 Sun 20:53:09]--[2023-06-11 Sun 21:09:13] => 00:16:04
|
||||
:END:
|
||||
- IEEE 754 FP
|
||||
- $$ Value = (-1)^s * 1.f * 2^{e-127} $$
|
||||
- s: sign
|
||||
- f: Mantissa
|
||||
- e: exponent
|
||||
- Parity
|
||||
- LATER Tutorial 2
|
||||
- LATER Tutorial 3
|
||||
- LATER Tutorial 4
|
||||
- LATER 数据库
|
||||
SCHEDULED: <2023-06-15 Thu>
|
||||
- {{embed ((647bf024-fa40-4786-9770-e16da8b57f0f))}}
|
||||
- LATER [[产品开发]] {{renderer :todomaster}}
|
||||
collapsed:: true
|
||||
SCHEDULED: <2023-06-16 Fri>
|
||||
- DONE 整理考点
|
||||
:LOGBOOK:
|
||||
CLOCK: [2023-06-09 Fri 15:05:10]--[2023-06-09 Fri 15:05:11] => 00:00:01
|
||||
:END:
|
||||
- LATER See past exam papers
|
||||
- LATER 整理 ppt
|
||||
- DONE Week 1
|
||||
- {{embed ((648581e7-cc5c-4514-9c2a-0b6af4adc5bb))}}
|
||||
- {{embed ((648594af-3833-4991-a4c2-2e9c8430a122))}}
|
||||
- [Topic 4: Product Planning](https://docs.google.com/document/d/17RTFywNdyxAnf7qcb4drrn_shtRjSRhO/edit)
|
||||
- {{embed ((64859157-dc41-453d-95ea-39e2280ea735))}}
|
||||
- DONE Week 2
|
||||
- {{embed ((6482bafb-b96b-44c3-834b-8b4966c1dc0c))}}
|
||||
- {{embed ((64857305-2925-485f-9aed-e15511b42149))}}
|
||||
- {{embed ((64857305-a186-4927-890d-607f66d97f95))}}
|
||||
- DONE Week 3
|
||||
- DONE Week4
|
||||
- LATER 概率论 (隔了一个周末)
|
||||
collapsed:: true
|
||||
SCHEDULED: <2023-06-19 Mon>
|
||||
- {{embed ((647bf024-41f1-45e7-afaf-f49026e826d6))}}
|
||||
- ![2023-06-09-13-21-19.jpeg](../assets/2023-06-09-13-21-19.jpeg)
|
||||
-
|
File diff suppressed because it is too large
Load diff
Loading…
Reference in a new issue