We had a strange issue at work – we had a misbehaving server, who worked perfectly well with one client but had strange issues when several clients connected to it. The server would broadcast a message to all of its clients but only one client would receive that specific message, re-sending the message would fix … Continue reading Spot the bug – misbehaving server
Month: February 2011
Multiple asserts – done right
If you’ve been writing unit tests for some time or seen a good presentation on how to write unit tests you probably heard the “One assert per test” rule. There are real benefits in having only one assert in each tests – you get a focused tests, it’s easier to understand what caused the test … Continue reading Multiple asserts – done right
Kanban workshop for leader/managers–Part II
a week ago (give or take a day) I attended a Kanban workshop by Agile consultant company, AgileSparks– the following is my impressions from that day along with my thoughts on the subject: In the 2nd part of the day we continued the workshop at full speed – the next few hours were devoted to … Continue reading Kanban workshop for leader/managers–Part II
Kanban workshop for Leaders/Managers
Yesterday I had the opportunity to participate in a one day Kanban workshop by AgileSparks. The workshop was intended for leaders and managers and so one morning I found myself sitting in a conference room with project managers, team leaders and one VP. Although it meant that not everything I learned was directly related to … Continue reading Kanban workshop for Leaders/Managers
How to ignore thrown exceptions
Yesterday I came across this question on StackOverflow:Is there a better way to ignore an exception in C# than putting it up in a try catch block and doing nothing in catch? I find this syntax to be cumbersome. For a code block, can't I simply "tag" it in such a way so as runtime … Continue reading How to ignore thrown exceptions