Skip to main content

Dynamifying my bookmarks

I guess this is as close I'll get to talk about Web 2.0 (yuck) in this blog. I'm in the process of moving my links in this blog out of my static template and into (tip o' the hat to Petter!), like the blogroll from bloglines, except this is a linkroll, I guess. Here are the steps I did to get it in:

  1. Bookmarked and tagged all the links on my (tagged with atleast 'cms')
  2. Did not bookmark links that I blogroll allready
  3. Find out what to do with the template. This turned out to be more difficult as all the how-to's on the net are concerned with how to integrate tagging between and blogger, which I don't care about (yet). Tagging (i.e. metadata) is seriously overrated anyway.
  4. Patiently wait for Petter to comment here and say what he did because I can't bother finding it out on my own right now :)
  5. Thanks, Petter! Went to and fiddled with it a bit
  6. Pasted it into a comfortable area in my template (same place as yon ole links)
  7. Fiddled with the CSS a bit (thanks, Lars!). Ended up with these styles:
.delicious-posts { margin: 1em; border: 2px solid #999; padding: 0.5em; width: 14em; font-family: sans-serif; }
.delicious-posts ul, .delicious-posts li, .delicious-banner { margin: 0; padding: 0; }
.delicious-post { padding: 0.25em; font-size: 80% }
.delicious-odd { }
.delicious-banner a { font-size: 80% }
.delicious-post a { }
.delicious-posts a { text-decoration: none; color: #f93; display: block; padding: 0.3em }
.delicious-posts a:hover { color: #fc9; }
.delicious-posts .delicious-odd a{ color: #888899 }
.delicious-posts .delicious-odd a:hover{ color: #cdcdcf }


  1. Hey Thomas!

    I love your blog's new style :) To get the code for your template visit:

    Just follow the instructions. - metadata rules! :D

  2. Thanks, Petter! I even styled it ut a bit (with a little help from my designer fairies - they sure know their RGB-codes). Will update the post promptly.


Post a Comment

Popular posts from this blog

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

    -> ~/.atom/*

    -> ~/.mrconfig
    -> ~/.config/mr/*

    -> ~/.tmuxinator/*

    -> ~/.vimrc
    -> ~/.vim/*

    -> ~/bin/*

    -> ~/.gitconfig

    -> ~/.tmux.conf    

    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams.

If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming. 

Since these tools are for gamers, they have to be
fast (low latency)light (as not to steal CPU-cycles from heavy games graphics) moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak, Ventrilo, more recently the massively grown Discord, and finally Mumble, which is the open-source alternative of the gang.
A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSpeak server set up…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…