Skip to main content

New Year's resolution: Blog more! (the boss says so)

As I wrote in my previous post I've been through my yearly evaluation at work. In short it was a 4-hour talk with my team-leader where we went through different aspects of my performance, such as development abilities, people skills, and so on.

Now such an evaluation might sound like a bit of a harsh Americanized performance indicator that decides my pay-check, but I appreciated getting honest feedback and ideas on areas where I can improve. Note that one important prerequisite for doing this sort of evaluation is having a team-leader you trust, not being the same person as the one who finally decides your pay-check ;)

After the evaluation of last year's achievements, we set out to decide this year's goals. We arrived at me reading quite a few books, doing some internal as well as external presentations, delivering some projects and participating on a couple of courses. All these goals were formalized with concrete objectives, and will be easy to measure throughout the year.

Now the final and (to this blog atleast) most interesting goal was to increase the readership of this blog. Quadruple it, to be exact. The indicator we are using is visits per week, as measured by Google Analytics. Based on statistics since August last year, my weekly visit count has been averaging on 30. By the end of the year this should have increased to 200! (for some reason we thought the weekly visit count was 50)

I have written about how to use the blog for online research before, and even if I'm not doing research anymore, the same rules still apply. Here's how I intend to increase my readership:

Blog about stuff that people want to read
I've blogged on various themes the last years like CMS, Portals, Blogging, Java, Knowledge Management and other stuff (will get better at using tags, promise). The subject of open-source content management systems seems to be the subject that attracts the largest crowd of readers, so I'll keep writing about that. As my work seems to have gone back into that direction in my newest project, it will be easier to collect experiences on the field again.

Produce trackbacks
Read blogs, leave comments. My main problem here is that my CMS blogroll swells with new posts faster than a Gartner hype gives your manager twitches in his forehead. So I'm gonna have to streamline it a bit and focus more on those blogs rather than reading all the Java-related ones.

Blog regularly
Every sunday, I tell you!

So go ahead and hit that subscribe-button now! It might result in me getting a (bigger) raise next year :)

Comments

  1. Anonymous17/1/07 21:54

    Every sunday does not seem like such a bad idea as these days often are used relaxing at the computer. At least thats what I do on a sunday :)

    I'd love to see some posts on KM as well as I am probably too lazy to blog myself i will do the comments!

    ReplyDelete
  2. I'll keep that in mind, still have some thoughts on that subject :)

    ReplyDelete

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...

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password...

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...

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...

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 https://github.com/tfnico/config-mr.git 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: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config...