分析瘫痪 [英] Analysis Paralysis

查看:84
本文介绍了分析瘫痪的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我读完Kernighan和Ritchie之后,我发现我对C一无所知。


读完Lippman后,我意识到我对C ++一无所知。

读完Meyers后,我意识到我对OO一无所知。


读完Gamma之后,我意识到我对模式一无所知。

读完Stroustrup后,我意识到我对STL一无所知。


现在我正在读Alexandrescu,我意识到我一无所知

模板。


亲爱的Usenet,我的愤怒的问题是:


....

现在开始编码是否安全? ;-)


也就是说,在什么时候我可以感到无耻地战斗这个

Wes Craven-ish害怕下一本书我接受了非常好的,非常雄辩的,非常非常明智地告诉我

我一直在做的一切都是错的?


舌头紧紧地贴在脸颊上,

(但眼睛坚定地注视着回应)


-Jeff

After I read Kernighan and Ritchie, I realized I knew nothing about C.

After I read Lippman, I realized I knew nothing about C++.

After I read Meyers, I realized I knew nothing about OO.

After I read Gamma, I realized I knew nothing about Patterns.

After I read Stroustrup, I realized I knew nothing about the STL.

Now that I''m reading Alexandrescu, I realize I know nothing about
Templates.

My exasperated question to you then, dear Usenet, is this:

....
Is it safe to start coding now? ;-)


That is to say, at what point can I feel brazen enough to battle this
Wes Craven-ish dread that the next book I pick up is going to very
politely, very eloquently, and very, very sensibly inform me that
everything I''ve been doing is wrong?

With tongue firmly in cheek,
(yet eyes firmly fixated on responses)

-Jeff

推荐答案

Jeff_Ch写道:
Jeff_Ch wrote:

也就是说,在什么时候我可以感到厚颜无耻,无法与之抗争

Wes Craven-ish担心我接下来的那本书会很有礼貌,非常雄辩,非常非常明智地通知我

我一直在做的一切都是错的?
That is to say, at what point can I feel brazen enough to battle this
Wes Craven-ish dread that the next book I pick up is going to very
politely, very eloquently, and very, very sensibly inform me that
everything I''ve been doing is wrong?



如果你读完,即使你完全理解,所有好的编程

书在世上,但没有编程任何东西,你什么都不知道。


现在开始编码,如果你不使用最推荐的,强大的,可靠的,便宜的,可重复使用的方式是否所有情况。


-

Salu2

If you read, and even if you completely understand, all good programming
books in the world, but have not programmed anything, you know nothing.

Start coding now, don''t care if you don''t use the most recommended, robust,
portable and reusable way in each and all cases or not.

--
Salu2


文章< 11 **********************@i42g2000cwa.googlegroups .com> ;,
je ********* @ cox.net 说...
In article <11**********************@i42g2000cwa.googlegroups .com>,
je*********@cox.net says...

读完Kernighan之后Ritchie,我意识到我一无所知C.
After I read Kernighan and Ritchie, I realized I knew nothing about C.



[提到更多精美的书籍已经过了......]

[ mention of more fine books elided .... ]


现在开始编码是否安全? ;-)
Is it safe to start coding now? ;-)



当然。

Sure.


也就是说,在什么时候我可以感到肆无忌惮为了战斗这个

Wes Craven-ish担心我接下来的那本书会非常有礼貌,非常雄辩地非常非常明智地通知我/>
我一直在做的一切都是错的?
That is to say, at what point can I feel brazen enough to battle this
Wes Craven-ish dread that the next book I pick up is going to very
politely, very eloquently, and very, very sensibly inform me that
everything I''ve been doing is wrong?



如果你对待开放改进因为意思错了,那么你现在可能会好好放弃 - 编程基本上只不过是一个精确的表达思路。鉴于我们如何表达我们对计算机理解的想法之间的巨大差异,以及除此之外表达思想的典型表达方式,仍然存在激烈的空间

的改善。考虑到人们在这方面的创造力,我希望看到

改善将在未来很长一段时间内继续发生。


-

后来,

杰瑞。


宇宙是自己想象的虚构。

If you treat "open to improvement" as meaning wrong, then you might as
well give up now -- programming is basically little more than a precise
expression of thoughts. Given the (huge) difference between how we have
to express our thoughts for the computer to understand, and the typical
way of expressing thoughts otherwise, there''s still room for drastic
improvement. Given people''s inventiveness in this area, I expect to see
that improvement to continue happening for a long time to come.

--
Later,
Jerry.

The universe is a figment of its own imagination.


Jeff_Ch写道:
Jeff_Ch wrote:

现在开始编码是否安全? ;-)
Is it safe to start coding now? ;-)



Nope。阅读重构,重构模式和测试驱动

开发。


完成后,开始编码总是安全的。


阅读所有其他书籍的一个谬误是,他们可以让你认为所有的OO和设计意味着你必须首先获得设计,或者

你被搞砸了。


事实上,OO一直意味着你可以动态改变设计,因为

你添加需要新设计元素的功能。所有那些老作家

遵循的做法与重构非常相似,但他们从不打扰

告诉你如何。 (而且许多其他作者实际上告诉你,只有明智的

程序员才能预先设计。)

Nope. Read Refactoring, Refactoring to Patterns, and Test Driven
Development.

After you do, it''s always safe to start coding.

One fallacy of reading all those other books is they can make you think that
all of OO and design means you must get the design right, the first time, or
you are screwed.

The truth is that OO has always meant you can change a design on the fly, as
you add features that need new design elements. All those old authors
followed practices very similar to refactoring, but they never bothered to
tell you how. (And many other authors actually tell you that only wise
programmers design up-front.)


也就是说,在什么时候我是否能够肆无忌惮地为这场战斗而奋斗

Wes Craven-ish害怕我接下来的那本书很有礼貌,非常雄辩,而且非常非常明智告诉我

我一直在做的一切都是错的?
That is to say, at what point can I feel brazen enough to battle this
Wes Craven-ish dread that the next book I pick up is going to very
politely, very eloquently, and very, very sensibly inform me that
everything I''ve been doing is wrong?



为什么要阅读f --- er否则?


-

Phlip
http://www.greencheese.us/ZeekLand < - - 不是博客!!!

Why read the f---er otherwise??

--
Phlip
http://www.greencheese.us/ZeekLand <-- NOT a blog!!!


这篇关于分析瘫痪的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆