TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Reducing friction as a standard operating method

25 点作者 rayvega超过 15 年前

2 条评论

10ren超过 15 年前
Similar story: shaving a 5 second build/run down to 200ms. It took 2-3 days to implement. I couldn't justify it in terms of time saved; nor did it <i>seem</i> I could use the article's justification that I'd tend to avoid compiling because it was too painful.<p>However, it <i>did</i> change my workflow, in that now I try things out quickly, and even using code like a config file, to test ideas instantly. Perhaps more importantly for me, every time I compile now I get a little feeling of delight, and a data-point suggesting that <i>all problems have solutions</i>.<p>details: <a href="http://news.ycombinator.com/item?id=939523" rel="nofollow">http://news.ycombinator.com/item?id=939523</a>
评论 #951840 未加载
RyanMcGreal超过 15 年前
I like the notion of expanding from a narrow cost/benefit analysis to a broader "opportunities lost cost" - the set of potential new things you can't do because you decided not to reduce friction in your current set of activities.