Technology – Page 13 – Chris Koerner

Silence in Open Source Projects

If you contribute to open source projects, or are the sole creator of an open source project, you need to keep talking about that status of what you’re working on. Never stop.

Silence will deter people. Even if your code is super stable. Even if all features have been added. If I see that the last update on your blog/twitter/etc. was a year ago, I’ll assume the project is not actively maintained. That you’ve moved on. That OS updates and/or browser updates will render upon me issues and bugs that will never be addressed. That I should find something else to use.

In a world where OS updates are yearly and mobile apps are updated without interaction, it’s maddening to see open source projects – good, solid, useful projects – go into a sort of hermit state.

Quicksilver went through a period where it wasn’t actively being developed. Now that it’s seen some love, updates are frequent and communication is constant. I know that it’s a living project and something that is being worked on. I can rely on it and treat it as something that is solid and tactile – not infirm or fragile. A feeling I often felt during the ‘dark times’ where it lacked leadership.

Most recently I’ve seen this with the Sequel Pro application. An application I love and use frequently¹. Sequel Pro hasn’t updated in over a year ². Devs say it’s still active, but aren’t communicating that.

I’m not advocating for point release updates just for the sake of appearance. I’m advocating for putting effort into your communication.

If you’re part of an open source project that is actively being developed – even by just a few contributors – make sure it is kept alive. Make sure new users, and existing users returning to see what’s new, know the status of things. Clearly and plainly. If the project is still active, communicate that. If the project is done and mothballed – let us know that as well.

The result is more people using your thing. More people making it better. That’s worth your time.

A Teenager ≠ All Teenagers

View at Medium.com

This article from Andrew Watts, a 19-year-old student at the University of Austin, contains some interesting insights on teenage usage of social media. He speaks from a particular perspective³ and provides some unique thoughts on the various networks in use.

Did you know the first use of the phrase “teenager” to describe a group of people was in 1944? That’s only 60 years ago.

Shortly after reading Andrew’s post, I noticed that danah boyd wrote a great response to Andrew’s post. Her biggest insight ⁴ is that we mustn’t forget that Andrew doesn’t speak for all teenagers.

Andrew is very visible about where he stands. He’s very clear about his passion for technology (and his love of blogging on Medium should be a big ole hint to anyone who missed his byline). He’s also a college student and talks about his peers as being obviously on path to college. But as readers, let’s not forget that only about half of US 19-year-olds are in college.

If you work with young people and are interested in understanding the complex nature of how they approach the same tools you may use (like Facebook, Twitter) then read both. Andrew provides insight into one perspective of social media usage and danah reminds us to keep the keel even. Let me know what you think with a comment below.

Ethan Hawke on Good Sci-Fi

And for that matter, look at the moral conundrums that GATTACA asked – which are right here. To what extent do we really want to homogenize ourselves, when it’s our uniqueness that makes us special – when so many of us, when given the option, would eliminate that? For example – if they can discover dyslexia in the embryo, and get rid of it, many people would choose to do that. And we’d lose Albert Einstein, John Lennon, and my daughter.

Actor Ethan Hawke always puts on a good AMA.

Shubhro Saha on why software engineers should write

Software engineers should write because our craft is increasingly collaborative. Open source projects invite worldwide participation, while industry products often require an army of engineers. (Google Maps has 1100 full-time employees!) Good writing– whether it be in a GitHub comment, code review, or technical documentation– facilitates clear, concise communication for projects like these to move forward.

I’m going to take Shubhro’s essay on why software engineers (i.e. programmers, developers) should write one step further. Everyone should write about their craft. Database administrators, project managers, accountants, plumbers, Wal-Mart door greeter, you name it.

Writing is thinking. Writing helps you to understand your work better. To take a step back from the hustle and bustle and reflect on what you’re doing. You ask different questions about your craft when you take a moment to think and put it down in words for others to read.

Unreachable Time and a Rant Against Voicemail

I’ve been at my employer for over 3 years now.⁵ The entire time I’ve been here my voicemail message has said the following:

“Hello, you’ve reached Chris Koerner. I’m often away from my desk and don’t respond quickly to voice mail. The best way to contact me is to send me an email at me@work.net or if it’s urgent call me on my cell at 314-555-2456. Thanks!”

So, don’t leave me a VM, try my cell or email. I’ll answer my cell from a work-prefix number when I’m at work.⁶ I respond to email in a few hours at most.

My wife finds it amazing that I’m able to do this. That my boss doesn’t prevent this or that I haven’t gotten in trouble yet. Here’s my secret. I never asked my boss how I should make myself accessible and spend my attention. I decided that. He trusts me. I said, for me, the best way to get my attention is via email or cell call. Voicemail sucks.

Short of that. I’m unreachable. I think that’s important. Even with all the responsibilities I have and all the various ways to get in touch with me, sometimes I will not be available. I might be busy with a big project and a deadline. I might be in a meeting.⁷

I’m still accessible – even faster than voicemail! – and I’m polite about it. The important thing for me is making sure that the time I have allotted to get work done is as productive as possible. I use the tools I have – email, phone, IM – in the best way possible. To me, being accessible via voicemail is the same as being accessible via fax. Ancient, cumbersome, and a pain for all parties involved.

Voicemail is slow. Like most folks I read much faster that someone can talk. If I’m familiar with a topic I can quickly read an email and respond.

Voicemail also introduces ambiguity. Did they say ‘Six five seven two” or “Six five six two”? I’d have to play back the message if I missed a number, address, etc. ⁸

The tools we use should make us more productive and efficient. We should delight clients and co-workers with our responsiveness. Clunky, outmoded tools like voicemail don’t help us. I encourage you to look at how you’re using things like voicemail and see if there isn’t a better, more productive and friendly way to manage your attention and time.

Leave me a ~~voicemail~~ comment with your own ideas.