译文语言

如何与同事有效沟通

开发者和非技术同事之间经常存在沟通障碍：一方习惯用"说明书"式的技术文档沟通，另一方则依赖"对话"来获取信息。解决这一问题的关键在于"翻译"和"重复"。所谓翻译，不是语言转换，而是切换信息框架——不要急于解释技术实现细节，而是聚焦于解决方案带来的实际效果。同时，重复是正常的沟通工具，每次重复都能让对方多理解一点，最终拼凑出完整的认知图景。

相关报道

Keep Your Slop to Yourself
3.0
David Gasquez argues that "slop"—low-effort, AI-generated content—degrades online spaces and should be kept private. He criticizes the growing trend of publishing thoughtless AI outputs as public work, calling for higher standards and responsibility in content creation.
Don't Roll Your Own
2.0
The article argues against the common security advice "don't roll your own crypto," showing how it's inconsistently applied. It demonstrates that many widely-used cryptographic systems do involve custom implementations, and that the real issue lies in avoiding known vulnerable constructs like ECB mode or weak random number generators, not in writing original code entirely from scratch.
Don't Roll Your Own ...
2.0
The author argues that web developers should stop implementing custom browser features like scrolling, link navigation, text selection, password fields, and date pickers. Custom implementations break familiar user behavior, cause accessibility issues, and create inconsistent experiences across websites.
Don't Roll Your Own
1.5
The article argues that the advice "don't roll your own" regarding cryptography is not about discouraging learning or hobbyist experimentation, but about cautioning against deploying self-made cryptographic systems in production environments where security vulnerabilities could have serious consequences.
You're on Your Own – Not Anymore
1.0
This work explores the shift from individual responsibility to collective support systems, examining how communities and institutions can alleviate the burden of self-reliance in modern society.

如何与同事有效沟通

Keep Your Slop to Yourself

3.0

David Gasquez argues that "slop"—low-effort, AI-generated content—degrades online spaces and should be kept private. He criticizes the growing trend of publishing thoughtless AI outputs as public work, calling for higher standards and responsibility in content creation.

Don't Roll Your Own

2.0

The article argues against the common security advice "don't roll your own crypto," showing how it's inconsistently applied. It demonstrates that many widely-used cryptographic systems do involve custom implementations, and that the real issue lies in avoiding known vulnerable constructs like ECB mode or weak random number generators, not in writing original code entirely from scratch.

Don't Roll Your Own ...

2.0

The author argues that web developers should stop implementing custom browser features like scrolling, link navigation, text selection, password fields, and date pickers. Custom implementations break familiar user behavior, cause accessibility issues, and create inconsistent experiences across websites.

Don't Roll Your Own

1.5

The article argues that the advice "don't roll your own" regarding cryptography is not about discouraging learning or hobbyist experimentation, but about cautioning against deploying self-made cryptographic systems in production environments where security vulnerabilities could have serious consequences.

You're on Your Own – Not Anymore

1.0

This work explores the shift from individual responsibility to collective support systems, examining how communities and institutions can alleviate the burden of self-reliance in modern society.