Carl T. Holscher fights for the customers.

Category: Observations Page 53 of 90

Coffee by Justin Leibow

Opinions

There are tons of things going on in the world. There are uprisings in the Ukraine. There are human rights violations in Russia and North Korea. There are celebrities screaming for attention to their latest hi-jinx. There are sports teams playing well and doing poorly. There are movies. There is music. There is art. There are books and magazines, blogs and forums. There are millions of things to care about.

Often, people ask what is your opinion about…? But rarely is it worth having an opinion on everything. It’s perfectly OK to just not care about things. You can’t have an opinion. You can say I Don’t Care.

I have opinions on things I care about. I have opinions on things I know enough about to understand. I have opinions on things I’ve taken the time to think about. If I haven’t, then it’s not my opinion.

It’s my parent’s opinion. It’s my friend’s opinion. It’s my news channel’s opinion. It’s everyone’s opinion but mine.

So next time someone asks you for your opinion on something. It’s fine to tell them, “I don’t have one.”

Sheep

You are not the intended audience

You are not the intended audience.

Now that the world is universal, we are becoming unintended audiences for everything. We see all sorts of messages and posts on our social mediums. It exposes us to things we’d never dreamt of before. There are vast differences of opinion on the international communication medium.

And we are not always the intended audiences.

This is a good point that’s worth repeating. I’m a straight white man. The strength and acceptance are not for me. I don’t need them. They are for those who need the support.

It could be someone telling others he or she is gay. It could be someone coming to grips with depression or anxiety. It could be someone joining or leaving a church. These are personal choices. These are personal experiences. We share because it’s liberating to share a truth. But also because of the best thing the Internet ever did for us.

Remind us we are not alone.

No matter how alienated I felt growing up, I knew there were other people out there who were like me. No matter how much I feel alienated, I know I am not alone. That’s a powerful message. And an even more powerful feeling.

You Are Not Alone.

So next time you see someone coming out they’re not doing it for you. They’re doing it for them. And if that helps you, great. But if not, then ignore it and go on about your day. You are not the intended audience.

Single Point of Failure

I am the single point of failure for my organization.

There is no one else in the organization that can do my job. There is no one else who can step up and take up the slack or fill my absence.

What happens when I get sick?
What happens when I go on vacation?
What happens when I leave the organization?

What is the backup plan for any of these scenarios? There isn’t a backup plan. If I am not in the office, manning the phone and email inbox, those emails and calls go unanswered. Or fall to people who cannot help.

A good friend recently told me,

“All you can do is all you can do, and all you can do is enough.”

We often talk about backups for data. I preach that if it doesn’t exist in three places, it doesn’t exist. But what about people? Where are the backups for people?

It’s great that you work hard job and have a set of specialized knowledge. Who else has that knowledge? It’s wonderful that I’m an expert on a certain application? Who else can I share this knowledge with? Who else can I teach? Where can I write what I know so my knowledge becomes institutional knowledge.

When I call out sick or when I move on to another job, what happens to my expertise? Where does what I know go?

If it’s lost, that’s a terrible blow to the organization where I worked. If I’m out sick and no one else can pick up the slack that’s a terrible blow.

People need backups just like data. Where are the single points of failure in your support network?

How can you tell where those spots are? Listen to what people say. Do you hear things like this?
“We can’t do that, we need Bob here for it.”
Tim is the only know who knows how this machine works.
Make a note of that. Those are the people you need to back up.

Encourage Bob and Tim share their knowledge. They need to train others on the machinery or in the systems Bob and Tim know. They don’t need to become experts overnight, but they need to start.

Even better than training someone, write things down. Start a wiki. Write document. Share it. Put it somewhere safe. Also be sure to back that up.

You know what’s worse than not having any documentation? Having documentation locked away on someone’s computer. Make sure the documentation lives somewhere accessible within the organization. If Bob leaves then IT wiped his computer and all his notes were there, it’s just as bad as never writing any of it down.

Unfit for print

What you don’t write (or publish) is just as important as what you do.

This past week I’ve written two posts. They were both good posts. They had some good information but they will never see the light of day. They go where posts go that aren’t fit to print, into my journal.

They weren’t right because I wasn’t in the right head space when I wrote them. The first was a half-rant about how some things have gone in life. It was vague and didn’t name offending parties But if you knew me, you’d know what I was talking about well enough.

I asked a couple of trusted friends and they both raised red flags. Thanks guys.

The second post was something I’m often asked so I thought I would write-up how to do something specific. But as I finished it, I thought better of posting it for a few reasons. Nothing terrible but it might not be something I want to share with the world. So again, I asked my trusted friends and they said no. Less emphatically than the first time, but still a solid no.

Sometimes it’s more important not to press publish than it is to publish. Taking what I’ve learned and been thinking about this week, allow me to share some thoughts.

What to think about before you press publish

What you say online stays online.

Everything I publish will stay online forever as far as I’m concerned. Google will crawl the new post and cache it on its servers. Archive.org may pick up the piece and store it away for all time. One of my readers may print, screenshot or copy parts it to quote in another post. Once I pretty publish, I have no control over what happens to my words. They are out there in the world to be read, captured and shared.

So before I say anything, I better be quite sure I want to say it and I want to have my name on it.

Don’t write about work

Before you write anything at or about work, consult your employer’s social media policy. My rule of thumb is never to write about work. I used examples of how I’ve helped people in posts but they’re unidentifiable people. And I only write about them in a positive light. Never bash your employer. Never talk bad about a co-worker. You never know who is reading your words. What you say could lead to getting fired of worse. It’s easier to not write about work.

Would you say it to their face?

Don’t write anything you wouldn’t stand up and say to the person’s face. It keeps with my general rule about not writing nasty things about people. But if you’re tempted, think about it. Would you stand up and say it to their face? If you wouldn’t say it to someone, you shouldn’t write publish it.

Don’t write about illegal things

I’ve seen people posting about their drug use on social media. The same goes for underage drinking. Those seem like obvious examples. But some less obvious ones may be piracy of media or software. Whatever your feelings on the topic, it’s still illegal. Don’t write-up how you pirate movies and TV. Don’t share that. It paints a target on you for law enforcement.

Think about future employers

If you’re not job hunting now, you will one day. It’s a reality that your future employer is going to search your name in Google. Try looking yourself up. What are they going to find? Pictures of you drunk at a college party? Posts about your drug use? How is that going to look to someone considering you for a job?

Write Angry. Edit Later.

It’s good to write when you’re fired up. The words fly out of your fingers. The idea is burning to be let out. The story is taking shape and it’s going well. Harness that. Write. Keep writing. Get it all out. But don’t hit publish yet. Wait. Step away. Save your file and come back to it. Read your words with a cooler head and make sure you still want to say what you wrote. Writing in the heat of the moment can be cathartic, don’t let it come back to hurt you later.

I am not trying to tell you what to post. I won’t pretend you care about my rules. But it could lead to trouble and these are some guidelines I’ve tried to live and write by and hopefully they’ll help you out too.

This also applies to writing at night. I have a strict rule that I don’t start any projects after midnight. I’ve made some big blunders with my web site or trying to repair a computer because it was 1am and my quick 20 minute project was approaching its third hour. The same goes for my writing. I love to write at night. But once I do, I edit in the morning. This allows me to spend some time away from the piece. It also means I’ve hopefully slept a few hours and can look at it with fresh, awake eyes. That great idea you had at 2:45am doesn’t always sound as good in the harsh light of day.

If you can’t say anything nice…

My mother always told me if you don’t have anything nice to say, don’t say anything at all. Those words ring in my ears when I am stressed or upset. There is a place for those words. Those words can go into emails unsent or journals unseen.

It’s good to get those feelings out. But you can do so privately. Not everything needs to be public. We’re in an age where the default seems to be public. The default is not public. The default should be private. Then let the public see what you decide to share. Not the other way around. That’s when you get into trouble.

Recently, I was about to hit publish on some things that, looking back, I was not proud of. I am glad I had a friend I could ask and get their honest thoughts about. If you’re unsure, ask a friend. Have someone you trust take a look at what you’re writing and ask them about it. Should you post it? Sometimes the answer is no.

On Self-Hosting

I predict 2014 is the year when we see more popular services go away. Either because they’re unsustainable businesses or they’re bought up and immediately integrated into larger companies. Either way, they go away and all we’ve left with is a message saying how much we, the customers, mean to them.

Because of this I’ve started to bring some services in-house and run them on my server. The following tools are what I’ve chosen to use.

Author’s Note: I am not saying they are the best thing out there. Nor am I saying they are perfect for you. They’re just what I use. I use them. I like them. You may not.

With the pile of services that will host your text and images, I still prefer to host my blog. Congratulations! You’re here.

Blogs

Tech in the Trenches is hosted on a WordPress installation I run off a Dreamhost shared server. I’m not fancy.

With the recent demise of Google Reader and Feedly’s questionable decisions, I’ve decided to host my own RSS reader. Sure, there are plenty of good ones out there. But it’s not something I care enough about to pay for.

If I didn’t have RSS, life would go on. I would go back to keeping folders of links just as I did before RSS. I would also use the various social media networks to let the good stuff bubble up from the muck of the Internet.

RSS

To that end, I found TinyTinyRSS and decided to install it.

It’s small, flexible and has a plugin community around it. But the reason I found it is Dreamhost blogged about installing it. What’s easier than that?

So a few minutes after reading the post, I had TT-RSS setup.

Once it’s running I would recommend finding a different theme as I don’t care for the default. I’m using the Feedly theme out of habit. There’s also a Google Reader-style theme if you want to relive the glory.

While there is a native Android client it didn’t help me out on iOS.

To get it working on my iPhone, I am using the Fever plugin. This allows TT-RSS to authenticate as if it were Shaun Inman’s Fever. It works with Reeder, which I use. It also supports Mr. Reader and ReadKit according to the developer.

To make this work you have to enable API access in your tt-rss account preferences (Preferences -> Enable external API) before using the client. I missed this step and couldn’t figure out why it wouldn’t work.

Analytics

I don’t keep a close eye on my analytics. But I am curious every now and again when I get more than a few hits on a post where the traffic comes from.

Piwik works well for me. It gives me what Google Analytics provides without the threat of it going away.

Photos

This is almost constantly in flux. For years I used Gallery. It was stable and robust. But then it grew bloated. I prefer smaller tools and went looking for an alternative.

I decided on Piwigo. It feels lighter to me. I don’t a complex set of tools. I want a place to make albums and show them off. That’s it. It’s simple and it works for me. If you’re a Dreamhost user, both of these are available as one-click installs.

I’ve also been flirting with TroveBox (formerly OpenPhoto). They have a hosted option that will use your own storage but also charges a monthly fee.

They provide downloads and documentation to get the software setup on a variety of server setups.

GIFs

Yes, I keep some animated gifs at my disposal. To do this, I use Eat My GIF. It’s a ridiculously simple drop-in installation and now I have a place to throw GIFs to deploy as needed. Yes, I realize this is very silly. But I like it and it’s developed by a friend.

So don’t hate.
Hates Gonna Hate

What I’m not hosting

Email. I have no desire to run my own mail server. I use Gmail and am perfectly happy with it for now.

Social Media. I see the value of a distributed social media network. However, I am happy with Twitter/App.net/Facebook. I don’t need anything else.

I tried out Tent in the form of Tent.is, which now appears to be Cupcake.io, for a short time but I’m not enough of an ubernerd to hack it.

OwnCloud I had running for a while. But I found I didn’t really use it. Dropbox is still fine for me. It’s on my radar and I may use it again for something. But I just don’t have a need for it.

It’s easy to get carried away and start hosting things I don’t need to host. It makes more work for me to support and keep it updated and working. Sometimes the trade-offs are easier letting someone else do the heavy lifting.

Just because I can do it, doesn’t mean I should.

Are you all self-hosting anything interesting? Tell me about it over on Twitter or ADN.

Page 53 of 90

Powered by WordPress & Theme by Anders Norén