有人用过 robin 大神的阅读训练五步法吗? 请帮忙看下这个情况

Orion_ChangUID: 3582304

这是第三天尝试这个方法

目前的情况是

我使用了曼哈顿推荐的 PEAR 和 Passage Map 方法
对于一篇500字的文章

如果我花3分钟去读, 那么读完以后一般都不太清楚具体说了些什么.
然后5分钟时间完成后面四步绰绰有余(因为大部分都想不起来), 甚至还可能瞪着天花板发呆.
而然在检查应该要补些什么的时候, 往往需要30分钟去重新读和对照着原文写完第一遍没写的部分.

如果我花6分钟去读
那么剩下五步可能需要些40分钟才能完成(尤其是第二步, 由于写作疏于练习, 表达不清经常修改, 语言不如原文简练, 最后写的总字数比原文还多. 这个步骤花费一吨的时间).
而检查和补漏需要5分左右.

然后每天5篇文章总共需要4个小时半左右

请问尝试使用过这个方法的朋友, 这个情况是正常的吗?

这五步法的第二步是要把全文的内容都写出来吗?    还是有其他的标准?

池学敏UID: 3600934

不知道诶。 5篇文章 耗时 4个半小时 是不是效率有点低。 我只是发表个人意见，不具有参考价值。

若如此UID: 3649064

...是归纳文章内容不是听写或者复述文章内容, 4个多小时的确太多了.

先试下每篇6分钟,保证记忆率了再不断往下压缩时间.

你回忆的时候使劲用脑子想, 能想多少是多少, 然后再认真读一次文章, 对照哪里的信息点漏了, 分析下漏的原因

Orion_ChangUID: 3582304

"第二步，根据你的记忆，按照文章所给的内容，写出你能记忆的所有的东西，顺序写"

这个是原话,  我把它理解为了复述文章内容,  这是不对的吗?

我也考虑过是不是归纳...  但是归纳的话好像这个方法就失去意义   因为本来使用 PEAR 就一直都在归纳

我在读的时候时间充足理解充分的话  读完基本上能全部回忆起来  但是要全部写出来的话要花40分钟  

花时间的地方包括使用语言不熟练 花时间措辞  也包括语言不如原文简练  比原文写的还要多

我应该怎么做?  把第二步当做归纳吗?

Orion_ChangUID: 3582304

我仔细的想了一下, 你说的应该没错, 这里不应该以字面去理解.

我明天试一试第二步只复述段落归纳, 并且尽可能快读完.

谢谢你的回复. You made my day (and possibly next few days).

若如此UID: 3649064

Orion_Chang 发表于 2016-3-28 00:10
我仔细的想了一下, 你说的应该没错, 这里不应该以字面去理解.

我明天试一试第二步只复述段落归纳, 并且 ...

GRE就算是长阅读也只是短短的3~4分钟读完, 想要所有内容都记住是不可能的.
跳过细节, 全文结构和主要内容要清晰就好, 细节记住地方到时回去定位, 所以才要归纳

池学敏UID: 3600934

如果说长阅读 不用定位，回去看原文。这个人的阅读能力除非登峰造极，就是长文章太简单。

Orion_ChangUID: 3582304

这个是可能的啊   虽然不能全部记下来   尤其没办法记下作者的语言

但是总体上来说只需要读懂文章   记住每个段落的大致内容   以及作者是如何呈现这个内容

复述的时候只要跟随着思路  自然就把文章大体上重现出来了   

会漏掉不少...  但是依然够我写40分钟了

我现在依然能回忆起昨天读的最后一篇文章的很大一部分



先定义了 S code 是什么鬼. 由于不断的修改不断的迭代最后形成的一块商业领域无法接受, 甚至有时保存着错误的东西. 有时还可能是多个过时语言的混合体. 到最后谁也不知道到底里面写了啥.

然后说明为什么这个东西会存在, 因为学术领域资金紧缺, 时间也有限, 在呈现一个研究结果的时候没办法去注意这些东西;  然而这些东西在商业领域却无法接受;  很多时候学术领域的成果有转换成商业应用的价值, 当需要这么做的时候 S code 就在中间形成了一个断缺.

OCC 是一个公司专门提供这个断缺的解决方案. 最近他们做了两个这个方面的项目. 其中一个是将一个医疗研究成果商业化, untangle原本的 S code 成为商业能够接受的东西. 另外一个是将一个过时语言和 matlab 程序的混杂物以统一的方式重新呈现出来. 这个项目是为了计算伦敦地下电力线路的负荷以及危险指数.

他们做到这两个项目的方式是这样的:  先拷贝一份原始的程序并确保它能像原始程序一样正常的运行, 然后一块一块的翻译成现代的能被商业领域和商业程序猿接受的程序, 还有可能给它做出改进和升级, 并且测试以确保能正确运行.

他们不是唯一做这个事情的人, 事实上这个已经形成一个行业. 除了OCC 以外还有其他三家也在做这个事情, 包括一个大学的 in-house 项目和其他两家面对开放市场的公司, 他们都在纽约.

这个问题从一开始就不会存在如果研究人员更加注意这个问题, 然而编程本身对研究人员来说只是一种方式而不是一个目的, 甚至形成了这么一个环境: 如果有人太在意这个问题的话会被指责为浪费时间.

但是仍然有违抗环境的人开始主张从根本上解决这个问题, 一个机构称为 SSI 开始鼓励研究人员更加注意不在最初阶段生产 S code, 为了他们自己也为了他们的成果更容易商业化. 他们致力于教会研究人员更好的编程.

虽然这个主张是好的, SSI 已经在这个领域做了很多年了, 其中一位工作人员从98年起就在相关领域从事该工作, 但是并没有很好的成效. 看来这个中间行业在短时间内还会继续有市场.







SOME programmers call it “spaghetti code”. Though error-strewn, it works—most of the time. It is likely to have been written in an out-of-date language, possibly more than one of them. It has grown by accretion, as different graduate students and postdocs, many long since departed to other institutions, have tweaked it, fixed it and patched it. And it is, of course, unannotated, so nobody really knows what is going on inside it.
In the rarefied atmosphere of academia, where enthusiasm is all and budgets are tight, that is generally good enough. For commercial applications, though, it is intolerable. Yet academic spaghetti code frequently contains commercially useful ideas that might be sold to outside companies or employed as the basis of new, startup businesses. So there is a market niche available to be occupied by those willing to take the stuff and untangle it.
One occupant of said niche is Oxford Computer Consultants (OCC), a firm based in the eponymous English city. A recent project it carried out was the transformation of drug-testing software developed by researchers at Oxford University into a commercial package called Virtual Assay, which can speed up preclinical trials of putative medicines. A second began with pieces of code written partly in Fortran, a programming language devised in the 1950s, and partly in Matlab, a more modern language, by researchers at Southampton University. This mixture was turned into RoCiT, a system that engineers at National Grid, the firm which (among other things) runs Britain’s electricity-distribution network, use to calculate the maximum power that underground cables can carry safely.
According to Reynold Greenlaw, one of OCC’s directors, cleaning up spaghetti code starts with the obvious but not-always-easy step of getting a copy of the program to run on one of the firm’s own machines—and, once it is running, to turn out the same results as it does on the originator’s machine. That done, each of the program’s parts can be examined and tested individually, translated into a more modern computing language if required, and upgraded as necessary. Only then, when all parts are working properly, is the spaghetti untangled, the entire program restructured into something a commercial programmer would accept, and annotation added to it so that other programmers can understand exactly how it works.
As might be expected, OCC is not alone in its mission to transmogrify academic software into something business can use. Such an industry exists in America, too. There, though, universities often try to keep the process within their walls. The Venture Development Centre of the University of Massachusetts, in Boston, is one example of an in-house spaghetti untangler for researchers who want to go commercial. The New York University School of Engineering Incubator is another. A third is the Southern Tier Startup Alliance at Cornell, also in New York state.
Untangling spaghetti code in this way would not, of course, be necessary if researchers were better programmers in the first place. But that would involve a change in their incentives, because for most academics writing software is merely a means to an end rather than an end in itself. Those who do put effort into producing good code risk being seen by their colleagues as time-wasters.
Some brave souls are, nevertheless, trying to encourage this change. One such is Neil Chue Hong, founder and head of the Software Sustainability Institute (SSI) at Edinburgh University. The SSI has the self-appointed mission (backed by government funding agencies) of encouraging British academics to code sensibly from the beginning—for their own good, as well as that of any commercial spin-offs.
Mr Chue Hong is a relative newcomer to the task of teaching good programming practices to academics, for the SSI was founded in 2010. Greg Wilson has been at it since 1998, when he started “software carpentry” workshops at Toronto University. He now runs the Software Carpentry Foundation, an international charity, but has not yet succeeded in turning the majority of computing’s academic bodgers into craftsmen. The spaghetti-untanglers, it seems, will be around for a while yet.

Orion_ChangUID: 3582304

另外 robin 大神不是说不定位的吗

Orion_ChangUID: 3582304

事实上面那篇帖子也写了34分钟...  而且还没翻译成英文...

若如此UID: 3649064

Orion_Chang 发表于 2016-3-28 11:37
这个是可能的啊   虽然不能全部记下来   尤其没办法记下作者的语言

但是总体上来说只需要读懂文章   记住 ...

你这种状态挺好, 练多几天, 时间会越来越短的. 可以尝试分析下怎么压缩时间.

Robin大神说不定位是因为他大神...如果你练到他那种地步了的确是可以的...

zerolotusUID: 3707096

robin的帖子在哪里 robin的用户名是？怎么找到它可以看的帖子啊

qilongdrewUID: 3638860

如果在第二部分回忆原文内容的时候用英文写浪费的时间太多，可以尝试用中文，毕竟这个练习是锻炼你对阅读内容的记忆，不是锻炼你的写作