Skip to main content
This tuesday I'm going to do a workshop on wiki for some people in management/business development department. We've been smart enough to choose Confluence for our internal wiki, and its use has been growing steadily ever since last summer, bout the same time as I joined the company.

Over this time I've managed to earn the rep of a wiki-evangelist within the company. This is probably I've taken the time to learn the in's and out's of Confluence content formatting, making pretty layouts with columns and tables, galleries, RSS-feeds, and intranet blogging. Some people think I spend too much time fiddling around with it (see for instance the screenshot of my personal space page), but I think it's fun and interesting to try out. I'm not doing it to evangelize the whole company into going crazy on wiki-usage, I just use the wiki to cover my own butt mostly.



If I didn't write things down in the wiki, I'd very quickly fall into the state of corporate goldfish memory, where the only accessible knowledge would be the one found in my brain, and most of that would be about the projects I'm working on right now. Not half-a-year ago or several years ago.

Instead of trying to remember old projects, I write down stuff every day. It could be anything from 5 to 50 lines, and mostly they're about what I have done, and what I'm going to do. These are for my own reference, not for project documentation. The archive is searchable, and I find my own (and others') notes being more and more useful.

But enough personal motivation. The thing I wanted to write about today is how I'm going to present the use of our beloved wiki for the management.

So, let's start with the cons we've got. These are reasons why management would not like to use the wiki:

  • They've already got an existing intranet. Adding another adds to the complexity of the infrastructure.
  • There is no special interconnection with MS Office/Exchange software.
  • It's another tool to learn (and wiki markup ~> programming language)
  • Suspicion towards wiki access control.
So, to sum up, the Wiki is hard to use, hard to control and does not work well with the existing infrastructure.

So let's start off with these points and break down the wiki-hostility :)

Complexity
The wiki is designed to be a simple tool. It builds on the very basic standards that define the success of the Web today. A wiki does not add much complexity because it is not complicated. It's just a simple web-application that can use your existing user directory service (LDAP), and beyond that it doesn't affect your existing systems (except the competition it adds to your DMS-systems/intranets).

No MS Office collaboration
We'll admit to the fact that there is no special compatibility between the content of your wiki and the content of your Word documents. We (as in us developers) would argue that this is a problem of MS Office not following industry standards, but management hears "bla bla bla our stuff does not work with MS Office", a very bad thing indeed since MS Office is the platform on which they rely to do most of their job.

Now you can upload Office documents as attachments to the wiki, but that's about it. Other than that we can't do much except recommend that management puts their document in explicit, transparent wiki content so they can enjoy the functionality of search, versioning and XML-export.

The learning curve
Once you get into it, wiki-markup is really easy. And if it's still too hard, you can still use the WYSIWYG editor. The issue is also countered by Confluence's excellent documentation.

Access control uncertainties
This is perhaps the most prominent show-stopper for wiki embrace in an organization. It is not only about security and confidentiality. Members of management have a certain.. sovereignity they must perform onto the content they create.

One manager's content is an important artifact. Often it should only be viewed by a select few, and naturally not edited by anyone else than the manager.

The wiki brings with it a message of free access to all content. Everyone can edit everything. This sounds risky to management.

Luckily, Confluence comes with great possibilities for administering access control. Will have to make a point of it on the presentation.



Now I better get started on the presentation. Will include these points, as well as some short history of wiki, the role of wiki (as a Knowledge Management tool?), and finally assignments! (wee, I get to boss management around)

Popular posts from this blog

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 and sa…

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-zsh.git
    -> ~/.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…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

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…

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…