The year is 2017. At this point, whenever Windows Server 2003 provides the inspiration for a blog post, it’s probably not going to be the very salutary.
Dan Frith used a recent experience with the dated OS to look at the state of software lifecycles, and quite frankly vent some frustration. He bases this discussion on something that’s both obvious but almost always overlooked by the IT community: almost all companies aren’t focused on IT. For them, IT is a line item not seen as an enabler in and of itself. You can argue all day that this is backwards, but it doesn’t change the fact that it’s true.
Dan uses this to frame the deficiencies of current software lifecycle approaches, which must quickly pivot from calling a piece of software the new hotness, only to have to sell it as terrible to justify an upgrade down the line. This is a broken cycle in a lot of respects, and doesn’t acknowledge the needs of many organizations.
Dan Frith comments:
This is one of those posts that is really just a loose collection of thoughts that have been bouncing around my head recently regarding software lifecycles. I’m not a software developer, merely a consumer. It’s not supported by any research and should be treated as nothing more than opinion. It should also not be used to justify certain types of behaviour. If this kind of hippy-dippy stuff isn’t for you, I’ll not be offended if you ignore this article. I also apologise for the lack of pictures in this one.
Read more at: How Soon Is Now?
