The Thinking Behind Micro-interaction

Micro-interaction design flow

1. Hand sketch and map out the transitions of the interaction
2. Understand the core concept behind this design
3. Try to use simple and intuitive interaction rather than complex interaction
4. Staggered time in a single screen
5. Logic between screens

與設計架構當朋友

架構設計最重要係有冇令人信服嘅理由

• Pixnet嘅架構設計
  1. 架構先決
     • 流程唔可以無視人員，只睇技術
     • 技術會影響公司文化，business嘅擴展
  2. 冇完美架構，只有最適架構
     • 要睇context
     • 唔能夠指出架構嘅決陷，代表未掌握
  3. 架構係演進的，預想但唔好過早調優
• 技術選型嘅三個角度
  • Cost
  • Flexibility
  • Time to market
• Low Cost + flexible
  • Premature debt
• Low cost + short time to market
  • Difficult to maintain
  • No HA
  • No scalability
• Flexible + short time to market
  • Business debt (燒錢)
• Conclusion
  • 思考各種可能性
  • 同其他人做善意嘅思考衝撞
  • Plan for (sudden) requirement change
  • No perfect architecture，唔好對自己嘅架構冇信心，重點係要知道自己點解咁設計

Productivity advice for the weird

Productivity 可以分做3個tier，由最重要嘅Fundamentals，到Psychology，最後嘅Details。大部份嘅productivity技巧都係最頂層嘅Details，都只係錦上添花。反而最平凡嘅Fundamentals先係起最關鍵作用

Fundamental

• 8 hours of sleep. Every. Night.
• Clear you apartment: A place for everything, and everything in its place!
• Have a consistent meal plan, and stick to it
• Optimize calendar

Psychology

• Set clear boundaries
  • 唔好負擔太多野
• Be unapologetic with what you need
• Be positive and resilient

Detail

Should spend less than 10% time on it

• If you can fix something with money, fix it with money
• Automate your repetitive tasks
• Use systems to help you be proactive about things you want to do

專案經理該在45歲前思索的4個職涯方向

1. 負責大型甚至巨型的案子
2. 成為高階主管的幕僚
3. 往業務端走，負責市場與品牌規劃
4. 自己創業

What Can You Remove From Your Product?

Perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away.

• Product debt
  • Introduce complexity to the product, which require engineer, designer and QA to handle it
  • User need to handle an extra complexity too
  • Similar to “Carrying cost” in tranditional industries

唐納·川普, 是美國總統, 更是談判高手

Bargining technique, worth re-read again

以下無需重讀

新創公司如何建立優質的工程師到職流程

篇文講左Quora嘅onboarding design。「sink or swim」就咁講好似好型，但實際上係on9嘅。盡快培養新員工嘅實力長遠黎講係好有用。

• 點解要有onboarding
  • 有D人俾少少指引就好productive
  • 俾左train都係唔掂，好可能係員工能力唔夠，盡早identify不良員工
  • 冇training會令員工遲左成為戰鬥力
  • 令新員工有較少壓力
• Onboarding design嘅理念
  • 加速提升新進員工生產力
  • 傳遞新創公司的文化與價值觀
  • 讓新進員工廣泛接觸成功所需的基礎
  • 運用社交讓新進人員融入團隊
• Onboarding 措施
  • Assign mentor
    • Mentor係頭果幾星期會冇左25%或更多生產力
  • First day tasks
    • Set up dev env
    • Do simple code change
    • Run test
    • Push a commit
  • First week task
    • Assign a simple bug fix, feature or experiment
    • Assign the task that mentor require one day to finish, to make sure mentee can finish it within a week
  • Tutorial
    • 解釋codebase
    • 解釋git (git flow?)
    • 解釋testing expectation
    • Introduce debugging & profiling tools
  • Codelabs
    • 說明公司內產品的抽象層(abstractions)和輔助工具(tools)
      • 說明為何一個核心抽象層(abstractions)如何被設計出來， 展示要如何使用它， 演練程式基底(codebase)相關的部分
  • 介紹新人給工作夥伴

12 Jan 2019

The summary is good enough

Do Responsive Sites Have to Be so Tall on Mobile?

Responsive 唔係就咁define 個grid system就算，有D位要redesign個layout，避免個page太長。

What UX designers can learn from 1990s Japanese video games

對比90年代嘅game同易家嘅app嘅UX design

The Magpie Developer

Don’t be distracted by shiny new toys and playthings. User don’t care what technology you use