In my last post I mentioned that I chose to remain behind the firewall curtain and only post internally because my employer was a little uncomfortable with us posting publicly.
With that, you might think that perhaps I'm tempting fate by choosing to start a public blog. After all, people have been fired for blogging about their jobs, right?
In this case, though, I need not worry. My employer is not going to fire me for blogging.
The tough week on Wall Street last week has led our new CEO to go forward with a reduction in force and has closed the entire New York office, including me and nearly my entire team (I had one developer in Chicago who is still employed.)
I'd planned to start my public blog because I was interested in sharing my excitement about the Microsoft Cloud services anyhow, but now for the first few weeks at least, I'm going to be using my blog to share resources with my team.
Regarding the reduction in force, I am naturally sad and disappointed that it had to happen, but I understand it is purely a business decision. It is not a reflection on the quality of the team of developers who I have worked with for the last five years, but rather on the cost of doing business in Manhattan during a deep economic downturn.
If you are reading this and have open positions in the New York City area, drop me a line and I would be glad to help you connect with some very talented and qualified ASP.NET developers.