I suspect it might work quite well in collaborative mathematics. Publish (internally, to your collaborators) when you get a new idea, have a rough sketch of a proof, find a plausible conjecture, think of a good way of presenting something, etc. Eventually, of course, you'd need to clean it all up and get the bugs out, but frequent informal known-buggy "releases" might be an excellent way to get from zero to a high-quality research paper.
That's an interesting idea, although the discussion was about studying. I assume it can also be applied as a studying technique: Read small chunks of material and solve a lot of problems for feedback.
My point was that you cannot overlook the fundamentals.
Hi everyone,
I am graduating as a philosophy student shortly, and want to pursue computer science / programming/ something-of-that-sort.
I am currently taking some basic math (calculus) and physics (mechanics) courses in order to obtain pre-requesits, and to develop a basic framework. My problem is that I can grasp concepts and ideas, but when it comes to solving specific problems with actual numbers, I seem to shut down. Specifically, it takes me much more time (read "hours") to solve problems that ought to take 10 minutes. This is a particularly bad thing on tests and exams.
I believe that the difficulty I am having stems from so little exposure to symbolic reasoning in the past 5-6 years. I am looking for resources, techniques and advice to "turbocharge" (to use CFAR terminology) my ability to absorb and deeply comprehend technical material, so that solving problems becomes second nature.
Thank you so much for your time,
Jeremy