Writing Well Part 3: Origins of a Writer

When writers are asked how to write well, they often reflexively talk about their childhood and how they became writers. James Joyce did it, George Orwell did it, and Steven King did it. I thought this was a strange pattern at first, but now I understand it. Writing well is not just about clarity and omitting needless words—it goes all the way down to the core of a person, and so writers tend to tell you about who they are to explain how or why they write as they do.

Joyce, Orwell, King

Joyce, Orwell, King

Growing Up

Many of us had that one teacher. That one horrible teacher who either hated you, or you hated, or both. For me, that teacher was Professor Cooney of the MIT writing department. In my entire academic career, she stood out as the most infuriating.

Before we get to her, I’ll tell you about what happened eight years earlier, in 7th grade. I was in Algebra I, an advanced math class for a 7th grader, because my 6th grade teacher said I was good at math. I had no idea I was good at math before that as I wasn’t particularly good at arithmetic. (Just as writing isn’t spelling—math isn’t arithmetic, so I’d be ok in that math class.) After the first test in that class, my friend got a perfect score and I didn’t do very well. I thought back to all the episodes of Star Trek I watched every weeknight at midnight during the summer, and about how Mr. Spock would have gotten a perfect score, too. And how could anyone not get a perfect score? You just follow things through to their logical conclusion and you get the right answer. From that day on, I was good at math and I liked it (and science, too). That’s where my head was.

Except for a girl, that is. Her name was Jenny. Jenny and I loved ironic double meanings. I talked to her on the phone often, for hours. She was there when the wet cement of my personality was hardening. We each delighted in the use of language, always saying things without saying them. I learned to choose my words carefully with Jenny, and to give them just the right shade of meaning. She gave me plenty of practice, too, and I've had a careful eye (and ear) for language ever since.

I got an A on every essay in every English class all four years of high school. I was not part of the literature kids' tribe though. I wasn’t into poetry or literature or reading any of that squishy stuff. I was the math and science kid who stopped by English class to get his A, usually causing a lot of trouble and debate. English teachers and I never had much regard for each other, and I knew some of them absolutely cringed at giving me those A’s, but what else could they do? I remember thinking at one point in high school that it would be an ultimate joke of the universe after all my hating of English classes if I would somehow end up a writer instead of a mathematician or physicist. (Note to the universe: nice one.)

By the time I encountered Mrs. Cooney, I knew how to write and I knew how to get an A on a writing assignment. I started her class by writing a short story in the style of Jack London (my choice) about a man and his dog. I thought it was pretty good. She hated it. The narrator actively judged the man in the first and last sentence of the story, on purpose. She hated that even more.

I didn’t know exactly why she hated it, and I wasn’t used to that kind of reaction. She kept saying, “It’s not literature! We write literature here.” It took me the whole semester to even get an inkling of what literature meant to her. It seemed mostly to mean, “boring stuff written by the students who Professor Cooney personally likes talking to in class.” She said my story was too fake and she wouldn’t even accept it, much less grade it. She said I had to write another story instead.

I may have some ability at writing, but writing takes me a very long time. What’s worse is that I can’t compartmentalize it from the rest of my life. When I write something, the actual time I spend typing is between 1% and 5% of the total time investment. The rest is spent day dreaming about it, thinking of how the ideas will go together, about this sentence that should appear halfway through, about things I might need to research first, and so on. And when all that’s sorted out, I still have to wait around for the moment when I’m not tired, hungry, or distracted. Then I have to keep waiting even more until I’m also inspired. I believe at least three of the planets must be aligned, too, or two plus a moon at the least. The point is, writing another story was a major time investment.

I don’t remember what happened with that second story, but I bet she hated it too. On the assignment after that, I wrote a story about a man who took a long journey to find a magic coin, but there was some kind of trick about how the guy who told him about the coin was not who he seemed. Yeah, she hated that one even more. I spent a very time long on that one making sure it was well-written. She said it was “genre writing,” not literature, and that it could appear alongside any other fantasy writing on a store shelf and blend right in. (Is that an insult or a compliment?) Apparently literature couldn’t contain magic. It also couldn’t be a mystery, couldn't have too much action, and could hardly have any violence, I would later learn. Meanwhile, we read a story about two girls who lived in an isolated countryside and used to play together as children, then they tried to keep in touch as adults but their lives had diverged too much to make the same kind of connection. Now that was literature, she said. I have to admit, even though it had no apparent point, it did feel real when I read it.

She made me write two stories for every one that anyone else wrote in that class. It was an incredible amount of time and work and she hated all of it. I wondered why she made me do all that if I was so terrible, yet none of the other students had to.

For my final assignment in that class, I decided to write something I knew enough about to bring to life. I wrote about a young man who was entering his first Chess tournament and the various personalities he encountered at the event. The antagonist was a tricky jerk who had enough experience with how the events were run to mess with the main character’s mind. They would face each other in the tournament, and I even went through the trouble of coming up with a real Chess situation that was interesting in itself, and that illustrated the mental sparring between the characters. And I took great care describing this so it wouldn’t be boring or overly technical for non-Chess players.

Guess what, she hated it. She said I was a failure as a writer and I’m guessing she added that I’d never amount to anything, for cliché’s sake. She said, and I quote, “You are a master of linguistic flourishes, but you ultimately have nothing to say.” Wow! Yes, she really said it, exactly like that. A master of linguistic flourishes…but ultimately with nothing to say. That was a lot of years ago, but I remember it exactly.

I began to wonder if she was right. She was a close-minded jerk to me, sure, but what was I trying to say with that story about the guy and his dog or about the magic coin? Maybe nothing. At least the Chess story had some point. The year after that in another writing class, I decided to write a comedy about depression (challenging!) and another story about someone who is trapped in his own superstitions, but ultimately realizes that he controls his own destiny in life. I was at least trying to really say something.

Having Something to Say

A few years later, I had a lot to say. I had competed in and organized numerous video game tournaments, and I kept seeing the same annoying losing attitudes. The players I hung out with didn’t have these hangups, but the ones on the periphery often had the whole concept of competition wrong. So I wrote Playing to Win. I finally had something to say, and I never got so much attention for writing anything until then.

William Strunk, Jr. famously said to omit needless words. I’ve come to look at this in a new light, and when I see writing that doesn’t really say anything, I wish all the words were omitted. There are a lot of mechanics involved with writing well, but it doesn’t amount to much unless you have something to say. Having something to say often goes along with taking a stand on something. Research what you’re interested in, live life and accumulate experiences, stand up for what you think is right and fight against what you think is wrong. It takes a certain kind of person to do that. Writing is often about revealing a truth or exposing a lie, so it’s no wonder that so many writers are the kind of people who don’t care what people think of them—they care about the truth and saying what they have to say. I don’t mean pop novelists either, I mean Ernest Hemingway and George Orwell. Even Richard Feynman was a great writer in this regard when he wasn’t busy being one of the world’s leading physicists. He even wrote a book called What Do You Care What Other People Think?

Learning the Craft

I worked with an amazing graphic designer for a while until he quit and went to another company. In our last conversation, the day before he left, I asked him how he became so good. How is it that he’s so much better at what he does than most others who try to do it? He said in art school, there was one Korean guy in his class who really shouldn’t have been in there. The Korean guy already took these classes in his own country, but his credits didn’t transfer over for some reason. My friend said he always studied the Korean guy, how he made this line, how he made that shadow, whether he added decoration here or not, and so on. He told me that when some students presented their projects, they had some big artistic vision they were trying to communicate, but they always fell so far short. My friend never focused on that—he focused on execution instead. His reasoning was that once he had mastered the mechanics of graphic design, he would then be able to think about what artistic statements he wanted to make. I did not take such a conscious journey as my graphic designer friend, but perhaps the result is the same: first, how to put sentences together properly, then having things to say.

Putting It All Together

There have been years where I had a lot to say, where I wrote many articles about game design. There have been other years where I was too consumed with working to say much of anything. Now and then, I feel the need to share some ideas, but I don't do it unless I really have something to say.

When I sit down to write, I don’t think about Jenny and the nuances of language I practiced with her all those years ago. Caring about exact shades of meaning is second nature now. And I don't think about Professor Cooney anymore either, but for a while I did. “A master of linguistic flourishes but ultimately with nothing to say? I’ll show her," I'd sometimes think. I’ll prove to her that I do have something to say, and that I’ll say it no matter what the consequences or what anyone thinks.

Maybe being fueled by such a negative fire was a bad thing, but being fueled by no fire is far worse. It's hard to work to have clear thoughts and to express them clearly, so some passion to get you through it—no matter what the source of that passion is—helps greatly. I’ll leave you with this quote from a writer who has sold over 350 million books:


You can approach the act of writing with nervousness, excitement, hopefulness, or even despair—the sense that you can never completely put on the page what’s in your mind and heart. You can come to the act with your fists clenched and your eyes narrowed, ready to kick ass and take down names. You can come to it because you want a girl to marry you or you want to change the world. Come to it any way but lightly. Let me say it again: you must not come lightly to the blank page.
—Stephen King

Writing Well, Part 4: Trolling

In some ways, trolling may be the most effective communication of all.

 

A troll is a person who posts or chats on the internet with the intent of stirring up trouble and getting emotional responses. A troll is not concerned with speaking the truth, nor with speaking lies. The truth value of statements isn’t important at all to a troll, only the amount of trouble their statements can cause.

Another aspect of trolling is efficiency. Ideally, the troll gives very little input to the system, but creates a large stir from it. Think of it like giving your opponent a bag of nonsense, but the opponent can’t simply open the bag and say “oh, that’s nonsense.” Instead, the nonsense is wrapped up in an intricate puzzle that takes pages of text to unravel and defend against.

 

James Cameron is a man clearly dedicated to his craft, but then again so was Jim Jones. But Cameron had much better results. Eleven fewer people died from cyanide poisoning.
—Mr. Plinkett

 

Is Trolling Bad?

I know a grandmaster troll. His name is garcia1000. He says that trolling is like sex: if you force it on someone, that’s bad, but if it’s consensual, then both parties enjoy the activity. Over the years, we’ve developed many “chat techs” that are handy language tricks for trolling. Playing with intentionally deceptive language is really fun, and I think there’s some value in it too. When someone tries to use this stuff on you, you’re ten steps ahead of them if you’re well aware of all these tricks. You can also incorporate these rhetoric tricks into your writing as jokes, or for real if you’re a news journalist.

Try consensually trolling your friends and develop your skills together.

Chat Techs

Implying a Connection When There Isn’t One

One of the easiest ways to troll is to imply a connection to something bad when there is actually no connection at all. The victim will have to go through all sorts of trouble to explain why there is no real connection.

He eats pizza without a knife and fork, like an animal in a zoo would.
Wilt Chamberlain had over 20,000 career rebounds. Meanwhile Governor Schwarzenegger had 0, the same number as Hitler.
DOTA has a song about it. So does killing cops.
Ian isn’t a pedophile, at least that’s the story so far.
Blake says he’s not racist, but Don Imus said that also.
By moving out of our cramped apartment into the larger one, we’ll finally have more breathing room, or “lebensraum” as the The Nazis called it.


Connection to Stock Price

stock.jpg


Amazon.com Inc. [AMZN -1.89%] is staying the course with a new line of Kindle Fire tablet computers that undercuts competitors like Apple Inc.’s [AAPL +0.55%] iPad on price. (source)


It sounds like the stock prices demonstrate that Amazon are idiots for undercutting Apple’s price, but the stock price changes are not because of this specific move. If Jeff Bezos cured cancer tomorrow, the Wall Street Journal article would read:

Jeff Bezos Cures Cancer [AMZN -1.89%]


 Mr. Bundesen says he chauffeured Grumpy Cat around Austin in a black BMW [BMW.XE +2.91%]  X5, with tinted windows. (source)



Did Grumpy Cat directly affect BMW’s stock price? Let’s go with yes.

Grumpy Cat

Grumpy Cat


True Goodness

 

Mother Teresa has performed many good deeds, but how many of them were truly good?
Aphotix has made many useful contributions to balancing the Yomi card game, but how many of them were actually useful?

 

Lack of Perfection = Badness

 

garcia1000, creator of numerous troll techs, has never created a single perfect troll.
Lady Gaga has written, directed, and sung many hit songs but she has yet to create any song without flaws.


The Absence of Something

 

The President will be holding a dinner at the white house next week. The best chefs in France will not be attending.
The ACLU will not be attending.
The League of Women Voters will not be attending.
EA held their company picnic last Friday. The IGDA, an organization that fights for quality of life issues on behalf of game industry employees, did not attend.
The downtown clinic opened its doors to all who needed medical attention, regardless of their age, class, or race. The clinic helped no black people yesterday.

 

In each case, it sounds like the lack of these people attending implies their disapproval. Actually it implies nothing and there’s no reason to expect them to have attended.


Not Immediately Available

Pop star Justin Beiber visited the Anne Frank museum and said “Hopefully she would have been a Belieber.” It’s possible this line made sense in the context in which it was said, but a news story can make it (or anything else) automatically look bad with this line:

Bieber's representatives did not immediately respond to CNN's request for comment Sunday, but visitors to the Anne Frank Facebook page had plenty to say.

 

Justin Beiber

Justin Beiber

“Not immediately responding” sounds like some sort of admission of guilt, when it actually means nothing at all. Beiber is guilty of not immediately responding many times though:

I don’t know what Justin Beiber did or didn’t do, but the “didn’t immediately respond” tech is great to combo with a false accusation.

Not the First Time


Sony's PlayStation Network servers crashed today. This isn't the first time that’s happened.


Even if it only happened once before, the statement implies it’s been multiple. Also, “it’s not the first time” can put the phrase "and it won't be the last" into reader's mind. The statement is factually correct though, even if it happened only one time before, so it can't be challenged.

Not the Last Time

Marissa Meyer

Marissa Meyer

Yahoo’s CEO Marissa Meyer banned employees from working from home, which was controversial. A “news” article ended the story with the sentence:

Her remote working ban may not be the last controversy of her rule. (source)

 

So now she’s held responsible for future, unspecified controversies! Also, it’s a nice touch to call her tenure as a CEO “her rule.” This implies it’s some dictatorial horror, when it’s actually the job of a CEO to “rule.”

This tech also combos well with accusations. Being accused of something doesn’t mean you did it, especially if the accusation is totally fabricated or ludicrous. But if we add that it “may not be the last time,” then it sounds more damning.

McDonald’s was accused of using rat meat for 20% of its burgers, and this may not be the last we hear of it.
Some people say Google is guilty of tax fraud, while others say this may not be the last time we hear this accusation.

 

That's also an example of “weasel words.”

Weasel Words

Weasel words are a way of using vague language and anonymous authority to assert something that’s impossible defend against because it’s too vague to even know what it means.

Some people / experts / many say that The Hobbit is the worst movie of modern times.

 

Which people? How do they know? What standard was used?

It is said that the this article is the definitive one on fun trolling language, though there are some who claim otherwise.


Who said that? They said it as fact? Also those who say otherwise only “claimed” it, so their viewpoint is diminished.

Examples
"A growing body of evidence..." (Where is the raw data for your review?)
"People say..." (Which people? How do they know?)
"It has been claimed that..." (By whom, where, when?)
"Critics claim..." (Which critics?)
"Clearly..." (As if the premise is undeniably true)
"It stands to reason that..." (Again, as if the premise is undeniably true—see "Clearly" above)
"Questions have been raised..." (Implies a fatal flaw has been discovered)
"I heard that..." (Who told you? Is the source reliable?)
"There is evidence that..." (What evidence? Is the source reliable?)
"Experience shows that..." (Whose experience? What was the experience? How does it demonstrate this?)
"It has been mentioned that..." (Who are these mentioners? Can they be trusted?)
"Popular wisdom has it that..." (Is popular wisdom a test of truth?)
"Commonsense has it/insists that..." (The common sense of whom? Who says so? See "Popular wisdom" above, and "It is known that" below)
"It is known that..." (By whom and by what method is it known?)
"Officially known as..." (By whom, where, when—who says so?)
"It turns out that..." (How does it turn out?¹)
"It was noted that..." (By whom, why, when?)
"Nobody else's product is better than ours." (What is the evidence of this?)
"Studies show..." (what studies?)
"A recent study at a leading university..." (How recent is your study? At what university?)
"(The phenomenon) came to be seen as..." (by whom?)
"Some argue..." (who?)
"Up to sixty percent..." (so, 59%? 50%? 10%?)
"More than seventy percent..." (How many more? 70.01%? 80%? 90%?)
"The vast majority..." (All, more than half—how many?)


Dog Wouldn’t Understand

 

If you explained global warming to a dog, the dog wouldn’t understand.
While James claims he's not racist, even his dog Woofy can't be sure of that.


Playing with the Likelihood of Things

 

It's possible Jeremy is sane like a normal person. We can't dismiss that possibility out of hand.

 

You can use the teapot fallacy to make anything, no matter how astronomically unlikely, have a 50% chance of being true:

There either is or isn’t a teapot orbiting Jupiter. 50/50 that it’s true.
There either is or isn’t a supernatural being who takes interest in my personal fortunes. Again, 50/50.


Saying Things Are Similar When They Aren’t

 

I think insisting on high quality games is similar to insisting on serving white people only. In both cases, you're insisting on something.
Amazon CEO Jeff Bezos was in charge of people, much like how Stalin was in charge of his.
Jill took several books from the library without paying. Robbers would have done the same thing.
John was good with building things with his hands, much like the Unabomber.

 

Admitted

Use “admitted” to make anything sound bad:

Bob admitted he bought the cheaper fabric softener.
Jane admitted she had pizza for lunch.
Andrea admitted she was intimately familiar with how to spell “pedophilia.”
We asked Greg if he committed the robbery, but he admitted nothing. (Also, he did not immediately respond.)

 

Combine this with the “absence of something” tech for even greater effect:

Charlie admitted his iPad didn’t contain any e-books against racism. Charlie also admitted he did not attend the recent ACLU rally about civil rights. 

 

Comparing Numbers and Degrees

When you say how good or how big or how numerous something is, say it’s more than an absurdly low value. This makes it sound like it probably is that low value.

The French Army had at least 3 soldiers.
Game of Thrones wasn’t the worst of HBO’s tv series, I’ll give them that.
When compared with the most vile and debauched scoundrels, President Obama is a lightweight. He did keep Guantanamo Bay open though.
The makers of the game BlazBlue were passionate about their craft, but then again so were Texas Governors. BlazBlue, a game with more than 6 fans, caused 137 fewer deaths by lethal injection.
Gordon Ramsay cares a lot about his craft, but then again so does Godzilla. Ramsay, who has 13 restaurants rated at least one star, had much better results. He leveled Tokyo 9 fewer times.

 

Being Paid For Things

 

The policeman, who is paid $52,000 per year, did not respond to the 911 call in time.

 

Throwing in salary numbers irrelevant to the situation makes it sound even worse. Being paid is bad.

 

The heart surgeon said the surgery was necessary to save Mr. Martinez’s life (he was paid to do the surgery).


You were paid to do something, implying that you're only doing it for the money like a hired shill. Being paid is bad.

 

Wolfgang Puck's signature herb-roasted chicken tastes like charred cardboard, and I could do a better job blindfolded,” said Ellen Kubolski, who has never been paid to cook anything in her entire life.

 

You haven't even been paid to do something, so your skills are very bad. Not being paid is bad.

 

Why Not Just?

 

Why not just implement a new feature in the game?
Why not just redo all the art in the game?
Why not just let prisoners come and go on the honor system?
Why not just have the CFO guess what the taxable revenue is this year?

 

“Why not just” is a powerful combo of two separate fallacies. First, “why not” implies that any insane idea should be the default. Why isn’t it ALREADY this way? Second, “just” is a red flag word for anyone who does any kind of work. “Just” implies that a task is a small amount of work no matter how much work it actually is. Finally, the “just” hides any and all negative fallout from the ripple effects of the proposed change. For example, if the CFO “just” guesses about the taxable revenue, she might end up in jail.

In Some Ways

Put “in some ways” before a statement to make it true no matter what. Even if it’s apparently false, the burden is now on the reader to construct some elaborate case where it could be true. If they can’t, it’s their fault for lacking imagination.

In some ways, having one of the worst health care systems in the world is a great boon to the United States.
In some ways, lack of exercise makes Jim even stronger.
In some ways, knowing more about a subject means you know even less about it.
In some ways, this article makes you a better writer.


Advanced Combos

 

The game Skullgirls sold fewer copies than the number of people in prison in the USA, a figure which speaks for itself.
Skullgirls could have given a copy to every one of those prisoners, but designer MikeZ admitted that he chose not to, which just continues the tragic trend.
We can't say if MikeZ is ultimately responsible for the prison riots, but we can say his decision to exclude prisoners from getting free copies of Skullgirls has been a long tradition of his.
Graham lacks the ability to sculpt believable statues from a single slab of marble, much the same way that animals in a zoo can't. This may not be the last time Graham is mentioned in connection with animals of subhuman intelligence.


This one is especially good because it manufactures an insane connection, then says it may not be the last time we hear it, citing itself as the reference.

 

I approve of this new tech, like Einstein who approved many new breakthroughs.
—garcia1000


You can think of these troll techs as a kind of vaccination. By injecting them into your bloodstream, you become more immune to them being used on you. Try injecting them into your writing, twitter, and friends. Enjoy!

The Sheathed Sword in Software Development

Working hard in and of itself is not a virtue. It's the result that counts, not the specific quantity of work needed to achieve it. Working smart is often a better tool to achieve a good result in software development. Unfortunately, working hard is more likely to be rewarded at most companies because it's so visible. Working smart can be invisible.

 

To see victory only when it is within the ken of the common herd is not the acme of excellence. Nor is it the acme of excellence if you fight and conquer and the whole empire says, “Well done!” True excellence is to plan secretly, to move surreptitiously, to foil the enemy’s intentions and balk his schemes, so that at last the day may be won without shedding  a drop of blood. To lift an autumn hair is no sign of great strength; to see sun and moon is no sign of sharp sight; to hear the noise of thunder is no sign of a quick ear.
—Sun Tzu, The Art of War

 

 

Software Development

Software projects (including all video games) are notoriously over-budget and over-schedule. Why is this? It has much to do with the highly counterintuitive nature of software project management, beautifully described by Steve McConnell in his book Software Project Survival Guide and in this article of his.

When project managers get involved in a project, they tend to impose a lot of process. They want tracking reports on this, detailed planning on that, reporting procedures on the other. It’s only “common sense” that all the time spent on extraneous bookkeeping like that takes directly away from the productive time that could have been spent implementing the actual software. Workers do admit that there’s a small amount of “thrashing,” or unproductive work, that’s basically unavoidable. So a graph of how much productive work gets done during the course of a project looks like this:

The mistaken notion that process is pure overhead and that everything will just work out in the end.

The mistaken notion that process is pure overhead and that everything will just work out in the end.

This is, of course, a fantasy. In reality, software development is an enormously complex undertaking that requires an enormous amount of coordination, cooperation, and communication. Defects that appear early in the process (and they DO appear) magnify in scale like a growing cancer as the project continues. When things can go wrong, things do go wrong, and they go wrong quite often in software development. It’s not the case that smartest and most able developers commit no errors. Even if that were true, errors and problems are introduced through coordination and communication problems, and even through outside factors beyond everyone’s control—not just through flawed code. So the real question is how does one go about minimizing, detecting, and correcting errors once one has admitted the truth that the existence of such problems is an unavoidable fact?

I can’t say it any better than Steve McConnell:

When a project has paid too little early attention to the processes it will use, by the end of a project developers feel that they are spending all of their time sitting in meetings and correcting defects and little or no time extending the software. They know the project is thrashing. When developers see they are not meeting their deadlines, their survival impulses kick in and they retreat to “solo development mode,” focusing exclusively on their personal deadlines. They withdraw from interactions with managers, customers, testers, technical writers, and the rest of the development team, and project coordination unravels.
Far from a steady level of productive work suggested [in the diagram above], the medium-size project conducted without much attention to development processes typically experiences the pattern shown [in the graphic below.]
In reality, the project becomes more complicated, and despite the emergency processes instituted, thrashing overtakes all.

In reality, the project becomes more complicated, and despite the emergency processes instituted, thrashing overtakes all.

In this pattern, projects experience a steady increase in thrashing over the course of a project. By the middle of the project, the team realizes that it is spending a lot of time thrashing and that some attention to process would be beneficial. But by then much of the damage has been done. The project team tries to increase the effectiveness of its process, but its efforts hold the level of thrashing steady, at best. In some cases, the late attempt to improve the project’s processes actually makes the thrashing worse.
The lucky projects release their software while they are still eking out a small amount of productive work. The unlucky projects can’t complete their software before reaching a point at which 100 percent of their time is spent on process and thrashing. After spending several weeks or months in this condition, such a project is typically canceled when management or the customer realizes that the project is no longer moving forward. If you think that attention to process is needless overhead, consider that the overhead of a canceled project is 100 percent.

 

 

Processes such as change control, QA, defect tracking, automated source code control, and so on are the methods of winning the battles against Murphy’s Law before the full-scale war is allowed to begin.

Even small investments in process can go along way. If you have a team of 20 people, having all 20 of them spend over an hour a day on tracking their progress is probably not a good use of time, but having them spend 10 minutes in a stand-up meeting (where you literally stand up) and have each person rattle off the work they plan to do today (and possibly what they did yesterday), keeping it under 30 seconds per person keeps everyone aware of dependencies. It might make you realize that of your three possible tasks, people are actually waiting on one of them, so you should work on that first. This type of meeting is just one example of investing a small amount of time in process to avoid bigger problems later.

Projects that attack problems before they become problems win the war with sheathed sword. Process becomes fine-tuned and second-nature, while thrashing is reduced.

Projects that attack problems before they become problems win the war with sheathed sword. Process becomes fine-tuned and second-nature, while thrashing is reduced.

Sun Tzu Says Nip It In The Bud

Sun Tzu’s said that the generals who win our praise are those who, through great effort, win large, dramatic battles. The far greater generals who should win our praise, though, are those who avert war altogether. They defeat the seeds of war long before the masses realize that there was any danger at all. This is especially true in the case of software design, since errors that appear early in the process become more and more costly and difficult to fix as the project progresses. Imagine a sentence in a design document describing how a particular piece will be implemented. How easy to change that sentence if it is in error and avert disaster, yet how hard to re-implement the entire module that later grows out of that sentence.

The Anchor

I worked at a company that was, like most software companies, entirely set up to praise hard work and not at all set up to praise kind of general Sun Tzu was talking about. In this company, two teams worked loosely in parallel from the same starting code base to create two different, vaguely related products, with roughly the same development cycle.

The actual quality of this software as far as end user is concerned—the game design—is totally irrelevant to this discussion. I know I like to talk a lot about game design, but let’s focus on software design for the moment. The lead programmer on my team was a careful, pensive, steady man. To him, the beginning of the project was a time for cleaning up the code base and reorganizing it to save time later. He was interested in creating a number of tools and processes designed to uncover code errors early in the upcoming development cycle.

I called this guy “The Anchor.” I felt I could sleep at night without worrying that the project would float off into an iceberg in the middle of the night, or something. His steady work made the final stages of the project pretty much by the book. The game made it through Sony’s rigorous approval process on the first pass.

Meanwhile, the sister project encountered a number of mysterious bugs towards the end of the project cycle. This was not surprising since their process was not as rigorous as that taken by my team’s lead. Tracking down some of those bugs was a monumental effort. Several of the programmers became company heroes by staying at work all night, working straight through with no sleep on countless occasions. Every time their project reached the final candidate stage, some new bug would be discovered, another monumental effort to fix it would take place, another final candidate would be created, then yet another bug would be found. Only through hard work totally unheard of in most industries and totally counterproductive to the well being of human workers was that project finally finished. (Let’s just say they didn’t get Sony’s approval the first time through.)

The management of the company couldn’t say enough good things about those guys who were working so hard. They were "examples we could all learn from!" The CEO gave out awards to some of those programmers on the other team who had worked far above the call of duty. The Anchor did not receive one.

Frankly, I found that offensive. First of all, those programmers who sacrificed their life and their health to pull of some kind of 11th hour Herculean win were not working beyond the call of duty. The company expected that from them. Worse yet, the far greater general—the general who had defeated armies of bugs before management or anyone else even knew a war was coming—was not given an award that day. His contribution was not visible even though it was far greater than the other team’s. When the hero wins the war before the masses know there was to even be a war, no one notices there even was a hero.

In closing, Sun Tzu in his Art of War had this to say about the tragic, hero-general:

…his victories bring him neither reputation for wisdom, nor credit for courage. For inasmuch as they are gained over circumstances that have not come to light, the world at large knows nothing of them, and he therefore wins no reputation for wisdom; and inasmuch as the hostile state submits before there has been any bloodshed, he receives no credit for courage.