Tap and hold on an Avatar to quickly Follow, Direct Message, Mute, Add to a List or Report for Spam. #TweetbotTip

— Tweetbot for iPhone (@tweetbot) December 17, 2011

The Irish Pub is a true pub. The drinks were cheap but good, the food was reasonable and excellent, and the company was as greasy as the fries (which is a good thing). Contrast that to the “bar” that is inside our resort – where the drinks were $14 each, we had no company, and they didn’t serve food. These types of touristy-flashy places have their place in the world – I just prefer the dives, the diners, and the pubs.

In every city I’ve ever been in the side streets, the alleyways – anywhere off the beaten path – has been where the best places are. This is why Eliza and I rarely plan our trips – we’d rather let them happen naturally by digging into the crevices of wherever we are.

We both highly recommend The Irish Pub. If you see Bill, the guy that looks like Leprechaun, tell him Colin and Eliza said hi. He’s great.

In other words, you have to cause yourself pain before you get healthier, stronger, faster.

I was thinking about this as I was dealing with soreness during some recent runs. As I was running I thought how odd it was that I had to put myself through pain in order to get healthier. You have to push through pain to force your muscles to heal stronger.

Friend and fellow Viddler team member Jeff Johns, who has run the New York Marathon, has an interesting approach to hills which I think is a great example of dealing with pain to get stronger. He says “I go as fast as I can and slow down on the downhill. I love hills, they present a challenge and the faster I run up them the better I feel. No matter what mile the hill comes at, I run as fast as I can up it.”

This may seem insane, Jeff says he likes the dentist too so maybe he is, but think about how our body is made. Our body is made to adjust and fit our lifestyle (within reason). For example, if you’ve never done 50 pushups in a row you’ll find it is pretty hard. However, you’ll also find that after trying to do 50 pushups in a row for a little while – you’ll be able to do them with little problem in a short amount of time. Running is no exception. That very first mile seems impossible and you may actually feel like you’re going do pass out. But, try it again two days later and you’ll be wondering what all the fuss was about. Within 1 day your body adjusts to running and is actually ready to run a bit further than the first time. Within two or three weeks you’ll be running longer distances than you ever thought possible.

This ability to adjust extends beyond pushups and running. Our metabolism also adjusts to fit our life style. Eat smaller meals more often and your metabolism sores and fat drops. Eat bigger meals less often and your body stores fat for the period of time between meals. Your body tries to do exactly what you ask it to do and then sets itself up better for the next time you ask for the same thing.

The point is, your body adjusts and very quickly.

When you’re running, even for the very first time, think of the pain as a sure sign that your body is working hard to adjust to what you are asking it to do. Obviously you want to be conscience of any injuries you could cause – and your body will tell you very quickly if you’ve injured yourself – but in general a little pain goes a long way. Waking up sore in the morning? That is your body healing itself not just back to what it was but better than it was the day before.

Within 4 runs my body is no longer sore and I’m back up to 6 mile runs at a time without thinking about it. It may take you a few more than that, and that is ok, but remember that when you feel pain you have to learn to hate yourself a bit. Push yourself through that pain knowing that tomorrow that pain will not be there and you’ll be able to do more than you did today. If you push yourself until you feel sore every time you run or exercise you will see dramatic progress.

Now, if you’ll excuse me – I have to go hurt myself. A little.

• Use your own API. The very best way to make sure your API is equipped with everything one would need to build something of value is to use it yourself. You will find that by using your own API to build your product you will work out a lot of kinks that would otherwise frustrate third-party developers.
• Remove as many learning curves as possible. An example of this is to provide more documentation than you really need to by writing tutorials and not just flat documents. Code examples go a long way too. Provide “wrappers” or frameworks in common languages that help third party developers to “plug and play” with your API.
• Follow standard conventions. This is related to removing learning curves, but you do not go against the grain. Try to utilize as many standards as possible. Chances are any third party developers that use your API will already be familiar with much of what you’re doing.
• Support multiple response types. Do not assume that third party developers will only use the response type that you prefer. Supporting XML, JSON, PHP, and others is not too much more work and yet has a measurable impact on your APIs adoption.
• Create and keep your own conventions. If you have one way to do things try to stick with it all the way through your API. An example of this would be how Twitter recently added a Lists API to their API and used the very same convention of interacting with that API as they do with accounts. This makes integration of new features dead simple and it will be appreciated.
• Add some brains! If there are common actions that must be taken by all third party developers to interact with your API try to build those actions into the API. A good example of this is Flickr’s support for machine tags. Although a third party developer could do all of the work on their end to work with namespaces, predicates, and ultimately the values they are looking for – Flickr makes it easy by doing all of that work on the server-side. Taking the most common actions and rolling them back into the API will slowly build tremendous value in your API.
• Open source as much code as you can. If you build any tools, frameworks, testing applications, products, or anything that uses your API – try to release that stuff as open source. This will help any new third parties to be able to see real examples of products that use your API. It would also be a good idea to promote open source projects to use your API as well so that the entire development community that you build can benefit.
• Communicate with those using your API. Give the developers a clear path to communicate with you about your API, their applications, or anything they may need to get their jobs done. You will learn a lot about what you are lacking that you may have never thought of.
• Drink a lot of caffeine.

These are just a few tips that I’ve learned in working with Viddler‘s development team to build our API. We’re currently working on the next version of our API, dubbed version 2, and we’ll be making massive improvements to the way that the API works, is documented, and how we use it internally. We’ve learned a lot over the last few years and we’re taking all of the tips above and everything we’ve learned from our development community to build what we think is a much more solid offering.

I hope that if you are building an API you can learn from our experience, our failures, and our successes (and I’ll try to share more of them here). If you have anything you’d like to add about good API design please do so in the comments.

The photo of the fire hydrant has nothing to do with this post but I liked it. It is one from my Lincolnton, North Carolina photo set.

Via Viddler.

Blog posts like this are everywhere. Page through my Photography tag and you’ll see a ton of tips and tricks that I’ve linked to in the past. What separates Kyle’s post from others is that he points out exactly what has helped him, rather than just a laundry list of tips that may help people shoot better.

Oh, and I love what he’s been doing with his photos section. He uploads his photos to Flickr and they are automatically synced with his site in an orderly fashion. Definitely a different approach but one that I think works extremely well.

Here is Veronica Belmont on Tekzilla for the tip.

For those of you not interested in watching the :51 second video, all you need to do is click anywhere inside the graph area and the values below the media types will change.  Pretty slick.

Source: Tekzilla Daily Tip – iTunes – Hidden Bar Graph Views.

I think the most important ones, for me, are perspective, framing, intentional empty space, and the horizontal line.  Everything else seems to fall into place once you follow those few things and really begin to see your photographs before you snap.

Source: 21 Ways to Shoot Better Photographs | 10e20 Blog
Via: Jason Kottke.

1. Backup your entire drive. Some good tips for this step can be found in John Gruber’s “I believe in Murphy’s Law“. In short; create a bootable backup of your hard drive before you install any operating system upgrade.
2. Uninstall anything non-Leopard compatible. There are many applications that you probably have that you could keep, because you know that it will be updated at some point, however there are others that start when your computer boots up that it’d be a good idea to ditch. The first of these may be Unsanity’s Application Enhancer (APE). Either remove this using these instructions or update it to the latest version. Another would be to rename your DivXNetworks folder in your /Library/Application Support/ folder. Doing these two things will ensure that your installation process will go much smoother.
3. Free up enough space. Leopard is going to need somewhere between 6 and 9 Gigabytes of free space in order to install. Leopard won’t actually take that much space once installed, but it will need at least this much space in order to complete the installation.
4. Plug in your computer. If your using a laptop computer I would advise having your computer plugged in during installation. The installation will take the better part of an hour in most cases so you’ll want to be sure to have enough juice. This may seem like a no-brainer but, for some, it isn’t.
5. Have a way to search Google handy. I hope all of your installations go as well as my Macbook’s install but incase they do not, have some way to search Google for solutions handy. There are thousands of people upgrading Leopard or have already done so within these first few days since its release and you can easily leverage their experiences to make yours better.

I’ll be doing a short write-up about Leopard sometime in the next few days but here is the short version; I am in love.