Skip to main content

The Stuff You Didn't Get Around To Read


Don't you think it's hard to keep up with everything going on out there?

You probably think there's not enough time in the day to dig into the latest things going on in IT, science, games, sports, politics, finance, or whatever your interests are.

Not to mention all those great books you got off Amazon, which are just stacking up. Maybe you got a Kindle or a tablet to help you get more reading done.

And then there are those 200 videos from that awesome conference on Vimeo for free! Will have to dig through them soon.

In a vain attempt to trick yourself into believing you'll get around to consuming all the material, you star it on Twitter. You tag it for later. You add it to Instapaper. Read Later. Watch Later. An ever increasing backlog of information you want to absorb, but the truth is that you'll never catch up.

What if I were to say: You do have the time. You're just not using it right. You're trying to consume good information, but you're using the wrong channel: the visual channel.

Now don't get me wrong, your eyes are great for absorbing information. The problem is that your eyes are already busy most of the day. Busy driving. Walking. Shopping. Doing the dishes. Cooking.

Your ears, however. Now that's a different story.


Your ears are free most of the day, as long as you're not in conversation, or concentrating. Think about the commute to work. That's 1-2 hours of time where your eyes are mostly busy.

This is time you should use to get through your information backlog. Hence, the alternative title of this blog-post is..

Why You Should Listen to Podcasts

Maybe you take the train/bus to work, and you think you're already getting plenty visual time to read when you're on the go. But do you really? How much time of that trip are you actually sitting down, have both hands free, and the concentration to read something? For me that's maybe 10-20 minutes of the 40 it takes me to get to work. The rest of the time I'm walking between transit or standing in a cramped train.

Listening to a podcast instead, I get 40 minutes of listening out of that trip. And again on the return trip.

I take my daughter for an hour's walk in the pram in the evening. She's mostly busy sleeping, or looking at stuff, so that's another hour of listening.

And later on when I'm cleaning up the kitchen and around, I usually get another 30 mins or more.

All together, that's nearly three hours of listening in a day. Three hours of learning. Three hours of entertainment. Time which would have been kind of wasted otherwise.

But how do I listen to podcasts?

You probably already have a smartphone. More or less any Android or iPhone will do.

If you drive to work, you'll need Bluetooth, or some way of hooking it into your car stereo (I spent about 150 euros into getting a Bluetooth stereo into my car, service included). A lot of car stereos also have aux-in (cable).

Now get either Downcast for iPhone, or BeyondPod for Android. Subscribe to a podcast of your liking, and start listening.

I recently started my own podcast as a supplement to this blog, and in the last episode we talk about our very first steps as podcast-listeners (there are some great podcast recommendations for you in the show-notes), and some tips and tricks for bootstrapping the experience.

But I don't get anything out of listening to people talk

Maybe. We're all different. Or maybe you should try doing it for a few weeks and see if you start to like it. I disregarded podcasts as being kind of useless up until summer last year. Now I'm a total podcast junkie.

But the information I want to consume is not available in podcast form

Hey, you just discovered a niche where you should start your own podcast! Well, maybe not, but this is something I'll come back to in a future blog-post, because once you really start consuming, you might exhaust the good podcasts' production rate.

For instance, the programming-related podcasts I listen to don't produce enough for me to listen to constantly, so I've widened out and started listening in other areas like science, etc. Expand your horizons a bit. Besides, in years to come I'm pretty sure we will get more and more content producers in every area.

And if you still run out of podcasts, there are still plenty of audiobooks.

But I still didn't get around to reading all those things I wanted to read

Neither did I. But I don't feel so bad about it anymore, because I'm investing a lot of new time into learning stuff. Besides, when listening to podcasts, I get a lot more information into my brain compared to when I skim through articles or blog-posts. A podcast is a bit like a real conversation with someone who's trying to explain something to me deeply. In the end, I feel smarter, and better informed.
Labels:

Comments

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...
6 comments
Read more

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...
1 comment
Read more

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...
Post a Comment
Read more

Git-SVN Mirror without the annoying update-ref

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit   directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our  fetching repo. Set up a  bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...
17 comments
Read more

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --...
12 comments
Read more