Their tearful reunion touches many, as they witness the heartbreak of lost connections. We celebrated the previous election, but many who participated then are no longer with us, says a survivor. District administration designated three polling stations for the survivors, two at Neelicappu and one at Meppadi

Good polling was reported at the landslides-affected region in Chooral Mala and tribes-populated areas in the district.

The award was presented at the 27th Energy Technology Meet in Bengaluru.

GSK will keep its existing portfolios while entering areas like oncology, said company officials at its centenary celebrations

Words to tattoo on your knuckles:

Over the past couple of years, my blog hasn’t felt my own, to a degree. It’s felt like I’ve been writ­ing for an audi­ence, post­ing stuff for oth­ers rather than myself. That’s arse-backwards. A blog should be about per­sonal expres­sion. The moment you start think­ing, and writ­ing, to please oth­ers then it’s a bind; it feels less like a per­sonal exer­cise and more of a job.

A beautiful, thoughtful redesign from Mark Boulton (and a responsive one at that). Go go, read read.

I’ve always sucked at writing.

Not the words, mind you: those usually come easily. (When I remember to sit down and write them, that is; hellooooooo, sad and neglected blog.) It’s more the process of the thing, I guess. It’s a struggle for me to get ideas down quickly; I get intimidated by the promise of that final draft, of shipping, so I often feel every word needs to be perfect as soon as it’s typed.

(No, I’m not going to tell you how long it took to write this fucking blog entry.)

Anyway. So, yes: writing’s hard. But I’m learning how to make it easier. And, alongside a few friends, I’m working on something that might make it easier for you, too.

Last year, I had a long conversation with Mandy. She talked about this idea she had: an idea for a tool that would facilitate conversation, discussion, and, most importantly, iteration during the writing process. Not just an application, actually: more a set of features to support a workflow, one that would, if done right, make writing not just easier, but better.

She and Jason had already sketched out how it might work. Soon after, David joined our merry band, and turned our responsive prototypes a living, breathing application. And Rob joined our team recently, and has been, as Mandy said, effortlessly solving problems we once thought impossible.

I am beyond honored to be a small part of this team, and I can’t wait to show you what we’ve been working on. We call it Editorially, and you can read more about it on our first blog entry.

Stay tuned.

Having a bit of a problem with my laptop lately, and thought I’d write up the problem in case it’s affecting anyone else:

So my MacBook Air (mid-2009, OS X 10.8.3) When my computer wakes from sleep, it doesn’t immediately reconnect to my wireless network. What’s more, if I open up the wireless menu in OS X’s menu bar, it doesn’t show any networks nearby. Zip. Zero. Zilch. It’ll scan for new networks repeatedly, but won’t see a single one.

But here’s where this gets really, really annoying: if I open the Network panel in System Preferences, all nearby networks are immediately visible without delay.

Given the weird inconsistency between the two menus, and that I can reproduce this issue consistently, I figure this is a bug: either with 10.8.3, or with my aging little laptop. Either way, I’d love to fix it. So if you’ve come across this problem and know how a workaround, suggestions via email or Twitter would be most welcome.

Update: Charles Gaudette suggested on Twitter that it might be a couple , and pointed me toward a page showing how to clear out corrupted plist files. Deleting the com.apple.network.identification.plist and com.apple.airport.preferences.plist files seems to have done the trick—thanks, Charles! And thanks to everyone else who wrote in or twittered suggestions at me.