---
# System prepended metadata

title: 試用期評估表

---

# 試用期評估表

#### 請敘述過去三個月的表現
##### 團隊合作(跨/同部門)、工作品質、時間管理。
*請描述成功的地方和值得改進的地方*


At the inital stage of developing the product features, I find issues to make the iteration faster according to my previous experience.

在開發前期根據經驗盡量想到問題，加速需求迭代，

For example, I met and solved problems with other team in Command feature that helped update API along with complete sepc doucments.

例如Command功能，在開發過程中一直有找到問題與其他部門思考解決方法，修改api與文件需求

As for time management, in order to reduce developing time, I would make arrangement to time effectively.  If api and data model are not complete yet, I code UI first.  In addition, I use mock data to run the process.  With the procedure, if the design is not well-managed, we are able to adjust it accordingly.  Thus, I save a lot of time.

在時間管理上會利用有限資源將產出最大化，例如Command API與資料尚未確定會先行撰寫畫面，API尚未部屬時會使用假資料模擬測試來確定文件與產品符合，過程中有任何流程上問題也可以反映討論

On the other hand, in quality, I check UI with designers and run spec that reduce QA's work.  Another thing I would do is to write unit test cases to protect code.

在工作品質上提交前與會和UI和開發文件校稿減少QA負擔，再利用剩餘時間補足單元測試提升質量


Sometimes, I can not understand the omain questions which I am not familiar with when other teams ask.

在部分Domain與專案不了解情況下，有時無法有效回答到其他部門問題



##### 專業能力(任務交接/與職務相關…)，請問你認為表現得如何呢?
*請描述成功的地方和值得改進的地方*

I share member's tasks and handle features like submodules, ab testing, pusher encrypted, command, etc. Furthermore, I write common modules and extensions which are low coupling and easy to use.

獨立開發功能並且分擔組員工作量
根據經驗寫出易用的共用模組與擴充

##### 請描述對於你的工作責任&管理的內容，請問你透過什麼方式達到團隊的標準?
*請描述成功的地方和值得改進的地方*

//句法單調, 能不能動名詞開頭
* discussing the issues with other teams when features are not clear
* making sure spec and writing unit test cases before creating pull reqeust
* discussing and sharing tech issue or news with my co-workers 


需求不明確或有問題主動與其他部門提出討論
提交前確認需求
遇到問題會主動同步與組員討論



#### 請提供一個給部門、團隊或公司產品的建議。

1. Feature Engineer: In my opinion, the first suggestion may be choosing one feature engineer who is responsible for tech issues.  In other words, having a feature engineer can greatly alleviate PM's workload and track feature proccess by assembling the meeting.  In conclusion, we need a person who is like the bridge to every department.  


1. feature enginer: 每次需求會議時挑選一位RD當作owner，他必須要掌握功能目前進度與遇到問題，可以減少PM工作量，並統一問題窗口，負責招集tech issue會議


2. QA Test case: One of the most important beneifts to list the test cases is to help the engineer know if the feature is completed.  It resembles the story of BDD user.  By doing so, we save time without redundant back and forth communication among the engineer and QA.

3. QA test case: QA在需求結束後列出 test case，可以讓RD了解開發完成的標準定義，在第一時間過濾掉有功能遺漏release，來有效減少QA負擔


3. Upgrading development tool: Now, my macbook pro hard disk is 128G. I need to remove lots of software to install new version of IDE. As a result, I hope it is possible to upgrade my team members' and my devices.

5. 設備:RD開發工具希望可以提升，目前筆電為128G，安裝IDE與系統占掉大多數，這次在裝新版IDE時因容量不夠被迫刪除

#### 為了達到自己的目標、工作期望，在未來3-6個月你的目標是什麼?請簡述要如何達到這個目標。

Target: strengthen livestream domain

Participating livestream about feature


