Listen up intern
- It is impossible to learn everything in the industries in just a few months
- Get overview on the industry
- Focus on building connection instead
- Find people to learn from, attach to that people
22 May 2018
This article give advice to interns, networking is much more important than the solid work skills.
We can share this video to the newbies.
I had a black dog, his name was depression
- Express emotion
- Write emotion dairy
- Exercise
22 May 2018
An impressive video about depression, not very informative, but attractive to see.
What makes us feel good about our work?
- Meaningless job crush the internal joy on doing tasks
- Management need to let employees feel the job’s meaning, not utilize them as a tool by money
- Adding motivation is not difficult
- Elimatinating motivation is incrediblely easy
- People like things which they put effort on it
- Pre-industrial revolution
- Efficency > Meaning
- Knowledge economy
- Meaning > Efficency
22 May 2018
Worth re-watch and move the review to an separated article
Whiteboard Interviews Suck, Get Good at Them Anyway
Whiteboard interview 嘅問題同工作唔大關係，但係D問題guarentee interviewee 水平唔會太差，係一個保底策略
22 May 2018
Tech blog 同side project 可以幫你揾到interview嘅機會，但係最後都係要靠whiteboard interview
How to Read Code
- 先睇main function
- 寫得好嘅 main function 可以睇到成個program 嘅overview
- 明左成個program 嘅structure可以幫助理解細D嘅component
- 㨂重要嘅code去睇
- 通常睇code都係有個目標，例如想查其個feature係點implement，要debug。
- 要時時刻刻記住個目標，skip曬冇關嘅code
- 睇左main function明左個program structure後，要揾出邊D code同個目標有關應該易好多
- 小心理解program入邊嘅comment 同 variable name
當D code睇唔明嘅時候，可以留意下D comment 同variable name。好嘅code嘅comment 同 variable name都係有意思，細心思考可以得到一D貼士。
但係要小心，comment 可能冇update到，同D logic唔match。要記住comment始終係輔助，要以code為主 - 睇Git history 同 GitHub pull request
做完以上3點，都睇唔明嘅時候，可以試下問人。如果有用version control，例如git嘅話，可以用git blame同 git log -p 去查下段code係邊個寫嘅，就揾到人問。
如果有用類似Github嘅version control service，可以睇返以前個pull request，睇返當時D人嘅discussion，可以得到有個D code嘅context
其實以上嘅skill work唔work，好睇D code寫得好唔好。如果D code寫到亂七八糟，用咩skill都好難睇得明。一條team嘅productivity，長遠黎講唔係depends on D code 出得有幾快，唔係depends on 用嘅technology有幾新，而係D code寫睇易唔易睇，易唔易maintain
24 May 2018
將D point 整理入 Pick up new project 之後就唔洗重讀
面对 bug 的正确姿势
係一個management嘅角度睇bug嘅處理手法
- 管理層要在乎code quality
- 如果唔俾足夠嘅資源俾developer，慢慢就會形成一種「交貨」嘅文化。冇人會想負責任，唔會主動fix bug，畢竟bug fixing好多時都係吃力不討好嘅工作。
- Bug fixing task集中係一個人身上
- 如果單睇做task嘅performance去assign task，所有難嘅task都會去曬rockstar engineer身上。而其他人就冇機會透過D難嘅task去進步，咩都靠曬rockstar engineer，做成一個single point of failure
- 要解決E個問題，似乎可以透過build up sharing 嘅culture，嘗試去sychronize成條team嘅knowledge
- 以獎勵fix bug嘅系統好易俾人利用
- 變相獎勵多bug嘅team
- 自己製造bug去fix
Maintain住code quality嘅好處唔明顯，好多人都以為個system做到野就得。文中有一句話形容得好貼切。Code quality好都唔保證個future development會快，又唔保證唔會有新嘅bug。但係code quality差，development就一定快唔到。
24 May 2018
- Software engineering 始終係工程，資源係好重要，無論係人才、時間定錢
- 冇resources，又想做到又快又好真係唔可能，做到出黎已經要偷笑
- Team management 唔但係講究進度，訓唔訓練到人才都係好重要
- 有時寧願做得慢一D，都要將D bug assign俾D做得唔係好熟手嘅人，靠佢地練下功，長遠可以提升team嘅水平
- 培養人才又係冇resources好難做到
以下無需重讀
Frustration Detection
UX差好多時唔係一個software bug，單從code嘅層面係detect唔到，因此要主動去check。
- Check 個page 用左幾耐去load
- Check user 有冇不斷refresh個page
- 要特別check埋hotkey(F5 / cmd + r)
- Check user有冇狂㩒隻mouse
- 好可能係個網頁冇反應，或者有D button錯誤地disable左
24 May 2018
Don’t need to re-read
Stuff at the Top of an SVG
篇文分析左svg嘅content,同埋邊D tag可以remove。
22 May 2018
Re-read when handle SVG
The Case of the Stolen Source Code
Product嘅source code俾人偷左，但係公司唔擔心個product俾人clone一個free version出黎。因為好嘅product唔係一件貨，而係一個service。好嘅product唔會單單俾一個clone打低，個product會keep住tune，隨住時代改變。對一間做product嘅公司黎講，精粹係做product嘅team，而唔係做出黎嘅product。
22 May 2018
Don’t need to re-read
Should you put tape over your webcam?
New Web technology allow browser access web camera, which make hacker easier to hack the web camera. Microphone is also dangerous.
21 May 2018
Don’t need to re-watch