Have a look at Airflow as well. It is a bit more adventurous (read Python) than WWF, K2, Automic or BizTalk, but definitely has its strong points. It is simpler to install and use. The concept behind is well-thought and there's a good open source community behind the project. Some big names are using it too, so it has enough support from the business. Deployment and configuration to multiple environments might be a challenge, but so is true for any other workflow framework.

In addition to all exercises previously mentioned I find this one to be particularly helpful. With one correction, you should point your head in the opposite direction to your knee. The cutie on the video keeps looking up, without moving her head. In general, any exercise twisting your spine (carefully!) and relaxing back muscle should help.

Same here. My wife and I decided to get rid of this time-consuming and brain-flattening device of mass control years ago. Now, if only there was a way to cut down on sleeping, I would have some spare time at last.

Oh yes, you tell them!! But wait, when you say "stupid, useless and dishonest", you don't mean software developers, do you?

So, in a brief moment of enlightenment, I came to a conclusion that my current place of work does not fully utilise my broad range of skills and expertise, and the best course of action for me is to change it (job, not skills). As the grass is always greener on the other side, I put myself on the quest to find it. Unfortunately this meant dealing with those dreadful kind of people called Job Agents. Here are some stories I’d like to share with you: Story 1 A job agent called, saying he had “a fantastic opportunity” with “a leading company, employing best people and using cutting-edge technology” and I am “a perfect match for the role”. Moreover the MD of the company is “a good friend of his” and he really liked my CV and “is eager to meet me”. I ignored those warning lights, and I decided to go ahead with it anyway. The interview was set up and I showed up at the specified time. The company turned up to be a complete disaster, chaos and filth in the office, and of course no one expected me. I waited for 20 minutes and some guy came thrice asking my name and if I was sure I had an interview there. I was almost ready to walk out, but was too curious to find out how it was going to end up. Then I was seated in a kind of a store room, which I think was the cleanliest place in the office, where I was interviewed by a techie guy, who must have recently read some book on TDD, and thought it was the greatest thing since sliced bread. On my delicate suggestion that TDD is just a tool, like many others, to help us write better code, he gave me that indulgent look, the way you look at a pathetic ignorant, and our ways parted. I didn’t get to meet MD. Immediately after the interview, I called the agent as it is customary. No answer. I texted him, emailed him, still waiting for any contact. Story 2 I received an initial email from an agent. I replied, we had a nice and long email exchange and three possible roles were identified, which I could apply for. She asked me to call her to discuss them in details. That’d be a first time I spoke to her, as all previous conversation was in email. Now, I might have some heavy eastern European accent, and there are some people who find it a bit difficult to understand in the beginning, but usually after some time they get used to it, and it was never any issue in communication. Anyway, I called the agent. After I spoke two or three sentences, I could clearly sense she became so disappointed (presumably with the way I speak) she cut the conversation short and h

I cannot agree with that. I've been using TFS for the past 6 mths, and while I found it to be great Application Development Lifecycle tool, when it comes to the source control, SVN is far superior IMHO. Initially I thought it is just a matter of getting used to the tool and I should give it a chance. After months of experience, I still reckon that common things like branching, merging, blaming, comparing revisions (changesets) or even committing is simpler and more intuitive in SVN.

Oh, good old days ^

I moved to a new job a couple of months ago. I'm working on extending existing product. It's quite mature as it's been developed for the past decade, so the code base is rather large. Many times often I need to dig into existing code. I find some strange things there, just a moment ago I found:

public override void ReverseProcess()
{
List actionsList;
// get actions
var actionsEnumerator = actionsList.GetEnumerator();
actionsEnumerator.Reset();
ReverseActions(actionsEnumerator);
}

private void ReverseActions(IEnumerator actionsEnumerator)
{
while (actionsEnumerator.MoveNext())
{
automatedActionEO = (AutomatedActionEO)actionsEnumerator.Current;
//process action
}
}

The code was written in 2013, so either someone is stacked on .NET 1.1 or thought that using GetEnumerator() in that way looks smart in the code, i.e. as if they knew some inner mechanisms of collections ;) There's a lot of weird things like this one in the inherited code. Most of them not harmful, just weird.

not wait a week for it to arrive There's that thing called Next day delivery. It works pretty well. You order your book during the lunch break, and next day in the morning et voilà! the book is on your desk!

You will love this: //----------------------------------------------------------------------- // Copyright (C) Microsoft Corporation. All rights reserved. //----------------------------------------------------------------------- // AtlasRuntime.js // Atlas Runtime Framework. :) and many of this can be found on every MSDN2 page!!! If I have developed sites like that I would be fired in no time :-D Jacek