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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Nobody Ever Gets Credit for Fixing Problems That Never Happened (2001) [pdf]

201 点作者 xvirk超过 10 年前

12 条评论

alecco超过 10 年前
And the matching rule: badly designed projects that blow up end up getting a lot of attention and resources, their engineers end up looking like heroes.<p>I remember the worst module of a very large J2EE website getting all the attention, got more developers, got 10x more hardware than planned... And in the end the lead was promoted. While several other modules did their work flawlessly and went unnoticed.<p>This is what you get when business people make decisions on technology projects.
评论 #8941621 未加载
评论 #8941578 未加载
评论 #8941459 未加载
评论 #8946766 未加载
评论 #8942009 未加载
评论 #8944307 未加载
评论 #8941820 未加载
评论 #8941740 未加载
kaa2102超过 10 年前
Nassim Taleb provides a good example in his book Fooled by Randomness. Imagine that a politician passed a $1 billion requiring all airline cockpits to be locked prior to 9&#x2F;11. That politician would probably be criticized and then voted out of office.
bruceb超过 10 年前
This is what I think about government in general. People complain about it but we live in country (if in US) where most stuff works, most stuff is safe. We don&#x27;t have ferry disasters, we don&#x27;t have serious virus outbreaks, the power almost never goes out, and the water is drinkable. This is because people work everyday to keep this up.
评论 #8941878 未加载
kev6168超过 10 年前
Sun Tzu talked about this 2500 years ago in the Art of War:<p>&quot;&quot;&quot; What the ancients called a clever fighter is one who not only wins, but excels in winning with ease.<p>Hence his victories bring him neither reputation for wisdom nor credit for courage. &quot;&quot;&quot;
astockwell超过 10 年前
In my experience this goes way beyond productivity. I know you have clients and projects and feature requests and bugs to fix and meetings to attend, but how about that backup scheme for that new project, the one that was bumped to &quot;post-golive&quot;? Or the lack of free disk space monitoring? Or that everything for these three services run as root and use someone&#x27;s primary AWS keys?<p>In software dev or ops, these are the things in my mind that sit in the gulf between &quot;producing&quot; and &quot;improving&quot;. Actually, they sit on the other side of improvement, because given a free hour, I&#x27;d rather spend it learning something than fixing a logging service.
Monkeyget超过 10 年前
There is a video presentation on the topic from the author: <a href="https://www.youtube.com/watch?v=xCkyPc72XNQ#t=97" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=xCkyPc72XNQ#t=97</a>
calinet6超过 10 年前
An extremely good primer on quality at the organizational level. Even if it&#x27;s your &quot;job&quot; to make quality products, the visibly rewarded metrics are often counter to the desired result.<p>The assumed management strategy is to individualize results, punish poor behavior (often directly related to errors or defects) and reward perceived good behavior (&quot;hard work&quot;) at an individual level. In reality, this causes a complex wash of quality-undermining behavior: politics, infighting, de-motivation, perceived unfairness, and worse. Despite the well-proven and scientifically understood reality, managers and even employees are entrenched in the surface level, when in reality the problems are deeper and higher level.<p>This is the wisdom of W. Edwards Deming and his contemporaries. The fundamental epiphany is that quality is the result of <i>how companies are managed.</i> That it is a result of four things: an understanding of knowledge itself (primarily, that our prior assumptions about work are incorrect) -- an understanding of psychology (behavioral science and real motivation) -- knowledge of statistics (for the ability to optimize process, and the knowledge that all behavior has a random element, even that of individuals) -- and finally, a deep understanding of systems and their effects.<p>This thinking brought Japan out of its post-WWII recession. It was the origin of the Japanese quality economy—of Toyota, Honda, Sony, Panasonic, and more Japanese companies with quality products at the core of their success. The Deming prize is still given to companies which embody the values of quality.<p>It worked in Japan because of a cultural readiness for a systemic worldview. It does not gain traction in the US for exactly the opposite reason: we are a culture of rugged individualists, who, despite scientifically proven truth, will not drop our core idea that individuals are the cause of both our successes and our failures. This is especially true for upper management.<p>To be successful, as companies and as a nation, we need a major cultural shift toward systematic quality. We need companies that understand that most of the deficit in the quality of products comes not from poor individuals themselves, but poor links between them, poor management of them, and the poor systems within which they work. Simply lack of attention to systems and process in general causes a standard of organizational chaos, where we truly do rely on the excellence of individuals to keep companies afloat. This is familiar to all of us, but surely there&#x27;s a better way.<p>If every &quot;whose fault is it&quot; question would be translated to &quot;what, at its core, caused this fault&quot;—every company would benefit—and that&#x27;s true even if some fault can be found with an individual. Display extreme restraint, as the better course of action is <i>still</i> systemic. And this isn&#x27;t a strategy of simply &quot;blaming management&quot;—instead, every person in the company needs to work together to improve the system surrounding them, and when every person understands why that view is important and why they&#x27;re a part of it, then the improvement will begin to multiply.<p>This is true in software as it is in manufacturing, and I think the industry is ready for a new body of work to translate Deming&#x27;s ideas to the software field. Skip Six Sigma, skip TQM—too dogmatic and heavy. Focus on Deming&#x27;s core ideas: the importance of systems, understanding of key underlying concepts, and the implementation of them with good leadership from the top. It&#x27;s a new old way, it is a better way, and we need it now.<p><a href="http://en.wikipedia.org/wiki/W._Edwards_Deming" rel="nofollow">http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;W._Edwards_Deming</a>
graycat超过 10 年前
It&#x27;s famous: &quot;The wheel that squeaks gets the grease.&quot;<p>Well, the title says something similar: Wheels that don&#x27;t squeak don&#x27;t get the grease.<p>At least in the US, a fairly strong norm is to be <i>rock solidly practical</i> which can mean operating close to the line of actual irresponsibility and following &quot;Never do today what can delay until tomorrow.&quot; Is such thinking common? In the US, yes. Good? Not really.<p>Or, wait until there is a really bad passenger airplane disaster before implementing some new safety procedures.<p>Wait until there are actual sick people with a threat of an epidemic before implementing the long well understood public health measures.<p>Do much the same for desktop computer security, auto seat belts, actions against smoking, and dozens more.
lucidguppy2000超过 10 年前
The scientific term for work needs to get into the general culture. You can expend a whole lot of energy without doing any actual work. &quot;Working harder&quot; is actually &quot;expend energy&quot; while the actual work done is the same.
guicho271828超过 10 年前
The pdf seems odd to me --- all &quot;fi&quot;&#x27;s are invisible, e.g., &quot;fi&quot;rm, signi&quot;fi&quot;cant, bene&quot;fi&quot;t...
评论 #8941508 未加载
Deuterium超过 10 年前
Futurama said it well: &quot;When you do things right, people won&#x27;t be sure you&#x27;ve done anything at all.&quot; (2002)
ryanmk超过 10 年前
Isn&#x27;t that called a &quot;paycheck&quot;?
评论 #8941484 未加载
评论 #8941270 未加载
评论 #8941553 未加载