2015/07/27 第289期

Wunderlist背后的故事

Productivity型的app一般都是创始团队自己需要用(比如Slack、Wunderlist),才去做的。自己就是用户,做自己也想用的东西。Wunderlist前不久被微软收购了。

怎么会有这个idea的?"We didn't really have an idea, but we had a specific problem to solve—and I think that was the initial success factor. Wunderlist was the result of trying to fix that problem by building a product that's simple, intuitive, beautiful, and fast."

创业过程中最大的困难是?"Focus was by far (and regularly is) the biggest roadblock ... As soon as you have success, you try to grow it by doing more and more, in our case, building more features, supporting more platforms ..."

"In general, fix your own problem. That always worked for me, I only build products I desperately want to use myself. Building products requires passion and patience, and if you don't enjoy it, don't do it. "

What are some of the biggest red flags in an interviewee

来自 Quora 掌管招聘、人士的 Sara Smith 的回答。有些人面试的时候就是一副苦大仇深的样子:“我老板对我不好;我现在的公司很烂;我学不到新东西了;我恨这个、恨那个”。面试中就表现出满满负能量,谁还敢要你?

Auto-Remediation at LinkedIn

随着业务增长、系统变得越来越复杂,工程师们(尤其是运维、oncall的人)收到的 alert 会越来越多,甚至比业务增长还快。解决 alert 的流程有不少步骤是可以自动化起来的,比如推送最相关的监控数据帮助 troubleshooting,而不用人为地打开许多不同的dashboard去拼凑各种指标。

管道胶布型的程序员

我超爱这篇文章的。管道胶布型程序员都是实用主义者,他们勇于使用快糙猛的方法解决问题,而不是像(伪)学术派那样用那种“高级”的、杀猪用牛刀的、复杂的技术让问题变得更复杂。

文中树立了一个典型的管道胶带型程序员:Jamie Zawinski,网景早期员工,Mozilla的命名者。"You’re not here to write code; you’re here to ship products." 管道胶带型程序员会尽量避免各种复杂的抽象、多线程、多继承,尽量避免引入新的系统、新的依赖、新的学习曲线、新的oncall麻烦制造者。是不是只有半吊子、半桶水的程序员才会整天争执哪种技术优越?Boy, please get things done!

以前有分享过Jamie Zawinski的文中:【jwz:离开网景/Mozilla

来自Paul Graham的创业建议,懒人包

这是速读版,总结归纳了PG比较经典的那几篇文章,有不少好词好句。这些文章大部分湾区日报以前都分享过了。