Assembled in Philadelphia

Author: zjs (Page 2 of 6)

Smart Guy Productivity Pitfalls

Brian Hook writing about Smart Guy Productivity Pitfalls:

I remember Carmack talking about productivity measurement.  While working he would play a CD, and if he was not being productive, he’d pause the CD player.  This meant any time someone came into his office to ask him a question or he checked email he’d pause the CD player.  He’d then measure his output for the day by how many times he played the CD (or something like that — maybe it was how far he got down into his CD stack).  I distinctly remember him saying ‘So if I get up to go to the bathroom, I pause the player’.

You know what’s pretty hardcore?  Thinking that  going to the bathroom is essentially the same as fucking off. 

This article is great, Hook is right once again and has more to say so read the whole thing.

There are exactly two things, in order of importance that have helped me be productive about the things I care about:

  1. The Back to Work podcast.
  2. OmniFocus for iPhone.

The Back to Work podcast has taught me a lot of important lessons. Like not giving up on something that is important to me just because I miss a day in the schedule. For a repetitive task like exercising or learning a language this is essential to making progress. You will screw up and miss a day, but it’s OK because tomorrow you can just go back to it instead of giving up entirely. I don’t explain it half as well as Merlin Mann, so go listen.

The podcast also pointed me to OmniFocus as a good step in “Getting Things Done.”

In OmniFocus I have a bunch of tasks to do each day, I spend most of my time with it in the Forecast. That view  looks like this:

OmniFocus Forecast

There is more to it, of course, but as a basic method of tracking that I have some things that needs to get done each day, OmniFocus is perfect. There are folders that I use to track tasks for projects and other features, but you don’t have to use half the features of this thing to reap some benefit.

You could probably do the same thing with another TODO list, this one has some other features that I like such as geofencing where it pops up when I am near the grocery store to let me know that I need to buy cereal.

Getting rid of all that junk swirling around in the toilet bowl of the mind so that you can work on the things that matter instead of constantly coming back to wondering about if you have enough Lucky Charms to get through the week is awesome.

I still need to read the actual book (Getting Things Done: The Art of Stress-Free Productivity), but so much of this stuff is easy to get started on before reading a tome full of business-speak.

Writing for LinuxGames

After a brief hiatus (4 years!) I’m writing for LinuxGames again. My byline on that site has changed to “TimeDoctor” to jive with TimeDoctor Dot Org, my home of late for dozens of gameplay videos.

I had first started writing for LG in 2000.

The editor-in-chief, Dustin, and I happened to be in the IRC channel for Loki, where the developers behind the biggest success story in Linux gaming would dole out beta access and generally carouse with anyone interested in their games. That’s where I hounded Dustin to let me write for LG, and eventually got the job. I don’t really recall what my intentions toward writing were. Just that I enjoyed doing it and reading the output of other gaming sites like Blues News, sCary’s Shuga Shack, and loonygames. I guess that I needed to find a niche to excel and channel some creative output in.

If you had told me then that Valve would eventually be on Linux through a digital distribution platform of their own creation I would have asked you what a digital distribution platform was and wondered what it might look like. That it would take 13 years to get there seems even more ridiculous.

Loki’s idea of jumping the gun straight to boxed copies of games that were released much later than their Windows counterparts wasn’t long lived. They were pretty much the first and last to do it with the community behind them, despite the best efforts of Linux Game Publishing.

There were a few ethical mistakes at the time that I regret. Being both press and an unpaid beta tester for Loki. Although I was able to separate out the difference in attitude and style when writing reviews, and to my recollection none of the readers ever questioned it. I can’t help but feel It would have produced a better article if I had gone in fresh, and when Loki got weirder during their downfall I felt really creeped out by having to justify my requests for review copies to them. My e-mail archives don’t go back far enough to let me know if I guaranteed a “good review” but what I can remember was not cool. As the only site for coverage on the topic it seems even more ridiculous in retrospect that those discussions had to happen at all.

Beta testing at Loki lead directly to my career in Quality Assurance (at Microsoft of all places) and creating a site called Game QA Blog where some friends and I wrote about QA in gaming for a while.

Writing for Linux Games got me a role as a technical reviewer on Linux Game Programming. That book only seemed to exist to compete with another book called Programming Linux Games. We beat them to the punch on the better title, but they had far superior content.

At one point we had a podcast going, but it was short lived due to conflicting schedules. I helped transition the site from an aging custom content management system to WordPress. Pushing for the site to modernize made me stop waiting for anyone else to do it and make twitter and Facebook accounts.

Once my career got off the ground I started writing less and less for LinuxGames but I attribute most of my success to that site and the friends I made through it.

As an aside, I now host loonygames’ archived site on my DreamHost account after Jason Bergman, the titular “loonyboi,” put out a request for help in the past year or so. Jason wrote about it on his tumblog.

With all of the success Linux gaming has had recently it is great to be back at LinuxGames. Even if most of my posts today are written on my Mac 😉

Once you go Mac

Miguel De Icaza:

While I had Macs at Novell (to support Mono on MacOS), it would take a couple of years before I used a Mac regularly. In some vacation to Brazil around 2008 or so, I decided to only take the Mac for the trip and learn to live with the OS as a user, not just as a developer.

Computing-wise that three week vacation turned out to be very relaxing. Machine would suspend and resume without problem, WiFi just worked, audio did not stop working, I spend three weeks without having to recompile the kernel to adjust this or that, nor fighting the video drivers, or deal with the bizarre and random speed degradation that my ThinkPad suffered.

Right on the money.

This mirrors my own experience, except for the trip to Brazil.

I had been a pretty big proponent of Linux on the desktop since about 2001.

Some time before that I had my first experience with Linux that was mind-boggingly stupid. Win modems.

My first Linux was RedHat 5.2 in the late ’90s. To get on the internet from home you had to dial-out.

Most computers at the time shipped with the cheapest modem you could find. Unfortunately, the price for cost-reduction was compatibility. These Winmodems needed extremely custom software to operate that replaced most of the expensive hardware with software which was only available in Windows.

Old hat, I know but the frustration of having incompatible hardware and software is a constant theme in Linux and the stories of folks who switch away.

When I knew a Linux machine couldn’t serve me anymore I went to the Mac. Where my kernel doesn’t need recompilation and my boot loader doesn’t tend to explode when I try something new.

With the Mac’s rise to the challenge of courting Unix lovers I hope that Linux developers who have stuck with it will start to compete by making better designed software that is more welcoming to new users.

Free only goes so far.

What is Online Community Management?

For about five years now I’ve been a professional online community manager. I’ve been doing it unprofessionally since 2001 or so when I first started working on free software projects.

There are two big misconceptions that have spread about what community management is and I’d like to correct them with these four points of discussion.

Community management isn’t marketing.
I won’t pretend to understand everything about marketing. I have written press releases and participated in interviews with journalists as part of my job. That is in addition to many other non-community functions I’ve done at smaller companies.

This is the biggest misconception I’ve found in job listings and much of the published material supports this idea that community is all about marketing. Marketing has a place, and I love working with good people in it. This is not that and the best marketing directors know it and will respect the difference.

The reason why there is more documentation on community management and social from the perspective of marketers is due to those folks being better at selling their message. I’m often glad that I am not as good at selling myself and my message, but I’ve had to become better at it to get my point across.

Instead of marketing…

Community is about building a relationship with an audience.
The most effective strategy for player or user retention is to develop real and honest friendships with the VIP/rockstars/etc of the community. That is it.

Metrics of Facebook Likes and twitter retweets have their place, but those numbers won’t keep people coming back.

Your role as a community manager can’t be solely about monitoring metrics and “engaging influencers” with cat pictures and contests relevant to your “brand”

If you are detached from the community and operate solely as a corporate entity doling out nuggets of information on a schedule your company’s biggest fans will wonder who is behind that twitter account, Facebook page, or anonymous forum name. You will never connect with them and when they leave the community you won’t know why.

Community management is about creating a space for community success.
Sometimes all you have to do is enable the VIP/rockstar community members to do what needs to be done. Then you will be able to step away and lurk for a while.

It’ll be difficult, but it is extremely important for their growth and the growth of the community as a whole. If the community can’t self-moderate and let you work on the big-picture for some of the time, you won’t ever get to help them take bigger steps forward.

Some of my favorite communities have had people that I learned to trust as they could contact me when something was wrong with the product or service before analytics and operations knew about it.

It isn’t your community.
Finally, there is a dangerously stupid idea that the community is something the company owns.

The community formed around the product or service organically and will dissolve and move on with or without you and your Klout score if you fuck up.

Listen to the community instead of just counting them. Relate and befriend the community instead of “engaging” with them. Empower the community and step away sometimes to let them grow.

The most satisfying part of the work is being part of a bigger community of people and helping them to continue to exist and keep their friends in the community that they have built.

You don’t know it, but your FOSS game project has a deadline.

Bart at Free Gamer:

“Your number one duty to your pet FOSS game project is to get it into a playable state without giving up.  If you miss your deadline, whenever that may be, you’re consigning your idea (and your time) to the graveyard of projects that never saw the light of day.  Make your project playable and get it out there, and it has a much bigger chance of succeeding in the long run.”

Amen, brother.

« Older posts Newer posts »

© 2020 Zachary J. Slater

Theme by Anders NorenUp ↑