Take the 2-minute tour ×
Writers Stack Exchange is a question and answer site for authors, editors, reviewers, professional writers, and aspiring writers. It's 100% free, no registration required.

Qualifier/Disclaimer

This may be a very atypical question for this site (of all those I've seen, this question on superuser seems most closely related to mine, but the question was closed as off-topic there), but after reading through the list of all SE communities, I'm pretty sure this is the next best one (after SU) for my question. There may be a better one (maybe TeX & LaTeX?), though, and if you have suggestions for a better place to field this question, I welcome seeing them.

At its essence, I think this question is more about software (to facilitate writing under specific constraints) and less about writing per se, which is why I posted it to SU first, but perhaps someone here has some thoughts. Please pardon the length; it's been criticized as a "life story" question, but I'm not sure how I can pare it down. The length is more due to the detailed description of the very specialized task (which I think would be so abstract as to be meaningless without the specific example of why I want such a tool) than anything else.

The Background

For an important job application, I need to write a single coherent narrative of all my many professional situations over 20+ years, but I am severely constrained in the method of doing so. I'm guessing this is typical of many job applications, so there may be others with a similar question.

This narrative must read cohesively (as if it were written in a single document), but it cannot not be written in a free-form, free-flowing essay like a single document in a single text file. Instead, I am required to do my actual typing in form fields with strictly-enforced character limits. Some of the form fields limit the character counts to 60 characters, others stop at 500, 1,000, or 8,000. All of these various fields are then assembled, building-block manner, by the form software into a single "cohesive" professional history narrative that (based upon the character limits placed upon each form field) has an upper limit of 29,325 characters (about 7 pages in this form). I write cohesive in quotes here because although the software does indeed mash all the pieces together into a single unit, unless I take great care in writing all of the parts, the reader (a person I want to impress) is unlikely to think that the entire unit was written by the same person on the same day. That is, the whole narrative is quite likely to seem disjointed and/or rambling because of the piecewise constraints on how I must write it.

So I have about 50 fields to work with, and most of the fields are supposed to answer one specific question (what was your work like at this job), but some are more comprehensive and of course I'm trying to capture 20+ years worth of varying but related professional history so as to describe the skills and experiences of a single person in a coherent manner. I'd like to be able to use as much of the 29,325 character (7 page) space as possible because, after 20+ years, there's a whole lot to write about and as I approach this task (several rough drafts already), I'm constantly facing decisions on what to leave out for lack of space.

The Question

What application and configuration is most well-suited to this task?

I have experience with GNU Emacs, and what I'm envisioning with this tool is creating ~50 Emacs buffers corresponding to the ~50 fields of the form. Each of these 50 buffers could be configured to give me constantly visible, updated in real time, measures of character counts (as I type) while a 51st buffer would not even be editable but would instead just incorporate the contents of each of the others. This would let me have constant continuous feedback about my character count and limit for each buffer but would also let me read the entirety as a single document (even as I type).

In a sense, I'm already doing something like what I described above with Emacs, but the time lag between writing something (into the web app containing the job application) and seeing the entirety (by printing the entire application as a PDF) is minutes to hours, so this workflow process is very cumbersome and time-consuming and I can't help thinking there must be a better way. Maybe with some macro magic, I could do something like what I described with Emacs, but I thought I'd ask if there was a tool that already did something like what I'm thinking of here.

My main goal is to be able to constantly keep track of individual field character counts (with respect to their maximum limits) while simultaneously being able to read the entire narrative as a whole.

I realize this is a subjective question, with no single objective answer, but I've tried to craft it in accordance with the guidelines for good subjective Q&A, and I think it is definitively (if not objectively) answerable.

Product Idea?

If there's nothing that anyone can think of that facilitates this kind of writing, it seems to me like there might be a product opportunity here. I'm not a professional developer so I don't imagine I could do it myself in a reasonable amount of time, but I bet there would be a fairly big market for a tool like this. Whether conscious of it or not, people are constantly doing this task anytime they are applying for a new job.

share|improve this question
1  
I do not have an answer for you, but I think you are overshooting your aim. These people are not stupid. They know how their forms look like, because they made it that way on purpose. So there is no need that it reads cohesively. Keep it short and interesting. You can tell your whole story if you have attracted their attention. Honestly, if you did X for five years at the beginning of your career and mostly have done Y and Z the following 15 years, do you really think that you are still such an expert in X that you have to tell them in detail about it? Or would be "done X for 5 years" enough? –  John Smithers May 27 '13 at 18:56
    
Thanks for your feedback @JohnSmithers. I'll certainly keep that in mind. –  TeXnewbie May 27 '13 at 19:01
    
My best bet: Fill all the fields with placeholders, [FIELD-1-80chars], [FIELD-2-3000chars], then obtain the output of that, and then use any common text editor to fill the blanks in with text that makes the whole thing appear as a common narrative. Then extract from the document what you filled in, and put it in proper form fields. There is no way to get the result look correctly if you don't know how your data is formatted exactly. –  SF. Nov 8 '13 at 13:41
add comment

2 Answers

up vote 2 down vote accepted

The operating system you are using is probably going to limit your options to some extent or other.

If you are using MacOS or Windows I would highly recommend Scrivener.

You could create a blank project with a single "card" for each of your 50 fields - Scrivener provides a live word and character count for content as you type and has numerous options for automatic backup and structuring your work.

share|improve this answer
    
Thank you very much. I'm trying out Scrivener now. It looks like it may have some promise. What I like the most thus far is, "The contents of the Draft folder represent the text fragments that will be compiled into one long document when you export or print using File > Compile…, which is the standard way of preparing your finished project for printing or final formatting in a dedicated word processor. This is very much the raison d’être of Scrivener - to assemble the text of your manuscript in the Draft folder for printing or export." –  TeXnewbie May 27 '13 at 19:02
    
Scrivener is a perfect match for my need. Wonderful! Totally new concept in an application for me, and it looks like it will have very long-lasting utility in my life for myriad tasks, not just this one. I cannot thank you enough. My only regret (though very small) is that it's not GNU/GPL or OSI software though perhaps I'll find an alternative eventually. Meanwhile, Scrivener absolutely fits the bill for me. –  TeXnewbie May 28 '13 at 5:15
add comment

The general approach you are required to take is called "topic-based writing". It's a controversial field and there are mountains of material online about it.

The most well-known tool is an XML specification called DITA. DITA is supported by numerous applications. I recommend using oXygen Author.

Since you have already been given a tool to work with, the main issue is how to write a cohesive narrative that is assembled from different parts. For that I'd recommended reading a document called "STOP", which was written by Hughes Aircraft in the sixties.

STOP provides a method on how to prepare a convincing argument that is assembled from much smaller pieces that could even have been prepared by different teams.

https://github.com/johngtait/ditabook/blob/master/STOP_Original%20Report.pdf

share|improve this answer
    
It's both natural and yet also kind-of mind-boggling to me that people have been thinking about how to do such things for almost 50 years. Though I've only skimmed it thus far, STOP looks like a terrific read and very valuable. oXygen Author also looks very powerful though I've only just glanced at it so far whereas I spent many hours working with Scrivener. Thanks very much! –  TeXnewbie May 28 '13 at 5:17
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.