Thanks for this post, this looks very useful :) (it comes at a great time for me since I'm starting to work on my first self-directed research project right now).
This post is great, I suspect I will be referencing it from time to time.
I don't know if you meant to include the footnotes as well, since they aren't present in this post. For instance, I tried clicking on
After a week, you'll likely remember why you started, but it may be hard to bring yourself to really care[2]
and it just doesn't lead anywhere, although I did find it on your blog.
I'm glad you like it!
Fixed the footnotes. They were there at the end, but unlinked. Some mixup when switching between LW's Markdown and Docs-style editor, most likely.
"Learning to research out of desperate need is like learning to drive on the way to the hospital."
Fully agreed as to the greater point but the flip side is that in real life, if the need is desperate, then entire chunks of this article can be skipped.
For example, if aliens will murder you if you don't tell them the correct name of the " Tiffany" in the CGP Grey poem, then you can blurt out "Theofania" and collapse into a heap in bed. No need to write anything
Similarly, if you are bleeding profusely from a stab wound, then it is probably sufficient to find the nearest competent emergency room and skip the step of quizzing a librarian.
Finally, so as to avoid creating too many strawmen, if you have an acute disease, then finding a few very reliable summary articles and convincing a doctor to help you implement the steps may have excellent odds of curing the disease. For example, there are many protocols for diseases.
This post is part of my "research" series.
Introduction
Sometimes the need is desperate. You have children to raise, cancer to treat, something important broke and you're going down with it. These kind of situations rarely afford you the luxury of time. You have to do the best you can, because it's your life, and you have ultimate responsibility over it. I think information is decisive in almost any scenario. Learning to research out of desperate need is like learning to drive on the way to the hospital. The time to practice any skill is years ago. Or now. Whichever is earlier.
I'm working off of two books: Umberto Eco's How to write a thesis and Mortimer Adler's How to read a book. Both have valuable ideas, and between the two there is enough to put together a first approximation to the process.
I'm writing this down so that:
I am not an expert. This is not a definitive guide. This is work in progress.
What do I mean by research?
In the academic world, "doing research" means getting published. For a thesis, this means a thesis defense; for a paper, this means peer review and editorial review. The process takes a long time and imposes pressures and incentives that I can only describe as perverse.
If slaving away for months or years over something that rides entirely on the approval of others—others who have no stake on it—does not distort the way you think and act, then go back to mining crypto because you've just failed the Turing test. So when I talk about "doing research", I'm not talking about breaking into academia. I think there is some overlap, as academics obviously need research skills, but academic survival is a different and much larger problem.
So what do I mean by "doing research"?
Because efficiency matters here, I'll focus on indirect (non-experimental) learning. That means reading books and talking to people. Note that when I say "book" I am talking about source material in general, including papers, videos, web pages, etc.
Cross-cutting concerns
In aspect-oriented software development, a cross-cutting concern is some work a program needs to do that is conceptually separate from other aspects of the software, but that in practice touches everything else. The classical example is logging: whenever something happens, a message needs to be written to a log. The do-something code and the logging code are completely independent at some level, so even though they have to run together, we'd like to talk about them separately.
There are quite a few cross-cutting concerns in reseach. I'll talk about them here because it's cleaner to do so, but understand that these are relevant at every step.
Reading, fast and slow
In chapter 2 of How to read a book, Adler proposes a classification of reading skills into four levels:
Each level of reading corresponds roughly to a part of the research process. Performing well in one does not automatically mean you will do so in the others, or that you'll know when to use each one. I'll discuss these in more detail as they become relevant, but at the bare minimum get good at skimming.
Research as an anytime algorithm
Many problems can be approached by successive approximation. Say you need to find the best hepathologist money can buy. You can start by just picking a random one. As you learn more, you could favor the ones that come from the most prestigious medical schools (reasoning that they got prestigious by training good doctors) or those that work for the most prestigious hospitals (reasoning that they got prestigious by having good doctors). At some point you may know enough to evaluate a doctor's performance directly. But at any point, you can just stop and pick a doctor.
Some problems cannot be handled this way, at least not in any meaningful way. For instance: back in 2004, billboards popped up in various places reading:
{ the first 10-digit prime in consecutive digits of e }.com
These turned out to be recruitment ads for Google[1]. What can we tell about the result without solving the problem? Very little: it is a 10-digit number, it shows up in e, it is prime. Using one of these pieces of information to narrow down your search is no easier than using all of them and just solving the problem. If you're faced with a really hard problem of this kind (say, breaking RSA) you are probably boned.
While this is discouraging, it doesn't have to mean you've wasted your time. Research is hard work, and important problems have a tendency to crop up again and again. Research will involve writing lots of things down, and a lot of it could be useful down the line, possibly to someone else.
These are the useful side products I know of:
Motivation
I wish I had this one locked down. This post took me months because I couldn't put in more than 20 hours a week. Showing up is huge. I wasn't pressed for time, I just can't seem to keep myself going. At least I got it done. Going by precedent, I would have bet on me giving up.
Here are the things I've noticed working for me:
Bibliothecography
While these days "to Google" means "to search", Google Search is not actually a library (Google Books notwistanding). The landscape of knowledge is not just the books that were written and the authors that wrote them, but also how and where they were kept.
As you build your bibliography—a catalog of sources—you should build a catalog of sources of sources (a bibliothecography). Where did you find your books? Where else could you search? Many specialized collections are either not accessible online, or don't play ball with Google.
There are also university libraries, newspaper archives, academic journals, private collections, etc. Keep track of these explicitly.
Note-taking and annotation
What's the point of taking notes? Aren't you just repeating what your sources say?
Kind of. When you read a book for research, you and its author may not care about the same things. Taking notes means you can highlight the parts that are key to your argument. If you are reading several books, you can record connections between them. And you get to write down your own ideas.
Command-F in real life? Computers are real life! Why not use it and forget about annotation entirely?
Because annotations are intentional. Full-text search can cause three kinds of errors:
There's a distinction between adding notes to a book, and writing notes about a book. I'm going to call the first "annotation" and the second "note-taking".
Annotation is convenient, but it locks the information into its original context. Say you read Robert Heinlein's The Puppet Masters and make a note on the margin that says "body snatchers". When you read Applegate's Animorphs you may not remember that you've read about body snatchers before, or remember that you did, but not where. Now you have to go back and review every annotation you've ever made, which could have been avoided by making a note for "body snatchers" in the first place. Plus, note-taking is medium-agnostic, annotating a movie can get quite involved.
The more you read, the more stuff you have to remember, the harder it gets to keep everything straight. Relying on your memory simply doesn't scale, while note-taking does.
Annotation
I'm squeamish when it comes to annotating books, but it doesn't seem like I have much of a choice. Just as annotation doesn't scale to lots of books, note-taking doesn't scale to very dense books. So how do we annotate?
Using color lets you add more marks without sacrificing speed, if used intelligently. Color must mean something, and you must know what that meaning is. If you know you are looking for the red mark, you'll find it quickly. If you know you are looking for a red mark, you'll have to stop and check each one. If you don't know what color mark you are looking for, then what is even the point?
Add a note at the beginning or end of the book explaining the meaning of each color. Alternatively, you could make an index, but this is painstaking work.
You can highlight passages by underlining them, circling them, adding a dash or vertical bar at the margin, etc. If you use more than one type, use that to convey meaning. For example: underline key arguments, circle definitions, use a vertical bar for quotable passages, and use dashes for everything else.
You don't have to be consistent across books—and probably shouldn't be. If you are annotating a novel you'll probably want to jump to important events or memorable quotes. That isn't that helpful when reading Das Kapital. As long as you can tell what the system is on each book, use whatever makes sense.
Hamlet's "To be or not to be" is about suicide, but he doesn't use the word "suicide". This makes highlighting somewhat awkward, so write the keyword you wish you had instead. When parts of an argument are scattered across several paragraphs, number them. Finally, you can use marginalia to add in connections to other pages or books. Use abbreviations where possible to conserve space.
Note-taking
Journaling
While organization isn't optional, dumping your thoughts as they come on a notebook or plain text file is a big step up from nothing. Because your notes contain only those things you put there on purpose, Ctrl+F or even manually looking for things can work well enough. And the things you are most likely to look up are those that you've thought about recently, so they should be in the last few pages. Even if you keep a more sofisticated system, keep a journal as a low-friction way of getting stuff out of your head.
Files
I'll cover this in more detail in s4.1.2.3, but the basics are to split your notes by type and keep them sorted.
The main categories you'll want are:
What makes this useful is connections. If you go to the note on "Variance" finding a definition is nice, but finding a list of people and books that talk about variance is great.
What is a source?
But, why shouldn't you cite Wikipedia?
Warning: this section is unsourced.
To my mind, there are two main criteria that should be applied when evaluating a source:
Citing a source should make it possible to go and look at it. If I cite The Bible, am I talking about the New King James Bible, the New International Version, or Noah Webster's Bible Translation? Getting the wrong version can be a big problem. And even when everybody agrees on what a source says, the context of a claim is critical to evaluating whether it's true.
Wikipedia actually does really well on both of these metrics. Sure, if you cite Wikipedia is not a reliable source the article could change under you without any warning; but if you cite Wikipedia is not a reliable source, 2022-04-08 17:42 you'll be referring to a specific version of the article, and the problem goes away. You can even check its edit history and see every single change to the article, when it was made, by whom, and what other contributions that person made to Wikipedia. University websites and newspaper sites are usually not this stable. So maybe you should cite Wikipedia, if you're careful about it?
There is a second consideration, which is that questions central to your research deserve more attention and care than questions in its periphery. This means being more or less strict with following claims back to their source. Since you'll have to revise your understanding of what your topic is multiple times, inevitably some sources will in and out of scope as you work.
The process itself
Assembling a bibliography
While the research material you need will be inside books, the other resources in a library are the map that will let you find it. A mere heap of books is not a library, no matter how high you stack them. In fact, the higher you stack them, the bigger the mess gets.
Inside a library you can find:
Online, Google generally serves the part of the catalog and librarian, while Wikipedia serves the part of the reference section.
The process of assembling a bibliography can be conceptualized as three steps:
These steps don't happen in strict sequence. Reading one book will frequently tell you about others, and refine your ideas about what your topic is. I've chosen to discuss the process in this order because as you work, you'll transition from doing more of the earlier kinds of work to more of the latter.
Definition
When pressed for time, being able to skip an entire book with just a brief inspection is no small thing. Writing down a definitive statement on what your subject is may seem like a hopeless endeavor, but do it anyways. You'll work faster and surer, and having your criteria written down will help your understanding evolve.
As you iterate this process, you'll find that you've wasted time with some books, and that you need to re-examine others. Accept the fundamental swingyness of the game, and play your best.
Discovery
There are three sub-skills here:
Finding books
I'll talk about the process as if you were on a library. On the internet things are much the same, except that there is much more to be found, it can be quite a bit harder to find it, and you are missing the (frankly invaluable) help of a librarian. For these reasons, if you live in a major city you may have an easier time doing your research at a physical library instead of online.
In rough order, you'll probably want to:
General encyclopedias such as Wikipedia are the first thing you should check. If there is an article about your topic, read it and look for related articles. Going over the Wikipedia article for "Research" I quickly stumbled upon "Epistemology", "Scientific method", "Metascience", "Primary source", "Library science", and "Scientific literature", among others. Write down relevant-looking books, keywords, and people.
If your subject is well-studied, there are likely courses about it online, in universities, or elsewhere. Obviously, you can take one. But let's say you don't; check if they have a publicly available syllabus. This is a sort of table of contents for the course, so scrape it for books, keywords, and people.
Look up everything you've collected thus far. Use online catalogs; you can consult the catalogs of major national libraries (such as the US Library of Congress) from anywhere with an internet connection.
Check reference works written by and for specialists (such as topic encyclopedias, "handbooks", or bibliographical indexes). Keep in mind some reference works are basically tables of figures in book form, and thus unhelpful to you at this stage. Without some reading done you may be hard pressed to query these effectively, or to understand what they have to say. However, that's ok; right now you are just trying to learn what concepts exist, so if something you don't understand keeps popping up, write it down so you know it's there.
Skim what you've found (I'll discuss how in the next section) to keep expanding your collection. If a book has a bibliography, go to town on it. If it's not at the end of the book, the references may be on a per-chapter bibliography or even in footnotes. If a book seems useful, try other works by the same author[5].
I've put this at the end, but don't be deceived: you should ask for help at every single step (except step 2, unless the library is attached to the university whose courses you are scraping). The librarian may know that some topic is under an unusual keyword[6], or that the catalog is split into a new and old version, or what is that one textbook everybody keeps asking for.
I believe that online journals and Google Scholar have wholly supplanted the traditional role of bibliographical indexes, but they are worth a mention because they are a libary's catalog in book form, and that is a really neat idea.
Skimming
As was promised in section 3.1, let's discuss skimming. When you are doing research, you care about a specific thing (your subject's center) and related things that provide context (your subject's periphery). The goal here is to put a book in center, periphery, or out of scope as quickly as we can manage. In an idealized process you'd read the title of every work you discover, skim everything that seems relevant, superficially read everything that is relevant, and then carefully digest (over several passes) only the stuff that contains critical information.
In chapter 4 of How to Read a Book, Adler proposes the following skimming process:
I can do the above with any book in about an hour. You don't have to do all the steps for each book, you'll often know enough with the first two steps. And I'd add a zeroth step: look at the book's cover; it contains a wealth of information.
Adler proposes an initial classification of books into:
This is obviously and opinionated selection, but there is some sense to it:
Organizing
You may be able to mentally keep track of the books you've read, but keeping track of every book you've seen mentioned is clearly out of the question. In chapter 3 of How to Write a Thesis, Eco explains how to use index-cards to keep track of your bibliography. Obviously we can do better with computers, but I'll explain Eco's system because the principle is the same, and physical index cards are easier to reason about.
Information is organized in files consisting of an ordered collection of cards. A file can be stored in a filing cabinet, carboard box, binder, or by wrapping it in an elastic band, depending on the number and size of cards.
We use cards because they can be kept sorted (a notebook doesn't really lend itself to random insertion), and we keep them sorted so that they can be found quickly. The files we'll discuss are alphabetical, but you could sort them in some other way. For example, you could create a chronological file for historical events.
At the bare minimum you'll want:
This lists all references you are aware of, regardless of whether they make it into your final bibliography or even if they are available. Cards on this file contain full and accurate bibliographic information (or as close as you can manage), directions on how to obtain a copy (when one is available), which category it belongs to (see the previous section), and a space to mark priority books to obtain/read. You may also want to leave some space to note how you originally found out about a book.
This lists all the books you have actually read (not just skimmed) and includes notes on their contents (opinions, summaries, and quotable excerpts). Since you already have an entry on these books in the bibliographical file, you can skip a lot of details.
As recommended extras:
You can add references to other cards with:
The goal is to have one place where you can go to and see all that you have on a thing. For ideas, you want to know where they are discussed, by whom, and what related ideas there are (eg: "modularization (programming)" would link to "Parnas, 1972", "Donald Knuth", and "programming languages", respectively). For authors, what did they write, what is written about them, and who did they debate/collaborate with.
An annotated bibliography, complete with cross references to author and idea catalogs, takes a long time to compile, so they are a valuable partial result (see s3.2).
I had originally written an explanation of how to use Obsidian and Zotero, but it ended up being a huge diversion, so I cut it. If you'd rather have no system than going through the indignity of installing new software, then use a spreadsheet. It's not an elegant solution, but it can be made serviceable with a bit of patience.
Tracking
These are some main points from Gwern's Internet Search Tips, see the original for a far more thorough discussion.
Searching on the internet is work which can get harder without prior notice. Websites change and die, breaking links. This is out of your control. If you've found something useful, archive a copy and make it more findable, at least to yourself. Ideally you'd host a public version. For websites, go to the Internet Archive's Wayback Machine and request an archive copy to be made.
When using a search engine you can search for:
"exact matches"
termA OR termB
-notthiskeyword
site:www.resultsfromthisdomainonly.com
site:www.thisdomain.com/in/this/subfolder/
site:www.thisdomain.com -site:www.thisdomain.com/not/this/subfolder/
site:gov
filetype:pdf
...among others. The operators used above are Google's, but they'll usually work in other search engines. Check out your engine's version of Advanced Search.
If you aren't finding what you are looking for, don't give up right away. Try altering the query a bit.
"the title: with subtitle"
. Try:"the title" "with subtitle
,"title" "with subtitle"
, or even just"title"
Remember that Google Search isn't your only recourse, or even your best.
These don't actually produce or host content.
Google Scholar, Google Books, PubMed, PsycINFO.
Google Images, TinEye, Yandex.
arXiv, Elsevier/sciencedirect.com
HathiTrust, Project Gutenberg
The Internet Archive (web archive, books, video, audio, images, software), LexisNexis (newspapers), Sci-Hub (pirated material), Library Genesis (pirated material)
You can search university websites, blogs, forums, etc, with an in-site searchbar or from Google with the
site:www.domain.com
operator. Depending on the quality of the site's backend, using an external search engine may be your best bet.Check WorldCat and the catalogs of any libraries you have access to for the material you want. If you can commute to a major library (such as the US Library of Congress), make sure to check their catalog (online if possible).
AbeBooks, Thrift Books, Better World Books, Barnes & Noble, Discover Books, findmorebooks. Amazon or eBay only if the above fail.
If something isn't available at your local library, ask if they have an interlibrary loan service. If you are a college student, use your university library; besides books, it will have subscriptions to academic journals.
If you are having trouble tracking down an academic paper, it may be hiding inside a poorly-formatted anthology. Check Gwern's post for details on how to track it down and create a new document with just the relevant pages.
A note on piracy: unless you sip from a truly inexhaustible fountain of money, you'll probably have to resort to pirated material. Even with institutional backing, you may find 100% above-board researcg finantially straining. This in spite of the fact that academic publishers don't pay for researcher or reviewer salaries, and the marginal cost of sending you a copy of a PDF is basically zero. Remember that this is a universe where lootboxes exist, and finding "whales" to sell them to is considered a viable business model.
Using your bibliography
Now that you have source material, let's discuss reading and writing. Let me remind you that, while this post is sequential, the actual process will be a lot messier. Every step can happen at any time, with only a gradual transition from doing mainly one kind of work to another.
Digesting a book
Pre-reading
Before even attempting a thorough reading, you should be following the advice on skimming from section 4.1.2. If you have a summary available, use it to grasp the structure of the text before you start reading. Check what it says against what you've learned from skimming the book.
Audiobooks probably aren't great for every kind of book (math audiotextbook?), but if it's available and it works for you, use it.
You may also want to try reading a limited reading of a book:
A focused reading is one in which you ignore all but a specific aspect of it. Blue suggests reading a story for one of "plot, character, themes, symbolism, or style". This can be a lot of fun. Try picking up a story you've enjoyed, choose a random secondary character, and go through the whole thing again pretending they are the protagonist. Star Wars from Lando's perspective?
A superficial reading is one in which you read from cover to cover without stopping. From chapter 4 of Adler's How to Read a Book:
Analytical reading
This is a summary of ideas from Adler's How to Read a Book, see the original for a more thorough discussion. This is where you'll engage most deeply with a given book, so be prepared to write copious notes.
There are three stages to analytical reading:
In a narrative, this is the plot in one paragraph. In an expository book, this is the main thread of argument.
And not just what the parts are, but how they fit together. An example could be "the introduction presents the problem and states the solution, chapters 1 and 2 provide a historical summary of the field, chapters 3 to 5 explore alternative solutions, chapter 6 presents the solution in full, chapter 7 shows benchmark metrics, appendix 1 proves a point used in chapter 7, appendix 2 is an example implementation"
These are the things that the book revolves around, and that it should answer. Crime and Punishment asks, among other things, "why do men do things that later cause them guilt?"
Any word the author uses specially, you must understand precisely. You must understand what the author is saying even if he uses the same word to refer to more than one concept, or more than one word for the same concept.
These are the individual claims that an author makes.
"Locate or construct" because sometimes arguments are made implicitly. In persuasive writing, this is often used to hide flimsy arguments. "The outsiders are all bad and we should kick them out", for example, is often argued tacitly.
Crime and Punishment concludes "men are more vulnerable to emotion than they believe".
This means not seeking pointless conflict and sticking to the Four valid criticisms, listed below.
Adler considers higher levels of reading to include lower levels, so analytical reading includes inspectional reading, which includes elementary reading. Stage one of analytical reading is performed by inspecting the book.
Adler claims that there are four valid criticisms one can make of an argument:
A concrete and relevant fact is missing from the analysis.
One of the premises of the argument is false.
Either the argument contains a contradiction, or it contains an unsupported claim.
By this we mean that the arguments in the book do not resolve the questions that the author set out to answer, and that we should identify as part of inspecting the book.
By "valid" we mean that these criticisms show that the author's arguments are not sound, in the formal sense.
You should distrust the feeling that you've understood a book. Test your understanding by restate the author's ideas in your own words, and looking for particular examples of general propositions ("Is a brick an essential object?"[7]).
Distrust your sources
If you haven't seen it yet, please check out CGP Grey's Someone Dead Ruined My Life... Again. It is a case study on confronting bad sources with truly heroic integrity. The video is 20 minutes long and very entertaining, so I'll proceed under the assumption that you've watched it.
Summarizing the argument: Grey found a poem quoted in several modern sources containing the name "Tiffany", proving that the name existed when the poem was written. The question of when the poem was written is obviously critical.
Let's see the trail that Grey followed:
In this case, there were two problems. First, the original poem was simply wrong; the name was not Tiffany at all. Second, the context of the poem (when it was written and by whom) was missing. But there are three ways in which a source can mislead you:
There are several ways you can misinterpret a claim:
Creating a skeleton for your work
Types of text
Point one is deciding what you should write. I propose three broad categories of work: exposition, reference, and journal. The difference between these should be obvious from their table of contents.
Both Adler and Eco focus on expository work. However, they both recommend organizing your notes like a reference work (as seen s4.1.2.3). While neither discusses keeping a journal, I believe this helps in two ways:
Ideas that initially seem not worth pursuing, or too hard to concile with an existing framework, can end up being very fruitful. Being able to write them down without commiting to them lets you put them safely away while you focus on something else.
Using an experiment as evidence for a theory it helped develop is double-counting the experiment[8]. Being able to go back and look at a researcher's process is a big help if you are trying to evaluate their work or learn from them.
Thesis last?
Beginning a research project by coming up with your conclusion is famously bad advice.
However, we are not starting off with our conclusion. We've hit the libraries, we've skimmed lots of books (and realistically, carefully read some of them), we've taken notes, and we've assembled a preliminary bibliography. At this point we should start generating hypotheses and narrowing our focus.
There are three things we need to write:
This is the guiding question of our research; our thesis in a sentence. "Does chocolate prevents cancer?" "What is the best high-school in the Bay Area?" "How to do Research?"
Why did you write this? What are the limits of your topic (center, periphery, out of scope)? What were your results?
This is the structure of your argument (if you're writing an expository work). "Context, facts, argument, conclusion, appendix" is a sensible place to start. You can elaborate on this basic motif by creating subsections or you could choose some other structure entirely.
Provisional is the key word here. You can and will come back to these later on (possibly to toss them out and start over) so don't try to get them perfect right away. You can add a guess on the results (if you've got one) or leave a space that you'll have to fill in later. Let future-you deal with the mess, they'll have better perspective and more information.
The table of contents, in particular, will be invaluable:
As I write this, I have a second document open. It is structured exactly as this post, but each section is composed of bullet points, each of which is either a topic I want to discuss, or some piece of evidence I should bring forth (mostly quotes). About fifteen of these one-liners become a full section, and I often find myself talking about things that weren't in my notes. Don't skip this step. I can't explain how relieving is to sit down to write and just be able to read what I'm supposed to talk about.
Extracting the discourse
In chapter 20 of How to Read a Book, Adler explains what he calls "syntopic reading". This is the process of extracting the views of different authors on a single topic and mapping out their arguments.
Translate the authors' arguments to a single common terminology. Ideally, you wouldn't adopt any single author's vocabulary to prevent extraneous connotations from leaking in.
Construct a series of questions that, if answered, would summarize an author's position on your subject, then extract the answers from their texts. If an author does not answer the question directly, you are allowed to perform some inference work, but you must not make shit up[9].
Where do different authors disagree? Why? What are the consequences of their disagreements on their overall beliefs? Is there enough common ground to say they are really talking about the same thing[10]?
For Adler, this is contribution enough. Finding the shape of the discussion as it stands, without undue bias or prejudgment is difficult and valuable enough.
Writing a coherent argument
"Writing is so much work, do I have to?" Yes, you do. You don't even need to share your writing to get value out it. Say you're a strong chess player. You may even be a strong blind chess player. But playing chess without a board is so much harder. Reasoning is hard, why would you make things harder for yourself by keeping it all in your head?
Now that you've sit down to write, you'll feel an impulse to try and write well. That impulse is a trap, squash it.
Critic-you interferes with creative-you. I've seen this described as "Babble and Prune" or "doing a vomit pass". Editing prematurely breaks your flow, and inevitably results on a lot of wasted effort when you come back for a second pass on your work. Write badly, and trust future-you to clean up the mess.
Editing
Try to edit from a remove. Wait at least a couple of hours, a day or more if possible. You can't have perspective without distance. You know what you meant by that sentence, you wrote it. Six-months-from-now-you is a total stranger, he doesn't know anything! When it comes to spotting errors, that's a good thing.
On the same token, use spellchecking. Your brain knows what you meant; so after a while it stops showing you the typos.
Reading your writing aloud brings out other kinds of problem.
Finally, a really common advice is to actively seek out feedback. I think that you should seek feedback early or never. Remember that "this is a bad idea, give it up" is possible input. It may even be solid advice and three months into the project you absolutely won't want to hear it. Ask for feedback before sunk costs lock you in. Otherwise? Save everybody some trouble.
Citations
Keep your sources straight. Sources give your reader a way to check your claims. Also, copying someone else's work without attribution is called plagiarism and it's a real dick move. This is important enough that I spent a whole section just setting up the infrastructure. Now it pays off.
There are two things you need to make: a bibliography and a footnote trail. The bibliography is where you put all of your sources together for easy browsing; it is a shopping list for anybody who wants to check your work. Footnotes are where you connect individual ideas or facts with the corresponding source; this way your reader can check one page instead of your entire bibliography.
Ideally, the bibliography would be organized and commentated:
In practice, this standard is not met very often. I've tried to meet it myself, and a welcome side-effect is that when I talk about a book, I now know whether I have to do my absolute best when interpreting it, or I can afford to treat it a bit more loosely.
The following table is from chapter 3 of Eco's How to write a thesis. It tells you what information is necessary when you are citing a text. If you are writing for an academic publication, then there's a citation style you have to stick to, so you can ignore it.
Items marked with asterisks are considered essential. Styling (italics, quotation marks, parenthesis, punctuation) and item order should be preserved. Field names ("edition", "publisher") should not be included in the final citation.
Remember that when you cite a work you are aiming to make it as easy as possible for a reader to get a copy of that source. This is why publisher and place matter; getting in touch with the publisher may be the most straighforward way of obtaining a copy. Full author name, full title, and date of publication (of the current edition) are usually enough for recent titles.
For internet-native documents links are not good enough. Websites change and die, links break. If you are citing an internet-native source, make a private copy and request (or host) a public archive copy (as discussed in s4.1.3). Link to both the original URL and the public archive.
Learning from the community
There's always a community. Even dead disciplines have historians and new fields don't pop out of nowhere. You may have to be creative, however, and look for people handling your subject incidentally. For example, if you are interested in statistics, you'll find common ground with people in marketing.
Bibliographic research will point you to other researchers. Get in touch. Conversely, publish your work so other researchers can find you.
When you get in touch, respect people's time. Read beforehand, and learn the discipline's jargon. Besides showing that you've done your homework, it helps you understand other people, and gives you a tool to evaluate their expertise.
If you share an idea, don't oversell it. If it's a bad idea, convincing someone that it's good makes both of you dumber; you want bad ideas to be unpopular and fizzle out. Also, unsolicited advice is usually unwelcome; don't badger.
I'll repeat my earlier advice on requesting feedback: do it early or never. If you wait until you're committed, then you won't change your mind no matter what feedback you receive. It's a waste of everybody's time.
Open questions and further research
References
Main works
Ancilliary material
NPR.org. Google Entices Job-Searchers with Math Puzzle. 2004. Archived copy at archive.org.
Kazmierczak, Marcus. Google Billboard Problems. 2004, blog post. Archived copy at archive.org.
My girlfriend is currently studying in a different city. We were talking about her coming to visit, but we weren't seeing eye to eye. Eventually we hashed out all of the details of her visit but were still pissed at each other. So we stopped to talk about why we wanted to be together, and reminisce about our first dates, etc. Within ten minutes we were both in tears, and everything was forgiven.
"[...] your brain kind of tricks you into feeling like you've been doing a thing all day. [...] when I was in university there were days I almost certainly felt like "Oh, God, I've studying all day" but what really happened is that I was probably in the library all day which is a very different thing from studying all day." — CGP Grey and Myke Hurley. Cortex podcast ep45. 2017. https://www.relay.fm/cortex/45. 2:40
"The most important thing [for the process of writing] is simply budgeting the time for it. When you get your due date, block in a few hours here and there to sit down and just write. Scheduling is important for three main reasons. First off, you'll be less stressed simply knowing that you have a plan. Two, you're more likely to actually pace yourself and not procrastinate when you follow that plan. And three, [...] multitasking murders your productivity." Blue. How to Read Books and Write Essays. 09:48
"Also note that the author catalog is always more reliable than the subject catalog because the act of compiling it does not depend on the librarian’s interpretation, as is the case with the subject catalog." Eco. How to write a thesis. p55
"[...] querying the subject catalog requires some skill. Clearly we cannot find the entry 'Fall of the Roman Empire' under the letter 'F,' unless we are dealing with a library with a very sophisticated indexing system. We will have to look under 'Roman Empire,' and then under 'Rome,' and then under '(Roman) History.' And if we have retained some preliminary knowledge from primary school, we will have the foresight to consult 'Romulus Augustulus' or 'Augustulus (Romulus),' 'Orestes,' 'Odoacer,' 'Barbarians,' and 'Roman-barbarian (regna).'" — Eco. How to write a thesis. p55
Feynman, Richard P, Ralph Leighton, Edward Hutchings, and Albert R Hibbs. "Surely You’re Joking, Mr. Feynman!": Adventures of a Curious Character, 1985. "A map of the cat"
Wentworth. How To Write Quickly While Maintaining Epistemic Rigor. 2021
"The difference between a coherent argument and a crappy headcanon is evidence. Relativism at its worst is everybody throwing ideas around carelessly, but at its best, it's a rigorous examination of every available idea to determine which ones have ground to stand on. What you end up with isn't the correct answer but one of many valid explanations." Blue. How to Read Books and Write Essays. 08:07
"[...] how can anybody write a thesis [titled 'The Symbol in Contemporary Thought']? One would have to analyze all of the meanings of 'symbol' in all of contemporary culture, list their similarities and differences, determine whether there is an underlying fundamental unitary concept in each author and each theory, and whether the differences nevertheless make the theories in question incompatible." Eco, Umberto. How to Write a Thesis. p11