Although it certainly can be used otherwise, a progress tracking system like the one Paul Silvia suggests in his book How to Write a Lot seems to work best for writing that can be open ended: by following a regular writing schedule, projects can regularly and reliably come to completion. What happens, however, if one is working under a deadline (be it self-imposed or not) and, therefore, needs to develop a writing schedule backwards from this due date?
This spreadsheet is at least an elementary attempt to provide a tool for performing such a task. Yet, one obvious limitation of this spreadsheet method is that all the writing projects are arranged serially along the completion timeline rather than allowing for working on more than one project at once.
If anyone else should find this tool useful and has refinement suggestions, I would be very interested in seeing them. These formulae appear to work on Google Docs exactly as they do on Excel when that program is operated on a Windows platform, but to my understanding, Excel calculates dates differently on Mac OS than it does on Windows, so Mac users may need to adjust this spreadsheet’s formulae.
In How to Write a Lot, reviewed in the previous post, Paul Silvia provides his own progress monitoring system as an example (39–45). Since finishing the book last month, I have been adapting Silvia’s database format to a Google Docs spreadsheet that will track some additional data in addition to the data that he finds helpful. Since it has been helpful thus far, I thought I would make the blank spreadsheet available (with just enough dummy data to give the formulae included some substance) as well as the one below with some sample data.
[scribd id=16494778 key=key-1anv54cgp3e2av7ippp2]
Some Additional Details Column E: I am working on estimating the average number of words that I write in an hour (including time for research), and thus far 175 seems fairly close, hence that value running down the E column. Behind this number is actually the formula =350/2—for an average of 350 words on one of my standard pages (including footnotes) and an estimated 2 hours for writing that page, though I have a sense that something like 2.25 to 2.5 might be more accurate.
Column F: An overall daily goal calculated based on =[Column D]*[Column E].
Column G: The results of a word count (including footnotes) at the beginning of the day. As the spreadsheet above shows, however, I did not start tracking beginning and ending word counts until May 29.
Column H: The results of a word count (including footnotes) at the end of the day.
Column I: A daily progress total based on =[Column H]-[Column G]. Cell I2 computes the average daily progress.
Column K: A daily progress measure against the daily goal based on =[Column I]/[Column F]. Cell K2 computes the average amount of the daily goal that is actually met each day.
Column J: The cells for each work day use the formula =IF([Column K]>=1,1,0). If a given daily goal is met, Column K = 1, or if it is exceeded, Column K > 1. In either case, this formula returns the binary value 1 (= Yes). Alternatively, if the daily goal is not met, the formula returns the binary value 0 (= No). Cell J2 then averages the values in Column J to determine the portion of the work days that meet the daily writing goal. The significant disparity between Column J and Column K appears because, as would be expected, some days have been more research intensive and other days have seen more writing.
Column L: Column L indexes how much “life happening” has affected the actual writing progress made versus the progress that was planned. A negative number indicates the number of planned writing hours that were spend on some other task(s), and a positive number would indicate additional, unplanned time devoted to writing. Cell L2 provides the total number of writing hours that actually happened over or under the planned number of writing hours.
If something like this spreadsheet seems like it would be helpful, a nearly blank version, again, is also available. If others have similar tools or methods that they have found valuable for research progress tracking and management, I am sure readers would find those helpful as well.
Paul J. Silvia teaches psychology at the University of North Carolina, Greensboro. In How to Write a Lot: A Practical Guide to Productive Academic Writing, Silvia chiefly pleads with his readers to set aside specific, regular blocks of time for writing and to adhere steadfastly to this schedule (16–17). “The secret,” he says, “is the regularity, not the number of days or the number of hours [allotted for writing]” (13). Silvia argues that observing such a regular writing schedule will allow an author to produce better material more efficiently (1). “More efficiently” does not, of course, necessarily indicate that all academics should publish a large quantity of material; those whose interests lie elsewhere can still use a regular writing schedule to produce the quantity of literature that they wish. Thus, Silvia suggests that a more accurate title for the volume would be How to Write More Productively During the Normal Work Week with Less Anxiety and Guilt, but he humorously recognizes that such a title may well have inhibited book sales (130).
To motivate his readers to take his advice about writing schedules, Silvia addresses four common barriers to productive writing and regular writing times (11–27). First, Silvia addresses the difficulty of finding large blocks of time to write by asking his audience to consider writing to be part of the set of required tasks that academics have. “Do you need to ‘find time to teach’?” he queries, “Of course not—you have a teaching schedule, and you never miss it. . . . Instead of finding time to write, allot time to write” (12). Second, Silvia cautions against the literary paralysis that can result from a constant feeling of needing to read more about a topic before writing about it. Doing this reading during one’s scheduled writing time can eliminate the roadblock it presents to the writing process (18–19). Third, perceived workspace or equipment inadequacies cannot be allowed to be deterrents from writing (19–23). Fourth, waiting for inspiration or “feeling like writing,” at least for those who do not intend to produce novels or poetry, should not dissuade someone from a regular schedule because keeping that schedule will itself generally prompt more ideas for writing and more occasions when an author feels like writing (23–27).
After attempting to dispatch these common roadblocks to productive writing, Silvia suggests some “motivational tools,” including: setting reasonable goals to achieve within one’s regular writing times, prioritizing different projects appropriately, and monitoring one’s progress (30–45). He also comments at length on starting and running a writing accountability group (49–57).
Silvia briefly discusses some characteristics of good writing style (59–76) before giving specific counsel for writing journal articles (77–107) and books (109–25). For journal articles, Silvia provides numerous specific tips (78–98)—some of which specifically relate to his own field of psychology but may still apply to articles submitted in New Testament studies—and a general counsel: Assume that any article submitted will be rejected (98). Silvia intends this counsel to calm fears about “what if. . . ,” and he encourages his readers to think of article rejections as a “publication tax,” or a cost that must be payed to have other things published (100–101). For books, Silvia suggests finding a co-author if necessary (112–13), and he provides some tips for authors when they want to “sell” their books to publishers (118–23).
While Silvia’s book contains numerous, practical hints for various issues that arise during the writing process, the book has a unified message: “Make a writing schedule, keep it, and you will write more than you do.” The “plan and persist” mantra is, perhaps, somewhat oversimplified at times, but this simplicity too serves Silvia’s purpose. How to Write a Lot: A Practical Guide to Productive Academic Writing, in the end, does “guide,” but this guidance is designed also to motivate.
Looking at beginning the dissertation phase here at Southeastern later this year, I found Silvia’s book encouraging, but perhaps more encouraging is a very simple writing schedule. If someone were only to average one page each week day, that person would write about 261 pages each year. At about 350 words per page, our hypothetical student would write in one year 91,350 words on a project where something around 100,000 words seems to be a fairly standard finishing length. Others who have already walked this road will certainly have a more nuanced perspective, but at the beginning of the road at least, such things are encouraging.
The next revision of the Theological Writing Handout is now available, and it can be previewed and downloaded below. As always, comments identifying errors or suggesting improvements are welcome. For anyone who may be interested, a change log from the previous version (0.4.1) is also available.
Scott Crider teaches in the English Department at the University of Dallas. His book, The Office of Assertion: An Art of Rhetoric for the Academic Essay, is intended to provide an introduction to “the classical art of rhetoric and composition” (xi). While providing this introduction, Crider specifically seeks to argue that rhetoric is, as a liberal art, a noble pursuit and to improve the readers ability to write academic prose (2).
The introduction defends a distinction between rhetoric and sophistry, between “persuasion aimed at the truth . . . and persuasion aimed only at the appearance of truth” (4; cf. 119). Following Aristotle, Crider affirms that rhetoric is not primarily formulaic, although it does involve certain formulas; instead, rhetoric is primarily a mental faculty (5–7). Having truth as its goal, fully formed rhetoric “in its finest and fullest manifestation is a form of love” (12). In addition to discovering means for persuading an audience toward truth, the rhetorical faculty carefully attends to what arguments will function best in a given situation (7–9; cf. 59).
Rhetoric begins with invention, some conception of an argument, and invention commonly has five topics: definition, comparison, relationship, circumstance, and testimony (29). Once the rhetor has refined an argument well enough to have a coherent thesis, the rhetor can use these topics to chart a course toward demonstrating the thesis (30). The additional, subsidiary arguments and the manner in which they are drawn together toward the thesis are best organized according to an “immanent design,” or an arrangement that arises from the arguments themselves rather than one that is simply imposed from without (e.g., the five-paragraph essay form; 43–47).
Even if written to people who have similar interests, an argument’s introduction should convince its audience that the argument is worth reading (49). This introduction calls for a certain degree of creativity to find some way of painting the argument’s substance in a way that will please and intrigue the audience; if a rhetor succeeds in this task, the audience will be more willing to spend the time and effort to ponder the argument proper (53). The introduction should also briefly outline the essential contours of the argument that the rhetor intends to prosecute; doing so aids the argument’s rhetoric by providing the audience a concrete set of expectations, which the rhetor can attempt to meet (55–56). Along the way to meeting these expectations, the rhetor should consider and account for possible counter-arguments (59): What weaknesses in the argument do these potential contraventions suggest? How can these weaknesses best be remedied? After prosecuting the argument, the rhetor should briefly conclude (61–62). Conclusions frequently summarize; they may also suggest additional implications that the central argument has, emotionally move the audience, or return to a theme or idea included in the introduction (62–63).
Throughout the introduction, argument, and conclusion, the rhetor is also constrained to use an appropriate style of language because an inappropriate style will hamper the audience’s reception of the argument (73–74, 77–78, 84). Particularly apt for academic writing is a kind of “middle style” that steers a middle course between the colloquialism of conversational language and the elevation of highly stylized discourse (74–77). This middle style includes conventions about word choice, sentence construction, figures of speech, and formatting (79–104). Together, a rhetor’s use of these elements suggest certain things about that rhetor and give the audience a certain picture of who the rhetor is—a picture that may aid or inhibit the rhetor’s persuasive task.
Once constructed, an academic writing needs a second look that does more than seek opportunities to make editorial changes (109). The writing needs to be evaluated in terms of the degree to which it fulfills its required objectives, the sharpness of its focus, the clarity of its thesis, the development of its logic, and the completeness of its explanations, and the piece should be revised accordingly (110). Such revision allows a rhetor to enhance the craftsmanship that the argument exhibits and the argument’s ability to move its audience toward truth (118).
Given Crider’s stated purpose to provide an introduction to rhetoric for the academic essay, The Office of Assertion is a helpful, concise, and in its own way, pleasant book. At various points, some readers might wish for more specifics or more direct instruction, but on Crider’s conception of rhetoric as primarily a faculty of the mind rather than a set of independent techniques, the book strikes a nice balance between generality and specificity. Crider seeks not so much to show his readers directly how to write good, academic essays as to show them how to think—how to have the kind of mind that produces good, academic essays. Style is a component of this larger package, but mere mechanical observation of grammatical or stylistic “rules” can, quite possibly, fail to induce other elements of good essays, like invention and organization. By contrast, a rhetorically-trained mind naturally seeks out effective style. Thus, Crider’s book and the relationship that he advocates between rhetoric, academic writing, and style have much to commend them as aids toward delightfully introducing oneself and one’s audience to truth.
Each Tuesday morning, he would close his study door and sit down to write the “Notes and Comment” page for The New Yorker. The task was familiar to him—he was required to file a few hundred words of editorial or personal commentary on some topic in or out of the news that week—but the sounds of his typewriter from his room came in hesitant bursts, with long silences in between. Hours went by. . . . When the copy went off at last, in the afternoon RFD [Rural Free Delivery] pouch—we were in Main, a day’s mail away from New York—he rarely seemed satisfied. “It isn’t good enough,” he said sometimes. “I wish it were better” (ix).
Striking is the fact that someone like White should wrestle so much and so frequently with composing these weekly essays, which were, admittedly, of a rather different cast than an academic paper or monograph on the New Testament. Still, there is a pattern of attention here to the craftsmanship involved in composing such an essay that we New Testament students would also do well to observe. Arguments about this or that interpretive point must surely be sound, but sound arguments presented winsomely should quite easily repay the additional efforts required to compose them. To borrow some biblical phrases, good, academic writing (much like good, academic presentations) combines “words of truth” with “words of delight” (Eccl 12:10).
The Greek font that the Society of Biblical Literature has been developing is now complete and available for download. Downloading and usage are free for non-commercial projects, but the font itself is not open-source. A list of open-source Greek fonts is available, however, as well as instructions for installing and using any of these unicode fonts under Windows, Mac, and Ubuntu.
For assistance with the SBL Greek and Hebrew fonts, you can also check the SBL font forum or email font support.