Google Docs: A New Hope

I suspect the Google Docs grammar bot is the least useful bot there is. After hundreds of suggestions, I can think of only one instance in which it was right. Is its failure rate so high because it learns from how other people use English, instead of drawing from a basic ruleset?

I’m not saying my grammar is better than everyone else’s but if the bot is learning from how non-native users of the English language construct their sentences, I can see how it would make the suggestions it does, especially about the use of commas and singular/plural referents.

Then again, what I see as failure might be entirely invisible to someone not familiar with, or even interested in, punctuation pedantry. This is where Google Docs’s bot presents an interesting opportunity.

The rules of grammar and punctuation exist to assist the construction and inference of meaning, not to railroad them. However, this definition doesn’t say whether good grammar is simply what most people use and are familiar with or what is derived from a foundational set of rules and guidelines.

Thanks to colonialism, imperialism and industrialism, English has become the world’s official language, but thanks to their inherent political structures, English is also the language of the elite in postcolonial societies that exhibit significant economic inequality.

So those who wield English ‘properly’ – by deploying the rules of grammar and punctuation the way they’re ‘supposed’ to – are also those who have been able to afford a good education. Ergo, deferring to the fundamental ruleset is to flaunt one’s class privilege, and to expect others to do so could play out as a form of linguistic subjugation (think The New Yorker).

On the other hand, the problem with the populist ontology is that it encourages everyone to develop their own styles and patterns based on what they’ve read – after all, there is no one corpus of popular literature – that are very weakly guided by the same logic, if they’re guided by any logic at all. This could render individual pieces difficult to read (or edit).

Now, a question automatically arises: So what? What does each piece employing a different grammar and punctuation style matter as long as you understand what the author is saying? The answer, to me at least, depends on how the piece is going to find itself in the public domain and who is going to read it.

For example, I don’t think anyone would notice if I published such erratic pieces on my blog (although I don’t) – but people will if such pieces show up in a newspaper or a magazine, because newsrooms enforce certain grammatical styles for consistency. Such consistency ensures that:

  1. Insofar as grammar must assist inference, consistent patterns ensure a regular reader is familiar with the purpose the publication’s styleguide serves in the construction of sentences and paragraphs, which in turn renders the symbols more useful and invisible at the same time;
  2. The writers, while bringing to bear their own writing styles and voices, still use a ‘minimum common’ style unique to and associated with the publication (and which could ease decision-making for some writers); and
  3. The publication can reduce the amount of resources expended to train each new member of its copy-editing team

Indeed, I imagine grammatical consistency matters to any professional publication because of the implicit superiority of perfect evenness. But where it gets over the top and unbearable is when its purpose is forgotten, or when it is effected as a display of awareness of, or affiliation to, some elite colonial practice.

Now, while we can agree that the populist definition is less problematic on average, we must also be able to recognise that the use of a ‘minimum common’ remains a good idea if only to protect against the complete dilution of grammatical rules with time. For example, despite the frequency with which it is abused, the comma still serves at least one specific purpose: to demarcate clauses.

In this regard, the Google Docs bot could help streamline the chaos. According to the service’s support documentation, the bot learns its spelling instead of banking exclusively on a dictionary; it’s not hard to extrapolate this behaviour to grammar and syntactic rules as well.

Further, every time you reject the bot’s suggested change, the doc displays the following message: “Thanks for submitting feedback! The suggestion has been automatically ignored.” This isn’t sufficient evidence to conclude that the bot doesn’t learn. For one, the doc doesn’t display a similar message when a suggestion is accepted. For another, Google tracks the following parameters when you’re editing a doc:

customer-type, customer-id, customer-name, storageProvider, isOwner, editable, commentable, isAnonymousUser, offlineOptedIn, serviceWorkerControlled, zoomFactor, wasZoomed, docLocale, locale, docsErrorFatal, isIntegrated, companion-guest-Keep-status, companion-guest-Keep-buildLabel, companion-guest-Tasks-status, companion-guest-Tasks-buildLabel, companion-guest-Calendar-status, companion-guest-Calendar-buildLabel, companion-expanded, companion-overlaying-host-content, spellGrammar, spellGrammarDetails, spellGrammarGroup, spellGrammarFingerprint

Of them, spellGrammar is set to true and I assume spellGrammarFingerprint corresponds to a unique ID.

So assuming further that it learns through individual feedback, the bot must be assimilating a dataset in the background within whose rows and columns an ‘average modal pattern’ could be taking shape. As more and more users accept or reject its suggestions, the mode could become correspondingly more significant and form more of the basis for the bot’s future suggestions.

There are three problems, however.

First, if individual preferences have diverged to such an extent as to disfavour the formation of a single most significant modal style, the bot is unlikely to become useful in a reasonable amount of time or unless it combines user feedback with the preexisting rules of grammar and composition.

Second, Google could have designed each bot to personalise its suggestions according to each account-holder’s writing behaviour. This is quite possible because the more the bot is perceived to be helpful, the likelier its suggestions are to be accepted, and the likelier the user is to continue using Google Docs to compose their pieces.

However, I doubt the bot I encounter on my account is learning from my feedback alone, and it gives me… hope?

Third: if the bot learns only spelling but not grammar and punctuation use, it would be – as I first suspected – the least useful bot there is.

Hacking newsroom productivity

Note: The name of this blog has changed from Gaplogs to edmx. This is why.

There are lots of parallels between software teams and newsrooms, their respective ideal workflows and desirable work environments. However, journalism is decidedly more human – considering that’s the species whose stories the profession is engaged in retelling – and journalistic offices wouldn’t entirely benefit from modelling themselves on tech rooms that strive to minimise ‘distractions’ and, more generally, human contact. Nonetheless, this doesn’t mean everyone should be forced to work in an environment that the majority finds comfortable. I’m writing this now because I stumbled upon an ancient piece in GeekWire about how open floor plans are bad for developers because they “don’t want to overhear conversations”.

“Facebook’s campus in Silicon Valley is an 8-acre open room, and Facebook was very pleased with itself for building what it thought was this amazing place for developers,” [StackOverflow CEO Joel] Spolsky said in an interview with GeekWire co-founder Todd Bishop. “But developers don’t want to overhear conversations. That’s ideal for a trading floor, but developers need to concentrate, to go to a chatroom and ask questions and get the answers later. Facebook is paying 40-50 percent more than other places, which is usually a sign developers don’t want to work there.”

 

Spolsky, who in 2011 created project-management software Trello, said the “Joel Test” that he created 16 years ago is still a valid way for developers to evaluate prospective employers. It’s a list of 12 yes-no questions, with one point given for every “yes” answer. “The truth is that most software organizations are running with a score of 2 or 3, and they need serious help, because companies like Microsoft run at 12 full-time,” Spolsky said when he created the test. He said that remains true today.

This is true of writers – whether you’re hammering out a 1,000-word copy on medical ethics or writing the next Dune – as well as copy-editors. Both writing and editing are benefited when you’re able to concentrate, and neither loses out when you’re unable to talk about what you’re doing when you’re in the middle of it.

But at the same time, newsrooms also need to encourage collaborations, such as between writers, editors, multimedia producers, social media managers, marketing, tech, etc.

This is why I think an ideal newsroom would be an open floor where those who want to work together can do so while the company allows those engaged in solo projects to work from home. Of course, this assumes everyone knows what they want to do, what they want to work on and that it plays down the admittedly incredible value of overhearing two people talk about something and realising you’ve got an idea about that. The inspiration for stories can come from everywhere, after all. It’s just that it might be time to start evaluating, and implementing, these things more systematically. For example, how often do we stumble upon story ideas? Is it a feature that editors deliberately try to work into newsrooms? Under what conditions does it manifest? And can better technology help?

This is because not everyone in a newsroom can work remotely – but every newsroom is likely to have someone who will benefit from being able to, whether temporarily or permanently. Moreover, ‘new media’ newsroom workflows have largely calcified, which means developers today have a greater incentive than before to build integrated/symbiotic newsroom tools with potentially industry-wide adoption. So at this juncture, they should consider collaborative tools for journalists that also make remote-working more efficient and less prone to communication gaps because, as technology promises to offer more solutions to better journalism, its choices will increasingly affect how journalists can or can’t work.

To be clear, the answers could lie in many spheres, could manifest in many forms – just that I’m particularly curious about whether technology has any of them. Because if it does, I can think of at least two major challenges.

Collaboration tools

For a developer, ‘communication pains’ can arise in at least three contexts (I don’t presume to know all of them): when brainstorming, when collaborating and when receiving feedback. For a journalist, there are two corresponding contexts: when brainstorming and when editing (collaborating to create an article seldom happens when the writers are working remotely). Here, the developer has the advantage because her ‘language’ affords shorter paths to truths. It has fewer syntactic rules, the syntax and semantics are strongly connected and the truths that need to be realised are very well-defined. For a journalist working with a natural language, things are more fluid and open to negotiation. The result is that it’s easier for developers to work remotely because building something good together requires a tool that is highly process-oriented and has perfect version control.

(Could one way out be something like the Hemingway app? It lets writers see what could be wrong with their writing by highlighting difficult sentences, the use of passive voice, adverbs, etc. Maybe. Such an app could definitely go a long way in improving bad writing and making it readable – which would be a boon for editors because they can then focus on making more creative kinds of improvements. But until the app is able to discern narrative techniques and styles, it won’t be able to run the last mile, which means you’ve still got an editor working mano y mano with whom is going to be better for everyone.)

Communication tools

None of Skype, Slack, Hangouts, etc. can cut it when it comes to realising perfect communication options for the remote-worker because the barrier they pose isn’t through a built-in function but concerns the user herself. She still has to want to open the app and dial/ping/buzz/whatever. On the other hand, it’s always been easier to just open your mouth and start talking. Moreover, chat-apps like Slack and Hangouts passively discourage users to reply immediately. In one-on-one communication, when someone talks to you, you’re expected to reply then and there if and when you can. This immediacy is very convenient and useful. However, when chatting with your friend, the app maintains an archive of past messages that your friend can return to later. It’s also quite tricky for you to force a response without coming off as pushy or annoying. //

Even if all of these are problems, the advantages of having a newsroom that is distributed yet not disconnected, more accommodating of different ways to be productive, more open to having its workflows hacked and more efficient at communicating feedback could be great. Then again, could technology have the perfect solutions?