Giving concrete examples is something Feynman talked about a lot too. It is easy to talk abstractly about anything but in the end, something real and relatable must exist. When I deal with enterprise software, I prod the sales guys to tell me what the feature really means and does. Sure, it will streamline the sales order approval process but what does that entail? Outlook add ons? Browser popups? Notifications over SMS? Excel reports? Or 12 different screens that users have to click refresh on all day? My users will interact with something in the end. Show me the screenshots of all that already.
When I write business software, I dig in for details with my users in the same way. I understand you want me to fix the document printing process. Unfortunately that is too vague to write code for. Let's find out exactly what it is that needs fixing. Usually after some digging in, I change a button or two and it is now fixed!
It is hard work to be exact, precise, and specific. Being general is too easy.
I used to write papers in a fractal form. A short one would go like:
In my opinion, A is true. A is true for at least three reasons: B, C, and D.
B is true for at least three reasons. First, E. Second, F. Third, G. Therefore, B is true.
C is true for at least three reasons...
D is true for at least three reasons...
In conclusion, A is true.
If I wanted a longer paper, there would be subparagraphs under B, C, and D, in the same form. For my thesis, each of those subparagraphs got sub-subparagraphs. You can guess what I would do if I ever wrote a book.
It seems to me that, in my opinion, as to all practical intents and purposes, it's arguable that what you meant to say was something along the lines of, "Your post seems to be no more than 113 words in length; I have no choice but to assign you a grade of 'D'."
Reminds me of the most wondrous, but little known, feature in word perfect for windows 3.1 - the "make my paper one page longer" button. That button saved me hours in college. I've often wondered how it came to be - talk about listening to your customers!
There was literally a button that said, "add one page" or something like that. I assume it changed line height or margins in some subtle way, but it was magic at midnight the day before your eight page paper was due, and you only had seven pages.
Though [edit] the titles are a good summary of the article [/edit] (as per "slip out of abstraction") the examples given are humorous, thorough, and help in really getting the point being made.
It's interesting to consider how the author's (sometimes verbose) sentences could be shortened. If writing for pure conciseness, what would you cut out? Which parts are completely necessary? Are the rephrasings necessary to convey the different aspects of the current point? Is the example given important enough to stay?
"Pat expressions are hard, often impossible, to avoid, because they come too easily to be noticed and seem too necessary to be dispensed with."
=> "Pat expressions cannot always be avoided."
"A writer's work is a constant struggle to get the right word in the right place, to find that particular word that will convey his meaning exactly, that will persuade the reader or soothe him or startle or amuse him."
=> "Each situation calls for a certain word with a certain connotation; the writer toils to find it."
Again, there's no problem -- it's excellent writing, it just struck me that word golf could be as interesting as code golf. What is the shortest possible phrasing to express this exact idea? (I suppose we're doing it all the time, except in English classes where word count is the goal.)
Slang adjectives like cool ("That's real cool") tend to explode all over the language. They are applied to everything, lose their original force, and quickly die.
I've often marveled at cool's longevity -- unlike the adjective sick (popular briefly in my social circle in 2005) which seems to have died out almost entirely.
Perhaps only semi-related, but can anybody tell me how scientific journal writing fell into almost universal use of the passive voice? It drives me nuts every time I read that some more assumptions will be validated or that something else will be proven.
Which is to say, every single time I read an academic article.
It's to make what was done (which is important to the paper) seem important and make who did it (which is less important to the paper) seem unimportant.
The interesting thing to me is that in mathematics journals, the universal pronoun is "we." The reason (I've been told) is that "we" represents the collaboration of the author and the reader to understand the results and proofs in the paper. This makes sense to me, because reading and writing mathematics is a skill entirely apart from most other types of discourse. (Of course, when I say "mathematics," I mean to include fields like theoretical computer science and others in which discourse is of the "theorem, proof, discussion" form.)
That is interesting. I instinctively use "we" when commenting code or talking myself through performing a novel task, in both cases for the same reason.
It projects an air of lack of involvement and therefore neutrality/lack of bias?
People will often fall back to passive voice (and other linguistic acrobatics) when they don't want seem like they're weighing in one way or another. For example, accident reports will sometimes go on with something like "Braking maneuver attempted without success".
Novels are written to enable immersion and focus on the actors (protagonist); academic articles are written to be clear and neutral and focus on the subject matter.
Hence "I realized I loved her" and "the solution was lightly stirred for 10 minutes".
At least he assigned a word deadline and not a page deadline. I wish schools would let you get feedback on an essay from the teacher and then hand it in again. Revision is not emphasized.
Revision was always emphasized to me, but I never understood why. I always thought I was above it. After I became a programmer and had to look at old code I’d written, I finally understood why revision is so important.
Couldn’t my teachers have told me that revision is so important because we’re not qualified to evaluate our creations until they’re no longer fresh in our heads? It’s not an obvious concept, and I wish others didn’t have to learn it the hard way.
"All subjects, except sex, are dull until somebody makes them interesting."
Certainly, sex can be dull. Unfortunately, going into the specific anecdotes concerning the topic would make HN less work-safe and also damage the modesty thereof.
When I write business software, I dig in for details with my users in the same way. I understand you want me to fix the document printing process. Unfortunately that is too vague to write code for. Let's find out exactly what it is that needs fixing. Usually after some digging in, I change a button or two and it is now fixed!
It is hard work to be exact, precise, and specific. Being general is too easy.