How to Reconnoiter a New Role!

“i.e. Starting a challenging new role!” I’m stepping into a role right now, which I announced recently “Career Update: Back … More

Coding on Orchestrate.io & Orchestrate.js & Orchestrate.NET

First context, then I’ll dive in. Orchestrate http://orchestrate.io/ Orchestrate is a service that provides a simple API to access a … More

Git Rid of Windows Azure and Amazon Web Services (AWS) SDKs with .NET + Git + AppHarbor Deployment Revolution

First a few tidbits on the latest SDKs. For the latest Windows Azure SDK go check out the Microsoft MSDN Site.

For the latest for AWS (Amazon Web Services) SDK check out the AWS .NET Site.

These two SDKs are great for customers who want to build on the bare bones X platform. Now whatever language & stack one builds in they are tied to that. Ruby on Rails, .NET, Java, PHP, or whatever. But getting tied to the stack is kind of like breathing air, one has to live with what air they have. You can’t exactly get a refund very easily on that.

The Cloud SDKs though for Azure & AWS provide a certain amount of lock in, in addition to the stack lock in you’re using. One of the easiest ways to prevent this lock in is to use a general deployment method backed by source control on something like Git or Mercurial. So far though, .NET has been left out the cold. There has been almost zero support for pushing .NET via Git or Mercurial into a cloud.

My Current Windows Development Machine Software Stack

I recently did a clean install of Windows 7 64-bit. It had been a really long time since I listed the current tools, SDKs, and frameworks that I’ve been using. Thus here’s my entourage of software that I use on a regular basis that is installed on my primary development machines.

Waterfall vs. Agile

I’ve seen it on more than one project in my career and it always seems to happen. Agile rarely gets credit in this scenario. People rarely learn what was and was not effective on the project in this scenario. What I’d like to know though, especially from those that have successfully dealt with the “Must have big design up front (BDUF) headaches” and transitioned those people to a more Agile style approach.

The scenario generally starts like this…

A project is green-lighted for whatever reason, often with some high level manager determining that a project will save X amount of money or make X amount of money. The project is poorly defined or simply not defined at all. The stakeholders, clients, or others that would prospectively use the software are nowhere to be found and unidentified by management. There are at least a half dozen external dependencies the project must have completed.