Developers to Vendors: Slow Down Already!
A common attitude among IT managers is technology exhaustion. Before you (or your organization) have had the time to discover the benefits of one product version—much less deploy it to users—a new version is released. Yeah. No surprise. But what is a mild shock is to discover the same attitudes from the developers who ostensibly are driving forward those technologies and products.
Earlier this week, I attended a Microsoft briefing about Silverlight 2. The event, sponsored by the local Phoenix-area .NET User Group, brought in Scott Guthrie and other high-level Microsoft people to describe such niceties as using Web services with Silverlight, the ASP.NET MVC Framework, and techniques for encoding video. There was plenty of technical material for programmers... but, as usual, I gleaned more wisdom from the developers during the lunch break.
In particular, one developer complained about the fast pace of product releases; he wished that Microsoft would just slow down. He said that he felt like he's always trying to keep pace with the next version (and, mind you, Silverlight 2 just went into beta) while he struggles to support users who are using software versions that are one or two generations behind.
Another developer at the table agreed wholeheartedly. He works at a government agency, it seems, that has just installed SQL Server 2005; adopting the newest version isn't even under discussion at this point. But rather than resent IT management for dragging their feet at deploying the latest-and-greatest, as I would have predicted, these developers were annoyed at users who try to circumvent or strong-arm IT's policies (such as expecting their iPhones to be supported).
Maybe it's simply that I sat at the Cynicism Table, or developers tied to a Microsoft vision are less likely to embrace change than are others, or that those who choose to work in larger organizations adopt a slower-to-change mindset... but I would have predicted a very different view. I've always thought of developers as the first to see promise in new technologies (which at least is supposed to be reflected in the newest version of any product) and anxious to deploy it before the digital paint is dry.
The other thing that struck me about the conversation is that the developers believed that this was a new phenomenon (according to the Gen Y developer) or that the pace of change had grown out of control (said the Gen X guy). I don't really believe that it's true. I worked harder to keep up with both product releases and the burden of "Too many choices!" back in the MS-DOS era, when it wasn't just an issue of "Should we upgrade?" but "Should we bet the business on this vendor's product rather than that one?"
This experience was completely anecdotal, so I'm not sure how representative it is. How does it match with your (or your developers') attitudes?
Previous Post: Messy Desk, Organized Computer. And Vice Versa.Next Post: In Pursuit of the Technical Contact
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
