Throughout my years as a developer and programmer, I've worked closely with many technical people, where I regularly required their assistance with everyday, work-related issues or problems. Even close friends or contacts of mine are technically-inclined, especially friends made through social networks, where it's my goal to meet like-minded people.

I realize there's that double standard going on when it comes to helping people with technical troubles. I've been on both sides of the fence. I've been annoyed at user's constant requests for piddly things (at least, things I think are piddly). I've also been in dire need of help, and been treated like my problem was piddly, with little or no help from others.

So I can accept that I can't expect superb help every time I need it, when I myself may have inadvertently treated others poorly.

The difference, though, is that I always go above and beyond to help someone. I don't just supply a two-word answer, or tell them "It works for me," and then ignore them. Sure, initially, I may provide a quick answer, because perhaps I'm in the middle of something, or maybe the user really is annoying and the request is piddly (if you asked most people, they'd think it is piddly too), but the difference is I will always follow up, no matter how piddly that user's issue seemed. I'll take the extra step to make sure the user was able to figure it out. Usually that means just stopping by and saying, "Hey, were you able to figure that out?" Just that extra level of care is what separates helpful people from unhelpful people.

I can usually tell pretty quickly who is helpful and who is not.

Helpful

Those that are helpful, I am comfortable pointing out bugs or issues that probably originated from their own efforts. I can simply say, "Hey, there's a bug on this page." Rather than getting defensive, they'll welcome the opportunity to fix something that they may have overlooked. They don't necessarily like bugs, but they enjoy challenges. This is the mark of someone who really loves what they do.

Those that are helpful also linger until the problem is fixed. This could be perceived as good or bad. They can often become overly helpful and continue to press the issue, when perhaps you just wanted a quick answer.

You know the type. They'll stand there by your computer while directing you to open a certain page or process, so they can look over your shoulder at the source of the problem. Eventually directing you becomes too difficult, so they'll completely overtake your computer.

Although this may seem annoying, this is a helpful person. They'll stay there with you until it's completely resolved, even if it means getting really behind on their own work.

Unhelpful

Those that are unhelpful are typically unapproachable. The slightest question will outwardly irritate them. Perhaps they don't come out and say they are irritated, but you can tell by their body language and response. It's like your completely interrupting something so important.

The most common response from an unhelpful person is:

"It works for me."

Unhelpful people will always find the gray area where they are neither right nor wrong. It's just enough to get you off their backs.

What are you?

It might be wise to consider what category you fall under. How do you respond to questions or problems directed at you? Do you immediately get defensive or argumentative, or are you open to hearing the person out?

It takes a certain amount of character to admit that you're wrong. Those are also the people I admire the most - selfless and caring.

I don't want to come across as the "morale police" here. I am not suggesting that I have never been unhelpful. We are all guilty of being unhelpful from time to time. However, if you try to be more helpful overall, you'll be doing a lot of good for those around you.

Feedback

When creating applications using API's, I tend to follow this mantra:

"Find out what's lacking, or could be improved upon, and use the API to create that."

With Brightkite's API, I have a few ideas for applications that could extend the usefulness of the service:

• Scheduled check-in's. Each weekday I usually check in at the same places, at the same time. Perhaps such check-in's could be automated, occurring in the background, not requiring my input or attention.
• Enhanced Twitter integration. Designate whether each check-in actually gets sent to Twitter. Sometimes I just need to update my location, and not necessarily "broadcast" it.
• Checking out of a location. Sure, you can check-in, but what about that gray area when you leave a place, and have yet to arrive at another place?

All three ideas could be created using the Brightkite API. I may opt to create one or two myself.

Feedback

Since I've started using GrandCentral, I've been a much happier telephone user. But the interface needs major improvements if GrandCentral ever wants serious adoption. There hasn't been a single front-end change since Google's acquisition.

The most glaring hole is lack of https. I'd feel a lot more secure if my sessions were encrypted, rather than possibly exposing my login credentials, allowing access to sensitive voicemails.

I've also noticed that older voice messages (anything older than four or five months) no longer play. It shows the message, but says it is 0:00 in length:

So much for never having to delete a voice message, eh? It seems they delete themselves.

I've also noticed strange looking URL's. For example, when I go to page two of my inbox (the screen showing my voice messages), the URL changes to:

http://www.grandcentral.com/messages/page/2//

The two slashes on the end makes it look like something is incomplete or broken.

It appears the entire interface is in need of a major overhaul.

I'd like to claim that I'll stick with GrandCentral forever, but to be honest, if a similar service comes along with a more fine-tuned experience, I won't hesitate to switch.

Feedback

I've never been enthused about contact manager applications - for example, within Gmail, or on my iPhone. I just can't get excited about organizing my contacts.

I think this is because, contact managers applications, by nature, are full of flaws. The larger your contact list grows, the more confusing it is to pull information from.

This is because the term "contact" is too vague. A "contact" could be a person, a place, a web service, etc.

You may not have all the information for a contact, so every contact appears differently. Some have a complete first and last name. Some just have a first name. Some just have an email address. Some are a name of a place, not a person.

Sorting all that information is never accurate, because there's never one field that is always filled in.

Duplicates are easy to create, since contact apps usually don't require any fields to be totally unique. For example, my Gmail contact list has numerous duplicates - the same person under different email addresses.

Some contacts I don't even recall how or why they are my contact. Perhaps I emailed the person once, three years ago, and never talked to them again. Should they still be in my contact list?

Then there's the problem of syncing. I have a contact list on my phone, another one on Gmail, and probably a few more elsewhere. None of them contain all of my contacts, but all of them contain some.

Some contact apps are web-based, providing me access anywhere with an internet connection. Others are client based, meaning I need to be using that device or machine. Unfortunately, I'm never near the one I need.

The emergence of social networks hasn't helped either. For every social network I am a part of, I have a different list of "friends" or "contacts." If I need to touch base with a particular person, first I have to remember which network I know that person from.

Altogether this leads to an organizational nightmare, further complicating the concept of "keeping in touch."

Unfortunately, I don't have an answer to this problem, or any ideas on how to improve it.

Feedback

This is absurd. Here's what a I want, and what Twitter will not allow:

Every day, I want to see the tweets I posted exactly a year ago, this date. From what I can tell, there is no way to specify a date in an API request. There are two methods that appear to do this: "since" and "since_id" - but neither of them work properly, nor make much sense. I don't want to see tweets since a certain date, I want to see tweets created on a certain date. This should be a simple parameter, something like:

http://twitter.com/statuses/user_timeline.rss?post_date=2007-07-12

Nope, that would be too easy.

There is no way to access tweets other than your most recent 200. (Or whatever Twitter is currently allowing - 200 is generous lately...)

What good does that do? I have almost two years worth of daily content posted to Twitter, and I can only see my most recent 200, which would probably equal the past two weeks for me.

I try other tools like Summize and Tweetdumpr, and they too are limited to how many tweets they can pull.

This is just not cool, and really limits things from a conceptual point of view. Twitter is just an entity, but my tweets are my tweets. I should be able to get them all whenever I want, and not be given an excuse that Twitter's servers can't handle it. That's not my problem. Give me my tweets.

I would be willing to pay for the service if they just fixed the damn thing.

Feedback

Back when Jim Thome played for the Cleveland Indians, he had a phrase, or a mantra, if you will:

"Don't believe the hype."

I believe he had that abbreviated into "DBTH," and written on his helmet, or something to that effect.

The phrase is one of my favorites, and often comes back to me, as I go through life and make internal decisions on what's really important, and really worth getting hyped up about.

Today the phrase stood out quite apparently, bouncing around in my head as I approached the Apple Store on Michigan Ave in the early morning sunshine.

As I glanced at the hundreds of people waiting outside the store for the 8 AM opening, I realized I was only looking at hype. These people weren't in line for a true need, like when you need food, or need a job. They were there because of a manufactured inner desire that was strategically given birth by extremely intelligent promotional genius.

The problem with hype is that it's short-lived, and it messes with your head. When you immerse yourself in hype, your normal, rational decision-making processes aren't functioning. Much like "love is blind," so is hype. And similar to love, eventually hype fades. True reality sets in and your affection and passion for whatever the hype was directed towards lessens.

As much as I love "iPhone release days" and the endless Apple hype machine, I still try to base purchases on needs, not hype. I try not to let hype make purchasing decisions for me.

I own an iPhone already. It's only a year old. What God-for-saken reason do I have to buy a brand new one, when there's nothing wrong with the one I have?

Being smart with your money means being able to tell the difference between needs and wants.

Here's to my discipline so far. Let's see how long this theory lasts. Will hype overcome me, or will I remain steadfast in my ideals?

I hate you Apple.

Feedback

I've always had an internal debate (OK, sometimes it's external) over JavaScript and Flash "widgets" that sites let you embed onto other sites.

Benefits are it's an easy way to quickly provide cross-network content, with minimal development skills required.

Drawbacks are that widgets often look tacky, and can sometimes break your page layout. They also slow page loading because if the server to be reached is slow or down, it affects the sites you embed onto.

Rather than using the pre-built widgets that some sites allow, I've become accustomed to grabbing that same content via the RSS feed. In a sense, I parse the RSS feed using a server-side language (PHP, in my case), then spit it out onto my site, all the while keeping the content appearance as if it's coming from my own database.

I find this approach more flexible, but I still ache from the page loading problem. The content still has to be accessed from another server, which could potentially be down. (Let's face it, in Twitter's case, being down is a frequent occurrence.)

Service like Gnip intrigue me, because supposedly it can handle the overload of API requests without hiccup. This is a fascinating idea that I'd like to see become a reality, with all the cross-network stuff going on these days.

Consider Gnip the Amazon S3 of API requests. Gnip scales with your application.

Imagine a world where data can be smoothly passed back and forth from one network/server to another without latency or throttling. This would benefit everyone involved: developers, application creators, and users.

Feedback

Shortwave is similar to Firefox keyword searches, except as a JavaScript bookmark, it is browser independent. This is useful if you use many different browsers, or just wish to have a central list of functioning keyword bookmarks.

Although, I don't like having to manually click on the bookmark before typing in my keyword search, but I suppose I could get used to it. The nice part about Firefox keyword search is that it allows you to use the address bar, which is where you'd type in your URL anyway.

However, I like the idea of having my keyword searches accessible regardless of the current browser I am using. In a way, this makes my keyword bookmarks portable and future-proof.

Also, it's an absolute must for iPhone/iPod touch users. It will save time typing, as well as reduce page loading time over the slow EDGE network, by bringing you directly to the search results page, rather than first going to the search page, then the results.

Create your own custom Shortwave

Creating your own Shortwave is easy. Just download the default waves.txt file, edit it with your own bookmarks, then upload to a web server of your own.

Go back to the Shortwave home page, and paste the URL to your waves.txt file into the box.

Sync your iPhone/iPod bookmarks

On your desktop Safari, drag the Shortwave bookmark to your bookmarks toolbar. In iTunes, sync your bookmarks to your iPhone or iPod touch.

You'll then have a JavaScript-prompt bookmark saved on your mobile device, ready for your keyword searches.

Feedback

Brightkite recently released a feature that allows users to customize their updates that get sent to Twitter.

Here's a standard Brightkite update on Twitter:

I'm at 150 N Michigan Ave, Chicago, IL 60602, USA http://bkite.com/977U.

If you ask me, this is rather bland. It sounds like a computer talking.

I've decided to make my Brightkite-to-Twitter updates look more human. I've converted the above example to:

I'm at or near 150 N Michigan Ave, Chicago, IL 60602. Say hello if you're here!

First, I added "at or near" since I'm not always exactly at the place when I update. "Near" means I could be just arriving, just leaving, or somewhere around the area. I've also added a personal touch to the very end: "Say hello if you're here!"

I use Brightkite and Twitter to meet people, after all. I want people to know that I'm open to meeting anytime, so don't be afraid to walk up to me and say hello.

I also removed the link at the end which normally takes you to the Brightkite site, with a map displaying exactly where I am. I've decided this is not necessary for Twitter. If you follow me on Brightkite, you have full access to the map already, so there's no need to send that to Twitter as well. I just want my Twitter followers to get an idea where I am. Doesn't have to be so precise with the map link (which also takes up extra characters in the tweet, so removing it saves room for other text).

Feedback

When I developed Twordy, I did so with the intention of filling a need - being able to post as much content as you'd like, while still taking advantage of micro-blogging services like Twitter.

This is especially useful for those that don't want/need to maintain a traditional blog, and already have a growing group of followers on Twitter.

I'm really not expecting this idea to take off and be a huge hit, but what I do expect is similar services to hit the web which mimic Twordy's concept.

One such service, called TinyPaste, does just that. You can copy/paste, or type directly into a text box, and then submit your content. You then receive a permanent URL for pasting into micro-blogging services. Essentially you're writing your content elsewhere, and just linking to it from micro-blogging services that would otherwise have limited the amount of text you could type.

This is no different from writing a separate blog post, and then linking to it on Twitter. The difference is that services like Twordy and TinyPaste remove the complexity and overhead of traditional blogging systems. They simply reduce the number of steps it takes to write content and share it - taking advantage of your micro-blogging network, which is already established and probably growing.

I think we're going to see more services like Twordy and TinyPaste, as social networks become more prevalent and necessary to conduct relations of any kind.

Feedback