Kanban and rants

Since I apparently got carried away blogged a lot in August 2008 I have to pick a few of the more interesting posts from that month and see if there is any update to be made. I guess that also means that by definition the things I don't mention today are not that interesting any more...


TeamSnippets review

This is for anybody out there looking for information on TeamSnippets since you are considering using it. Short version; I don't see why you would want to use such a service.


Go for C# developers: Introduction

When I first started to learn Go a few months ago I compared a lot of things to things that was familiar to me; C#. And I decided to make a series of posts explaining some go-isms in C# (or .Net) terms as well as high-light some of the differences that are important to know about.


All you ever wanted to know about password hashing

Well sometimes I'm lucky and somebody else writes something so I don't have to. Since you should assume that your system will be breached eventually you should make sure that your user's  passwords cannot be exposed as a lot of users reuse their passwords across multiple sites.


Removing stuff you don't need

So I start this series of updated old opinions and the MSDN blog change interface so there are no longer links to monthly archives except the last three months of posts. There is some logic to it I guess since it keeps the archive list shorter but I wish they made it configurable... Anyway; this time it is time to talk about some posts from July 2008 which can be found on this page.


Inter service communication: pub/sub vs message bus vs req/response

Over the last few weeks I've been going over a few different ways to solve inter service communication. So which one is best then?


Inter service communication: pub/sub

In order to distinguish pub/sub from message bus communication I will assume the pub/sub does not use another component to distribute the data as that would be a message bus pattern. I will assume that the publisher knows about all subscribers either statically or dynamically.


Inter service communication: message bus

Last week we covered request/response communication and now it is time to talk about the complete opposite; message bus communication.


Inter service communication: request/response

Over the next few weeks I will cover a number of different ways to services can communicate with each other. First out is the classical request/response.


Code Coverage and nothing is too simple to test

So time to look back again and update some old opinions from June 2008. And while there are some other useful stuff in there I'll focus on code coverage and testing simple things. Because I feel the urge to explain myself...