Category Archives: thoughts

Thoughts, musings, etc.

I noticed an interesting thing in Chrome Canary this morning (Chrome Canary is the bleeding edge version of the Google Chrome browser for early adopters to try out) – when you perform a search using the browser omni-addressbar, you’re taken to the standard Google search results page. However, the search bar that has been at the top of the Google results page since seemingly forever, is gone.

In the above image, the Google Canary is using the dark blue theme. Apparently, the Google designers think that if you’re savvy enough to do a search via address bar (instead of going to Google.com to do your searches), then you’ll always do it from the address bar.

The light-gray subnav bar (“Web Images Maps Shopping, etc”) is bumped up to the top of the results page. Removing the search bar (and button) adds a good 30 pixels for more search result real estate. Here’s what 30 pixels looks like on a 500 pixel-high browser window:

What 30 pixels looks like on a Google Search results page

What 30 pixels looks like on a Google Search results page

(note: The black-bar top-nav is also removed in Chrome Canary, though I’m not sure if that’s the result of a different UX decision. That also frees up more screen space)

It’s a sensible design choice; for all I know, this change could’ve been enacted a year ago and I probably wouldn’t have noticed. The search bar as-part-of-the-browser-app is a design pattern that’s only become more entrenched with how search is done on native apps (on Google and on any other service that has full text search), where the search is accessed through a fixed widget or special button. Perhaps this will increase the rate of click throughs for Google search results that aren’t among the top two returned, now that there’s a little more real estate? It may seem like a sliver, but slivers can matter: Google’s and Amazon’s tests famously showed that imperceptible delays would have a significant negative effect on user engagement: in Amazon’s case, every 100ms cut sales on a given page as much as 1%.

Note: at the time of this post, Google Chrome was at version 26.0.1410.43. Canary is at 27.0.1454.0.

Update: Just noticed that Google Operating System (an unofficial blog) covered this issue last week. In his March 16 post, Alex Chitu has these complaints:

Closely integrating Chrome with Google Search breaks a lot of things. For example, you can’t edit the URL to tweak some parameters, the “I’m feeling lucky” feature is no longer available and the omnibox doesn’t include visual spell checking, enhanced suggestions and probably other features.

I think all of these complaints are likely seen as minor:

1. I bet Google’s A/B testing shows that a very negligible part of their user base tries to manually tweak the URL parameters. Hell, I don’t even do that and I’m a developer. When teaching data journalists how to navigate government websites by futzing with the params (which are much more straightforward than Google’s), I’ve found that many of them are amazed that you can even do that. I’m guessing that is very much the same for most Google users in general.

2. Spellcheck is not needed for Google searches. Google spends a significant amount of resources and academic talent to get past user input errors. In fact, Google probably wants to train users *not* to spellcheck their queries, as it slows down the search time (from the user’s perspective). Better to have Google bend over backwards for the user, I suppose.

3. “I’m feeling lucky” is more or less unneeded with how Google has refined its search experience. And it doesn’t seem like a much used feature anyway, though it is a cool quirk.

The bigger picture, though, is that greater visibility for the third or fourth search result is likely to be something that benefits all Google search users than the features listed above.

Author Amy Wilentz has a fun piece about how Google listed her as “dead” in the rich snippet search result for her name. Her untimely death apparently came from her Wikipedia entry, which was, to say the least, unconventionally created:

(is there a conventional way for Wikipedia entries to come about?)

Google picked up my facts from my Wikipedia entry. My Wikipedia entry, oddly, was put up by Cousin Joel, who has a genealogy obsession, and has assembled an astounding dossier on our family, finding members of it in places as far flung as Dvinsk, Latvia, Hollywood, California, and Perth Amboy, New Jersey.

So it’s not too surprising that my original Wikipedia entry, as conceived by Joel, was — let’s be honest — more about my father (a famous New Jersey judge) than about me. Joel began the entry with my connection to my father, and immediately mentioned my father’s birthdate and the date of his death.

Google is not a subtle thief. If your name on Wikipedia is followed by a birth and death date, apparently those belong to you from that day forward, no matter whose dates they may be. Seen that way, I suppose I should just be glad that I’m not related (as far as Joel knows) to King Solomon, another judge.

The problem was probably not Google’s fault: natural language processing across the entire corpus of the web is a tricky thing. But Wilentz tackles the technical topic of search indexing from a layperson’s standpoint, which, in my opinion, makes it a particularly valuable read as she details the impregneable process of how to correct Google. I understand the technical theory (I think) of Google’s searchbots but I’m not sure that even I know how to get something fixed in the search results. More importantly, I don’t even know that if Google wanted to improve things, how they might do so that wouldn’t crimp the technical workflow. Anyway, Wilentz’s anecdote is well-worth reading, and as you’d expect from an author deserving of a Wikipedia entry, nicely written and entertaining.

At some point after Wilentz wrote her post, her search result correctly lists her as alive (for now). It’s likely a result of her Wikipedia entry’s first line listing her birth date – “Amy Wilentz (born September 1, 1954) is an American journalist and writer. – as opposed to: “Amy Wilentz is an American journalist and writer.”. Note/Update: this theory is wrong, as the corrected birthdate format didn’t happen until today. Matt Cutts responded to the post on Hacker News.

But who really knows the machinations behind Google’s search results? Wilentz’s fixed lifespan reminds me of this entertaining anecdote from (Steven Levy’s “In the Plex”) (non-affiliate link) on how Google engineers fixed a vexing problem of a garden gnome that wouldn’t go away:

But one problem was so glaring that the team wasn’t comfortable releasing Froogle: when the query “running shoes” was typed in, the top result was a garden gnome sculpture that happened to be wearing sneakers. Every day engineers would try to tweak the algorithm so that it would be able to distinguish between lawn art and footwear, but the gnome kept its top position.

One day, seemingly miraculously, the gnome disappeared from the results. At a meeting, no one on the team claimed credit. Then an engineer arrived late, holding an elf with running shoes. He had bought the one-of-a kind product from the vendor, and since it was no longer for sale, it was no longer in the index. “The algorithm was now returning the right results,” says a Google engineer. “We didn’t cheat, we didn’t change anything, and we launched.”

Someday, a Google engineer may find it easier to just ressurect someone than algorithmically fix a search snippet…

Update: Google search engineer Matt Cutts responded on Hacker News. He doesn’t say how it was eventually fixed, but says that the “Feedback / More info” link really does lead to a reporting tool that gets reviewed “and that’s the fastest way to report an issue”

The senseless, polarizing feud sparked by a “dongle” joke at PyCon had nowhere to go but to the bottom-feeders. Adria Richards’s artless public shaming of two joking developers led to one of the developers being abruptly fired by his employer, PlayHaven. The firing predictably led to a vicious, cowardly backlash by misogynists, which could only force moderates, whether or not they agreed with her initial reaction, siding with Richards against the ugly attacks.

Now Richards’s has been fired by SendGrid, almost as a ritual sacrifice to the DDoS crowd.

With two martyrs, I don’t have hope that the discussion to become any more rational and less reactionary. But I almost forgot the ex-PlayHaven developer’s apology two days ago, after his own firing and before Richards’s.

In the annals of gracious responses on the Internet, “mr-hank’s” ranks at the top. Of all the ways he could’ve criticized Richards, with an angry Internet mob behind him, he not only called for peace, but killed Richards’s accusation with kindness:

Hi, I’m the guy who made a comment about big dongles. First of all I’d like to say I’m sorry. I really did not mean to offend anyone and I really do regret the comment and how it made Adria feel. She had every right to report me to staff, and I defend her position. However, there is another side to this story. While I did make a big dongle joke about a fictional piece hardware that identified as male, no sexual jokes were made about forking. My friends and I had decided forking someone’s repo is a new form of flattery (the highest form being implementation) and we were excited about one of the presenters projects; a friend said “I would fork that guys repo” The sexual context was applied by Adria, and not us.

My second comment is this, Adria has an audience and is a successful person of the media. Just check out her web page linked in her twitter account, her hard work and social activism speaks for itself. With that great power and reach comes responsibility. As a result of the picture she took I was let go from my job today. Which sucks because I have 3 kids and I really liked that job.

She gave me no warning, she smiled while she snapped the pic and sealed my fate. Let this serve as a message to everyone, our actions and words, big or small, can have a serious impact.

I will be at pycon 2014, I will joke and socialize with everyone but I will also be mindful of my audience, accidental or otherwise.
Again, I apologize.

Only Richards and the joking devs know what was said at PyCon, how it was said, and the intent behind it. But mr-hank avoids even the slightest hint of misogyny and instead pleads with Richards to use her “great power” more responsibly in the future.

No accusations of man-hating. No calls for vengeance. Just a straightforward apology and an appeal for everyone to learn the importance of patience in confrontation. Besides the loss of the two jobs and the needless fear and hate generated by this incident, my greatest disappointment is that Richards didn’t get (or ignored) a chance to respond to “mr-hank”, whose gracious apology will likely be forgotten in the angry debate that will continue for the next few days.

Update: Richards messaged me to point out that she did respond to the HN commenter. I do remember reading this and fault myself for not mentioning it, as it was a civil response. I guess what I was disappointed in not seeing was a full-blown dialogue, but it’s hardly Richards’ or mr-hank’s fault that that didn’t happen amid the fallout and the Internet’s rush to judgment.

Richards’ response is posted below:

Thanks for speaking up, contributing your viewpoint on HN and not attacking me.

I’m sorry to hear your employer deciding to not to work with you on this and I hope they reconsider, bring you back on and dealing with it constructively.

For context, I’m a developer evangelist.

That means I’m an advocate for developers, male and female. While I hear abou demanding bosses with impossible deadlines for product launches, I also hear about the experiences of women working at startups.

In both cases I offer suggestions, ideas and mentoring to help the developers become problems solvers. Sometimes the answer is our API or not answering email after 7pm while other times it about being assertive and shedding impostor syndrome.

The forking joke set the stage for the dongle joke.

Yes, this time I decided I didn’t want to argue my perspective. I decided instead to accept it bothered me and took action based on the PyCon Code of Conduct. It sounds like if I’d said something about the forking you would have denied it having a sexual association. Not sure if I smiled but I’m also unsure what facial expression you would have expected.

I just got done writing my blog post you can read here: http://butyoureagirl.com/14015/forking-and-dongle-jokes-dont…

See you next year.

I’m done buying physical books – except when I go to The Strand in the East Village, where I seem to never leave without buying something.

Vogue: The Editor’s Eye is my latest purchase. I have enough photo books but I liked that this one is purportedly about the influence of the fashion editors on the magazine’s photography. As a photographer, I’ve come to realize that editing is as important as the actual on-camera skills. Maybe even moreso in this day of near infinite film rolls.

For every hour I spend taking pictures, I probably spend five to ten hours picking out photos, organizing, and then publishing them. Even on my Flickr account, where I dump photos for archival purposes, I probably upload fewer than 1 out of 50 photos that I actually take.

Anyway, The Editor’s Eye is still worth it for the photography alone. The book covers eight fashion editors and devotes a few pages of text to their biographies. But the process of editing – it being more a confluence of personality, experience, and temperment as much as it is skill – is hard to capture in words and the book doesn’t shed any particular light on the work. It’s not a surprise, then, that fashion editors were uncredited until Anna Wintour took over in 1988.

The above 1950 photo by Clifford Coffin of Ernest Hemingway and Jean Patchett is one of my favorites in the book. The fashion editor then, Babs Simpson, said she was sent to Havana to “catch” Hemingway, without even a single phone number to reach him at. She went to the Ambos Mundos, one of his favorite drinking spots, and got his phone number from the manager.

Simpson described the circumstances of the difficult photo session to writer Dodie Kazanjian:

We wanted to start early in the morning before it got hot. When we got there at eight o’clock, as agreed, nobody was in sight. Two champagne glasses were bubbling away, though, and finally Hemingway appeared, with a very young and good looking Basque priest.

Hemingway took a great shine to Jean, of course, and I got on very well with the Basque priest…but it got worse and worse as the day went on, because Hemingway and the priest got drunker and drunker…Isn’t [Hemingway] revolting? They wanted us to go and see the pelota or something or other with them afterward. They wanted to spend their lives with us. So we got the first plane we could out of there.

You can order Vogue: The Editor’s Eye from Strand’s Website. Apparently HBO did a documentary with the same title a few months ago.

I’m currently reading “Heads in Beds” by Jacob Tomsky, a purported insider’s account of the hotel business. Besides being pretty entertaining, it’s full of interesting facts (it costs $30 to $40 to turn over the average hotel room), helpful advice (speak out the employee’s name when making a request you don’t want said employee to forget), and unpleasant anecdotes, such as what happened to a pro athlete’s bottle of cologne when the athlete stiffed his bellman.

The worth of a bellman is a recurring topic in the book. Even in the age of wheeled suitcases, a good bellhop can still make a living. While the wages are low – the median salary is $20,880, according to current Labor Department statistics – a Manhattan bellhop who’s a “real hustling bullshit artist” might make “well over a hundred thousand dollars” annually, Tomsky claims, from an endless stream of ones and fives. And a guest who is too cheap to spare a couple bucks? Tomsky writes: “He shouldn’t use his toothbrush that night (or ever again, really).”

So when Tomsky, then a recent college graduate and college loan debtor, is offered a promotion to be a bellman or a manager, it’s not a straightforward decision. The bellman position pays much better for fewer hours. But his general manager frames the tradeoff in a memorable way:

(emphasis mine)

“I trust you, Tommy. I’m going to offer you a choice. You’re done with the front desk. I heard you’ve started to loosen up down there, started in with the jokes.”

“Oh, well, I hope I haven’t—”

“Not to worry. It’s natural. You’ve outgrown the position. So I’d like to offer you two opportunities. Whichever one you want is yours. As you are aware, there is a bellman position recently available. Extremely recently. It’s yours if you want it. You are fantastic with the guests. Or.”

“Or?”

“Housekeeping manager. Management, Tommy. Take over the evening position down there. You’d be in charge of turndown, scheduling, purchasing, and a thousand other things. A staff of 150.

“Let’s talk money. Housekeeping means ten-hour shifts or more, on salary. When you break it down hourly, you will make less than you are making now. You’ll have to purchase your own suits. The work is physically demanding, the staff is large and can be difficult. It’s a very challenging position. Bellman? You’ll double your money immediately and keep the eight-hour shifts. Zero responsibility.”

“You think I should take the bellman position?”

“Do that, and you’ll never be anything else in your life. Hate to say it, but it’s true. I’ve seen it my whole career: Show me a twenty-year-old kid getting his first job as a bellman, and I’ll show you a seventy-year-old bellman who started fifty years ago. You grow accustomed to that pay grade, and taking a step forward will always mean cutting your money in half. No one takes that step.”

“Housekeeping,” I said.

Not a bad lesson, for the hotel business or any business.

Excerpt via: Heads in Beds: A Reckless Memoir of Hotels, Hustles, and So-Called Hospitality (non-affiliate link) by Jacob Tomsky (2012).

A relevant 2001 essay: “How to Correctly Tip a Bellman

One of my least fulfilling reporting experiences involved a meeting between Ukrainian community leaders and local school district officials. There had been a brawl at a middle school and the Ukrainians, being the minority in that area, suspected their kids were racially targeted.

Anyway, the difficulty was that they didn’t speak English very well and many others at the meeting – the district officials and me, included – didn’t speak Ukrainian. So we had translators. The meeting had taken some time to plan and parents were nervous about their children’s safety, so everyone hoped for some kind of resolution. But after the meeting kicked off with long speeches by both sides – made doubly long by having to listen to the sterile translation that came afterwards, it seemed obvious that even a meaningful, impassioned debate was futile, nevermind reaching a satisfying resolution. The district officials told me afterwards, of course, that this was a good use of time, while the Ukrainian community members didn’t think anything came out of it.

When you think about it in theory, having a translator seems like a “good enough” solution. But when you’re sitting there, even though you and your other side share the same thought processes and general human understanding (independent of spoken language), a translator cannot:

  • Connect statements to the body language and emotion nuance of the original speaker
  • Mediate the kind of free-flowing give-and-take that is necessary for fulfilling debates
  • Make up for the time delay between the original statement and spoken translation

And of course, there’s the problem of knowing if the translation is even correct, as we know from Suntory Time:

This is a roundabout way to argue for the need for digital literacy, i.e. the Learn to Code movement. Code.org launched with big fanfare this week, featuring just about, well, everyone – Bill Gates, Bill Clinton, will.i.am(?), and everyone’s favorite “computer geek trapped in an NBA player’s body,” Chris Bosh – telling us why we all needed to program.

And of course there’s the backlash: why does everyone need to program? Jeff Atwood wrote a well-read essay about it last year (“Please Don’t Learn to Code”), Coders Lexicon posted an essay last night:

The fact is, the whole world should not learn to code anymore than all of us should learn to be a space shuttle engine designer or a lawyer. While I understand the need for more people to get interested in computer science and to fill our ranks with people who can meet the skills of the 21st century, going out there and telling everyone that coding is as easy as putting a bit of syntax down into an IDE and hitting compile is not the way. We need passionate people who are creative and want to learn to DESIGN software in addition to coding.

There are a couple problems with this argument. The first is making programming sound as time-intensive and domain-specific as space shuttle engineering or law. The second is making programming sound like an all-for-nothing proposition: don’t get into programming unless you can do it really well, or else your program will kill people.

(Not that that hasn’t happened…but the more relevant statement would be: don’t code people-killing programs unless you know what you’re doing.)

What would schools be like if we warned children to not learn how to read or write because ideas in books and newspapers have frequently made people’s lives miserable? Or, how about, don’t learn math, or the metric system, because even Lockheed Martin and NASA engineers can screw up and lose a $125 million Mars satellite?

The reason to learn how code works is to have a direct involvement in the technology and data we rely on. Just as we learn to read and write at a basic level so that our time isn’t spent waiting for someone – who may be much better and specialized at it – to read the news or road signs or write love letters for us.

In the newspaper world, it’s assumed that every reporter knows how to write. That’s not even remotely close to reality. In the golden, fat days, a reporter could expect three to four layers of editors to go through his/her work before it got printed (today, readers just have to deal with a lot more typos and errors). But even then, you couldn’t get by as being a fantastic reporter and storyteller who was also illiterate. Think about it: you don’t need to know how to read or write to go around asking questions or dictating what you remember hearing of a blockbuster scoop. But imagine the editors who get to spend their day transcribing and retelling you what they’re actually putting down on paper.

More importantly, think about what you, the illiterate reporter loses out on. You don’t get hands-on involvement on how the facts and quotes are arranged, because you have to wait for it to be done (and then read back to you) before you have a say. And there’s a lot that you just don’t know that you don’t know. Like how a headline, by its size, color, and length, can change everything about how a reader perceives your story. Or how a story that’s in print has a much different, detached effect than what you’ve experienced with the spoken word (similarly, writing copy for broadcast is its own separate art compared to newspaper writing).

But you don’t know that because you know that there’s a story, of some sort, is on the paper and people seem to be reading it so what’s the big deal?

This is the gap of understanding for anyone who isn’t digitally literate. It’s not about knowing how to build a website or assemble your own computer. It’s not even that you need to know a lot, just as you don’t have to be able to recite the entire works of Shakespeare to justify traditional literacy. With digital literacy, it’s about knowing enough to know what’s possible with computers, data, and technology, to control more of how it affects you. Or, as Donald Rumsfeld puts it, having fewer unknown unknowns.

How much is “knowing enough”? There’s a lot that’s been written about it in better places, Code.org probably isn’t a bad place to start. Besides learning to program, which is not the only thing to do or even the ultimate end goal, the two practical steps I can suggest are:


Also this week, Jeremy Ashkenas announced the first release of Literate CoffeeScript, a format that combines CoffeeScript with the easy-to-read-and-turn-to-HTML Markdown syntax. If you’re an experienced coder, this seems like nothing more than block-extended comments that are found in any language.

However, in practice, the power is in the details. I know that I avoid documenting code – even though we spend far more time re-reading code than actually writing it – because I just have never committed to some kind of system of making code comments easy to read (should I use asterisks to emphasize something? Or all caps? Or double space things?). With Markdown, you have the power of HTML to document your code. And more importantly, it’s intuitive and easy, which makes you more likely to write comments in the first place.

Check out Ashkenas’s demonstration: his own blog is powered by a “quick-and-dirty” blogging engine he wrote in Literate CoffeeScript. This is what the generated code and documentation look like on Github.

On a related note: if you’re a programmer who doesn’t understand why non-programmers need to be digitally literate: imagine having to write code in another language. Not programming language, but human language, such as in Chinese characters, without actually knowing that language. Sure, you could conceive an amazing program. But writing it yourself, with the help of an interpreter who types out what you say? Sounds even more laborious and mind-numbing than the worst programming project imaginable.

My former colleague, Charlie Ornstein over at ProPublica, wrote a thought-provoking, emotional piece on the costs of end-of-life care. As a health care reporter (one of the best in the business; he was a Pulitzer Prize recipient at the LA Times), he has written a lot about how end-of-life care is often prolonged beyond reason – account for as much as 25% of Medicare payments in the last year of a patient’s life. But when his mother was dying, he writes, “none of my years of reporting had prepared me for this moment, this decision.”

My father, sister and I sat in the near-empty Chinese restaurant, picking at our plates, unable to avoid the question that we’d gathered to discuss: When was it time to let Mom die?

It had been a grueling day at the hospital, watching — praying — for any sign that my mother would emerge from her coma. Three days earlier she’d been admitted for nausea; she had a nasty cough and was having trouble keeping food down. But while a nurse tried to insert a nasogastric tube, her heart stopped. She required CPR for nine minutes. Even before I flew into town, a ventilator was breathing for her, and intravenous medication was keeping her blood pressure steady. Hour after hour, my father, my sister and I tried talking to her, playing her favorite songs, encouraging her to squeeze our hands or open her eyes.

You can read the rest of Charlie’s story here.

Charlie’s piece brought to mind an equally powerful but hard-to-read story written by Atul Gawande for the New Yorker, “Letting Go (2010)

Several days ago, Sri Lankan investigative reporter Faraz Shaukataly was shot in the neck at his home. Shaukataly is expected to survive but the shooting brings to mind the death of Lasantha Wickramatunga, who was the editor at Shaukataly’s newspaper, the Sunday Leader.

Wickramatunga was shot to death on his way to work in January 2009. He had been assaulted before and his home sprayed with machine-gun fire. Because he expected to die in the service of journalism, Wickramatunga penned a letter to be published in that event of his assassination.

It’s an eloquent description of the thankless job of journalism under a corrupt state and the motivations for those who still pursue it despite the danger and hardships. It is also personal, addressing the man whom Wickramatunga considers a long-time friend, and who Wickramatunga believes will be ultimately responsible for his death: President Mahinda Rajapaksa.

The letter was first published by Steve Coll at the New Yorker:

No other profession calls on its practitioners to lay down their lives for their art save the armed forces and, in Sri Lanka, journalism. In the course of the past few years, the independent media have increasingly come under attack. Electronic and print-media institutions have been burnt, bombed, sealed and coerced. Countless journalists have been harassed, threatened and killed. It has been my honor to belong to all those categories and now especially the last.

I have been in the business of journalism a good long time. Indeed, 2009 will be The Sunday Leader’s 15th year. Many things have changed in Sri Lanka during that time, and it does not need me to tell you that the greater part of that change has been for the worse. We find ourselves in the midst of a civil war ruthlessly prosecuted by protagonists whose bloodlust knows no bounds. Terror, whether perpetrated by terrorists or the state, has become the order of the day. Indeed, murder has become the primary tool whereby the state seeks to control the organs of liberty. Today it is the journalists, tomorrow it will be the judges. For neither group have the risks ever been higher or the stakes lower.

Why then do we do it? I often wonder that. After all, I too am a husband, and the father of three wonderful children. I too have responsibilities and obligations that transcend my profession, be it the law or journalism. Is it worth the risk? Many people tell me it is not. Friends tell me to revert to the bar, and goodness knows it offers a better and safer livelihood. Others, including political leaders on both sides, have at various times sought to induce me to take to politics, going so far as to offer me ministries of my choice. Diplomats, recognizing the risk journalists face in Sri Lanka, have offered me safe passage and the right of residence in their countries. Whatever else I may have been stuck for, I have not been stuck for choice.

But there is a calling that is yet above high office, fame, lucre and security. It is the call of conscience.
The Sunday Leader has been a controversial newspaper because we say it like we see it: whether it be a spade, a thief or a murderer, we call it by that name. We do not hide behind euphemism. The investigative articles we print are supported by documentary evidence thanks to the public-spiritedness of citizens who at great risk to themselves pass on this material to us. We have exposed scandal after scandal, and never once in these 15 years has anyone proved us wrong or successfully prosecuted us.

Every newspaper has its angle, and we do not hide the fact that we have ours. Our commitment is to see Sri Lanka as a transparent, secular, liberal democracy. Think about those words, for they each has profound meaning.

Transparent because government must be openly accountable to the people and never abuse their trust. Secular because in a multi-ethnic and multi-cultural society such as ours, secularism offers the only common ground by which we might all be united. Liberal because we recognize that all human beings are created different, and we need to accept others for what they are and not what we would like them to be. And democratic… well, if you need me to explain why that is important, you’d best stop buying this paper.

Many people suspect that The Sunday Leader has a political agenda: it does not. If we appear more critical of the government than of the opposition it is only because we believe that – pray excuse cricketing argot – there is no point in bowling to the fielding side. Remember that for the few years of our existence in which the UNP was in office, we proved to be the biggest thorn in its flesh, exposing excess and corruption wherever it occurred. Indeed, the steady stream of embarrassing exposes we published may well have served to precipitate the downfall of that government.

It is well known that I was on two occasions brutally assaulted, while on another my house was sprayed with machine-gun fire. Despite the government’s sanctimonious assurances, there was never a serious police inquiry into the perpetrators of these attacks, and the attackers were never apprehended. In all these cases, I have reason to believe the attacks were inspired by the government. When finally I am killed, it will be the government that kills me.

The irony in this is that, unknown to most of the public, Mahinda and I have been friends for more than a quarter century. Indeed, I suspect that I am one of the few people remaining who routinely addresses him by his first name and uses the familiar Sinhala address oya when talking to him. Although I do not attend the meetings he periodically holds for newspaper editors, hardly a month passes when we do not meet, privately or with a few close friends present, late at night at President’s House. There we swap yarns, discuss politics and joke about the good old days. A few remarks to him would therefore be in order here.

Mahinda, when you finally fought your way to the SLFP presidential nomination in 2005, nowhere were you welcomed more warmly than in this column. Indeed, we broke with a decade of tradition by referring to you throughout by your first name. So well known were your commitments to human rights and liberal values that we ushered you in like a breath of fresh air. Then, through an act of folly, you got yourself involved in the Helping Hambantota scandal. It was after a lot of soul-searching that we broke the story, at the same time urging you to return the money. By the time you did so several weeks later, a great blow had been struck to your reputation. It is one you are still trying to live down.

You have told me yourself that you were not greedy for the presidency. You did not have to hanker after it: it fell into your lap. You have told me that your sons are your greatest joy, and that you love spending time with them, leaving your brothers to operate the machinery of state. Now, it is clear to all who will see that that machinery has operated so well that my sons and daughter do not themselves have a father.

In the wake of my death I know you will make all the usual sanctimonious noises and call upon the police to hold a swift and thorough inquiry. But like all the inquiries you have ordered in the past, nothing will come of this one, too. For truth be told, we both know who will be behind my death, but dare not call his name. Not just my life, but yours too, depends on it.

As for me, I have the satisfaction of knowing that I walked tall and bowed to no man. And I have not travelled this journey alone. Fellow journalists in other branches of the media walked with me: most of them are now dead, imprisoned without trial or exiled in far-off lands. Others walk in the shadow of death that your Presidency has cast on the freedoms for which you once fought so hard. You will never be allowed to forget that my death took place under your watch. As anguished as I know you will be, I also know that you will have no choice but to protect my killers: you will see to it that the guilty one is never convicted. You have no choice. I feel sorry for you

That The Sunday Leader will continue fighting the good fight, too, is written. For I did not fight this fight alone. Many more of us have to be – and will be – killed before The Leader is laid to rest. I hope my assassination will be seen not as a defeat of freedom but an inspiration for those who survive to step up their efforts. Indeed, I hope that it will help galvanise forces that will usher in a new era of human liberty in our beloved motherland. I also hope it will open the eyes of your President to the fact that however many are slaughtered in the name of patriotism, the human spirit will endure and flourish. Not all the Rajapakses combined can kill that.

You can read the full letter at the New Yorker.

In September 2012, a majority stake in the Sunday Leader was bought by one of President Rajapksa’s allies. The Leader’s editor was reportedly sacked for continuing to publish critical articles of the Sri Lankan government. The newspaper‘s tagline, though, still remains: “Unbowed and Unafraid”

It’s kind of fun to read through the New York Times’ historical archive and read what the tech coverage back in 1851 – a recent gem posted on HN concerned the controversy behind Thomas Edison’s 141-question job interview (‘Where do we get borax from?‘).

I was looking up some computer history and was wondering when the word “computer” made its first appearance in the Grey Lady. The NYT’s archive search allows for some fuzziness, so “computer” brings up numerous articles with “compute” and “computed” – as in, to calculate.

I didn’t search through every individual article, as the old articles are still in PDF form. But I think May 2, 1892 (the job posting says May 1), may at least be the first time the word “computer” shows up in a NYT headline (PDF).

The short blurb appears to be in the Classifieds section. It reads:

A COMPUTER WANTED

WASHINGTON, May 1. – A civil service examination will be held May 18 in Washington, and, if necessary, in other cities, to secure eligibles for the position of computer in the Nautical Almanac Office, where two vacancies exist – one at $1,000, the other at $1,400.

The examination will include the subjects of algebra, geometry, trigonometry, and astronomy. Application blanks may be obtained of the United States Civil Service Commission.

FYI, according to this inflation calculator, $1,000 in 1892 is equivalent to about $24,650 today.

Again, the “to calculate” meaning is implied here, with the applicant expected to help compile the used by the U.S. Navy for celestial navigation. The almanac office is still in existence (as a part of the U.S. Naval Observatory) and you can still purchase your own copy of the almanac, which includes “the following data tabulated at hourly intervals to a precision of 0.1 arcminute: the Greenwich hour angle and declination of the Sun, Moon, and navigational planets; the Greenwich hour angle of Aries” and more.

edit: Menachem Wecker ‏says there are earlier references and puts my archive searching to shame:


It wouldn’t be surprising, though, to see “computer” as machine referred to in the 19th century. The concept of a calculating machine dates back to the English mathematician and engineer, Charles Babbage, though his “Difference engine” was never built during his lifetime.

In his 1953 book, “Faster Than Thought,” author B.V. Bowden refers to the job of (human) computer as unskilled labor and that the French had figured out a method of assembly-line computing:

In 1812 [Charles Babbage] was sitting in his rooms in the Analytical Society looking at a table of logarithms, which he knew to be full of mistakes, when the idea occurred to him of computing all tabular functions by machinery. The French government had produced several tables by a new method. Three or four of their mathematicians decided how to compute the tables, half a dozen more broke down the operations into simple stages, and the work itself, which was restricted to addition and subtraction, was done by eighty [human] computers who knew only these two arithmetical processes. Here, for the first time, mass production was applied to arithmetic, and Babbage was seized by the idea that the labours of the unskilled computers could be taken over completely by machinery which would be quicker and more reliable.

When was “Charles Babbage” first mentioned in the Times? Again, the fuzzy searching feature makes it hard to narrow down articles that contain only “Charles Babbage”. The earliest I found was this “Scientific Gossip” column, dated Feb. 6, 1881, which mentions his son, Henry P. Babbage, who “has recalled to public attention the numerical system of signals proposed by his father…a system which is applicable to light and sound.” According to that method:

Every light house would have its own number, which would be continually repeated, either by light or sound, as long as necessary. Thus, if the light-house was numbered 73, there would be during foggy weather seven blasts at short intervals, then a pause: then three blasts, and a longer pause; after which the same would be repeated as long as the fog lasted. The number of the light-house could be given in 30 seconds.

As the light-houses on either side would be arranged with numbers not having the same digits, (say, for example, 25 and 48,) the counting of one digit would in most cases indicate the light-house and the counting of the second would afford a check and give positive assurance of the correctness of the observation if it was found to tally with the number found on the chart.

In this system nothing else has to be done beyond counting the number of the blasts; no special training is required, and a glance at the chart tells everything wanted. Surely this is within the intellect of almost any sailor of any nation.

If you read the rest of that Scientific Gossip column, it seems that the audience of 1881 had more patience than the audience of today for verbose technical explanations.

Another random first-mention-in-the-Times search: Nintendo, found on Oct. 8, 1955. It’s a brief note on how the “Nintendo Playing Card Company” and the approximate translation of “Nintendo” is “a corporation whose fortune or prosperity should be left to the mercy of heaven.”

The article notes, “evidently heaven has smiled on the Nintendo Company, because it has been using the mark since 1887.”

Well, I’m not quite done with my promised revision of the Bastards Book of Ruby. Or of Photography…but I’ve decided, oh what the hell, I should write something about regular expressions.

Actually, there is some method to this madness. As part of the process of updating the Ruby book, I realized I needed to spin off some of the larger, non-Ruby related topics. So, at some point, there will be mini-books about HTML and SQL. Regular expressions, as I keep telling people who want to deal with data, are incredibly important, even if you think you never want to learn programming. Hopefully this mini-book will make a strong case for learning regexes.

The second motive is I’ve been looking for a html/text-to-pdf workflow. So this is my experiment with Leanpub, which promises to turn a set of Markdown files into PDF/mobi/etc, while handling the selling process. I don’t expect to sell any copies of the BBoRegexes, but I hope to get a lot of insight about the mechanics behind Leanpub and if it presents a viable way for me to publish my other projects.

Check out the Leanpub homepage for my tentatively tiled book, The Bastards Book of Regular Expressions. Or, you could just read the mega-chapter on regexes in my Ruby book.