raganwald
(This is a snapshot of my old weblog. New posts and selected republished essays can be found at raganwald.com.)

Friday, February 09, 2007
  Off Topic: Eliding Raganwald


My editing “policy”:

(Please imagine me making those oh-so-last-century quote marks with my fingers as I say the word policy.)

I deliberately post as soon as I think an idea is finished enough to communicate the gist. Then, as time and inclination allow, I polish my posts. Sometimes readers provide some excellent feedback, and that gets worked in as well. To me, this reworking is a benefit of the medium. If you read and re-read my posts, especially in the first seventy-two hours, you’ll see the changes.

So far, this is probably not contentious. However, there is a prevailing style amongst bloggers to mark their edits, perhaps by striking out words they have elided.

update: Or by noting that new words are, well, new.

There are good reasons for that style. The primary place where people insist on it is when there’s some emotionally charged conversation, and someone retracts something they’ve said. The idea seems to be that if you just delete wrong words, you’re pretending you never said them, which is somehow hypocritical and reprehensible.

I do not subscribe to this view, and I do not hold others to it. My intent with my writing is to present as coherent a view as possible. Vast tracts of strikeout and insertions can degrade a post.

That being said, you will find stricken words and updates scattered throughout the site. I use this style when I am trying to portray a thought process. For example, I recently described an unexpected behaviour and admitted I didn’t know what was going on, although I speculated as to what might be causing the behaviour. A reader managed to explain the behaviour in a comment. I struck out my original words and added an explanation. That particular post was about unexpected behaviours, so showing the process of going from not knowing what was going on to having someone else explain it added value to the post.

Nevertheless, there is no overarching consistent policy around edits. If recording my words exactly as I originally said them is important, someone ought to donate more funding to the wayback machine so that it can achieve a finer granularity of archiving.

Is this a disclaimer?

Of a sorts. I fully expect that sooner or later someone is going to write an angry comment saying that I changed my words and didn’t keep the originals around as a scarlet letter of shame. Knowing my (bad) habit of writing emotional posts before I’ve had my third coffee, it’s inevitable that I’ll write something I’ll regret enough to retract.

I don’t expect that writing this will get me off the hook when that happens. I’m not saying to you, “no fair criticizing me for doing this, it’s in the fine print.” I’m writing this to explain, not to mitigate.

Ok, thanks for your patience with this wildly off-topic post. Time for my second coffee and to return to working with a team of programmers a cut above JavaSchools idiots mediocrity certification-happy and buzzword-driven programmers the rest.

;-)
 

Comments on “Off Topic: Eliding Raganwald:
For those of us not regularly following the discussion on your site, the hardest part is having old posts pop up in Bloglines over and over again. I can never tell what's changed. It'd be nice if there were diffs.
 
Thanks for the feedback.

Hmm, that's tough! You can tell Bloglines not to show you updates, but then you don't get updates!, and maybe you want to know when an article changes.

I would like it best if bloglines did the diffing. I respect what you want when you are re-reading a post, but think of the new reader who hasn't read the earlier version.

Helloooo, feed reader authors! Feature request!!
 
I like your policy - perhaps because I follow a similar policy myself :-) As you say, clarity of the end result is important.
 
Relevant here is the relationship between blogs and wikis. Every now and then I (and surely others) catch glimpses of a deep relationship between the two formats.

Blogs make it easy to start a conversation and to go back and forth a bit. Once a synthesis is reached it calls to be summarized and placed in a wiki under version control.

Eventually the tools will catch up. The crucial need is for later readers to be able to retrace the history of a conversation using permalinks.
 
There's a whole world of work that aggregators can do to answer the question, "What's changed since I last checked?" After we solve that problem, maybe we can move on to eliminating procrastination.
 




<< Home
Reg Braithwaite


Recent Writing
Homoiconic Technical Writing / raganwald.posterous.com

Books
What I‘ve Learned From Failure / Kestrels, Quirky Birds, and Hopeless Egocentricity

Share
rewrite_rails / andand / unfold.rb / string_to_proc.rb / dsl_and_let.rb / comprehension.rb / lazy_lists.rb

Beauty
IS-STRICTLY-EQUIVALENT-TO-A / Spaghetti-Western Coding / Golf is a good program spoiled / Programming conventions as signals / Not all functions should be object methods

The Not So Big Software Design / Writing programs for people to read / Why Why Functional Programming Matters Matters / But Y would I want to do a thing like this?

Work
The single most important thing you must do to improve your programming career / The Naïve Approach to Hiring People / No Disrespect / Take control of your interview / Three tips for getting a job through a recruiter / My favourite interview question

Management
Exception Handling in Software Development / What if powerful languages and idioms only work for small teams? / Bricks / Which theory fits the evidence? / Still failing, still learning / What I’ve learned from failure

Notation
The unary ampersand in Ruby / (1..100).inject(&:+) / The challenge of teaching yourself a programming language / The significance of the meta-circular interpreter / Block-Structured Javascript / Haskell, Ruby and Infinity / Closures and Higher-Order Functions

Opinion
Why Apple is more expensive than Amazon / Why we are the biggest obstacles to our own growth / Is software the documentation of business process mistakes? / We have lost control of the apparatus / What I’ve Learned From Sales I, II, III

Whimsey
The Narcissism of Small Code Differences / Billy Martin’s Technique for Managing his Manager / Three stories about The Tao / Programming Language Stories / Why You Need a Degree to Work For BigCo

History
06/04 / 07/04 / 08/04 / 09/04 / 10/04 / 11/04 / 12/04 / 01/05 / 02/05 / 03/05 / 04/05 / 06/05 / 07/05 / 08/05 / 09/05 / 10/05 / 11/05 / 01/06 / 02/06 / 03/06 / 04/06 / 05/06 / 06/06 / 07/06 / 08/06 / 09/06 / 10/06 / 11/06 / 12/06 / 01/07 / 02/07 / 03/07 / 04/07 / 05/07 / 06/07 / 07/07 / 08/07 / 09/07 / 10/07 / 11/07 / 12/07 / 01/08 / 02/08 / 03/08 / 04/08 / 05/08 / 06/08 / 07/08 /