Group items tagged

"Interfaces are wonderful for a language like C#. Interfaces give us everything we need to work with an object in a strongly-typed manner, but place the least number of constraints on the object implementing the interface. Interfaces make the C# compiler happy without forcing us to pay an inheritance tax for working with a class hierarchy. We'll define an interface that describes exactly how we want to fetch customers and how we want the customers packaged for us to consume."

I was pondering over the thought: agile is nice and all, but how can we sell it to customers that have a more traditional way of thinking about projects? This blog article gives some good food for thought on these matters.

"Switching from developing ASP.NET WebForms to MVC might seem awkward at first, but Ed demonstrates why the change needn't be painful, and how best to build a set of tools for rapid MVC development."

Some time ago, the development team at my firm staged a revolt against the sales team and senior management: our demand was that no Statement of Work was to be sent to a customer without first being reviewed by a member of the development team. [..] Today I would like to explore an important aspect of any Statement of Work: the pricing model.