perplexity 让人打开消息提醒的方式,还是蛮好的,我经常看到这个之后,就老老实实打开了。

这么看来,骨传导耳机其实比普通降噪耳机风险还大些呀,因为会不自觉地调高音量。

今天上午,窗外的云。

4 月确实忙得不可开交,没多少时间看书。还好,上下班通勤的时间,在公共交通上还可以看点儿闲书。

支付宝打开长辈模式,果然干净多了。

聊天记录断舍离。之前每次换设备,都还要把聊天记录搬来搬去,生怕缺了某次聊天的上下文,会耽误事。这次来个大扫除,以后每次换设备,也不备份、迁移了,都是崭新的开始。

昨天徒步后,朋友带着一群人进了家博物馆吹空调。看到这时,一位朋友说:这協字,看起来三个力,就很大力的样子,就是协作呀。简体字的协,一个人用力,两个人在边上看,倒是很像我们干活时的样子啊。

我老觉得,需要打开微信再开的产品,都会被微信吃掉。微信太像贪吃蛇了,用户的注意力在微信上而不在小程序里。

我的灵感经常来自两个场景,一是洗澡,二是散步。但这两个场景下,掏出纸笔或者手机打字记录,都有些怪异。而且——其实我试过,但经常记得过于简略,几天后回顾时,就忘了是什么。

所以我想试试:

  1. 用语音记录内容,语音可以回听。
  2. 用 AI 将内容梳理顺畅,方便快速复制到其他地方(比如发朋友圈)使用。

请同事帮我做了个小工具,粗糙、简陋,Bug 多,但用起来还算顺手。发出来给大家看看,有兴趣且有 Testflight 的朋友,在 iPhone 上可以试试,试用链接:

https://testflight.apple.com/join/1EBDy9d0

笔记叫 Slax Note,Slax 是品牌名,Simple and Relax 的含义,希望这个品牌下的小工具,简单,从容。

已经接到多位用户反馈知识星球的模板消息被封。我们自查没发现滥用,目前的使用均为产品的通知推送,因此正在尝试与微信安全团队沟通。如果真的有问题会修改产品。不过可能是假期原因,不一定能很快得到回复,还请各位朋友耐心等等。

今日动车晚点 333 分钟,值得记录一下。祝福台湾人民。

挺有道理的,一般人确实对你的“规则”不太质疑,比如说我戒酒了,通常人家不劝。但如果说,我今天不喝,他可能会不愉快。

In a quirk of psychology, people typically don’t argue with your personal rules. They just accept them as features of who you are. People question decisions, but they respect rules.

有用户问:为什么很多用户在知识星球里,不用知识星球的长文功能,而是用飞书文档来写内容。

很简单:飞书做得确实好。

知识星球后续可以改进的方向或许是:

  1. 用户贴进来的飞书文档,我们可以生成一份缓存。避免用户“撤回”后,内容没了,星主和其他用户感受不佳。
  2. 尽量改进长文功能——但老实说,不容易。

至少找出三个解决方法,而不是只依赖直觉,接受第一个冒出来的点子。

The 3+ principle: Force yourself to explore at least three possible solutions to a problem. If you find yourself considering only two options, force yourself to find at least one more.

很多解决方案,只想一步,不考虑后果。理想的方案,应该能用较低的成本,比如预期的 20%,解决掉 80% 的问题,且问题不会春风吹又生。

Use the test of time. Test whether you’re addressing the root cause of a problem, rather than merely treating a symptom, by asking yourself whether it will stand the test of time. Will this solution fix the problem permanently, or will the problem return in the future? If it seems like the latter, then chances are you’re only treating a symptom.

邀请其他人参与你的早期设计思考,简单直接地拉到白板前讨论好过给出详细的文档。

Try to keep the clay wet. Rather than writing up a document or creating a slideshow, invite them to a whiteboard and redraw the elements as you worked them out earlier, building up the concept from the beginning.

Stick completely to the concept you already worked out to get feedback on the work you’ve already done. Then once you’ve covered the work you already did, open it up and invite them to suggest revisions. Having seen this concept, do they have any insights about how to drastically simplify or approach the problem differently?

写一份需求说明,shape up 需要具备五点。问题、胃口、方案、坑、不做。

There are five ingredients that we always want to include in a pitch:

Problem — The raw idea, a use case, or something we’ve seen that motivates us to work on this

Appetite — How much time we want to spend and how that constrains the solution

Solution — The core elements we came up with, presented in a form that’s easy for people to immediately understand

Rabbit holes — Details about the solution worth calling out to avoid problems

No-gos — Anything specifically excluded from the concept: functionality or use cases we intentionally aren’t covering to fit the appetite or make the problem tractable

Think of yourself as dead. You have lived your life. Now take what’s left and live it properly.

—MARCUS AURELIUS, Meditations, Book 7

Everyone has an incomplete view of the world. But we form a complete narrative to fill in the gaps.

这个说法很有意思。每个人都是瞎子摸象,但每个人都自己脑补了似乎能自圆其说的信息,其他人看来,可能会觉得傻逼。