4:25 pm, May 28, 2015

FederalNewsRadio.com - Purpose of Comments statement Click to show

Hubbard Radio, LLC encourages site users to express their opinions by posting comments. Our goal is to maintain a civil dialogue in which readers feel comfortable. At times, the comment boards following articles, blog posts and other content can descend to personal attacks. Please do not engage in such behavior here. We encourage your thoughtful comments which:

  • Have a positive and constructive tone
  • Are on topic, clear and to-the-point
  • Are respectful toward others and their opinions

Hubbard Radio, LLC reserves the right to remove comments which do not conform to these criteria.

  • 1

  • giveaways and self-licking ice cream cones
    Data Center Consolidation This draft legislation has major new legislative drivers to push all feds into consolidated data centers, and to drive the fairly useless metric of server utilization. Does anyone else out there know how to write a script to drive server utilization through the roof? I thought you did. The real kicker is section 203 - "(2) appropriate consideration of shifting Federally owned data centers to commercially owned data centers." This is a a pure, unadulterated giveaway to several large beltway bandits. It's a license for those federal contractors to print money - or rather, to haul money away from federal IT budgets in dump trucks. section 214 - transition to the cloud. This hasn't been working out terribly well on a flexibility and cost basis, so now it's going to be implemented in legislation. another giveaway to a small number of private vendors. Not that all cloud is bad, but "all cloud all the time" is an invitation for cloud infrastructure vendors to cart off "adaptation" and "tailoring" fees to torture cloud infrastructures to do things they were never intended to do, and will never do well. but only until the next fad and crisis 'reveals' that cloud was a bad fit for many projects, but whatever's new is no required. section 301 - Federal commodity IT acquisition center This is the section put in by Microsoft to ensure there's a single center that can dictate that desktop and e-mail are 'commodities' and provide (exclusive, mandatory) acquisition contracts ensuring that all fed gov desktops and e-mail are provided by Microsoft, and paying license fees to Microsoft for all time. The moral hazards and conflicts of interest in this section are truly mind-numbing. The only upside i can see is that this will probably exist as a paper tiger for longer than its actual impacts will be relevant. I assess less than a 20% chance that this will have any teeth within 5 years. Hopefully by then Microsoft will be toothless as well. section 302 - Assisted Acquisition Center of Excellence (AACE) Here's another layer of governance, sign-off, and bureaucracy brewing on the horizon. The veiled language here indicates there's some unspoken motivation that will 'pop out' of AACE rules-making. I grant that section 405 makes good use of this AACE mechanism to support a variety of Open Source goals (I can't imagine 302/405 came from the same staff as 301...). So maybe 302 is just an 'enabling framework' to salt AACEs around government doing good work that needs to hide from the IT-license lobby. Here's hoping. Overall... This feels a lot like legislation written by lobbyists, with some clever bits salted around the edges by idealistic staffers. This bill does little or nothing to address the actual dysfunction that plagues government IT shops. That is going to require significant effort and real management reform, not a few buzz-words sprinkled on top of a lot of private sector pork.
    { "Agree":"1","Funny":"1","Insightful":"1","Disagree":"-1","Offensive":"-1","Troll":"-1" }
  • { "Agree":"1","Funny":"1","Insightful":"1","Disagree":"-1","Offensive":"-1","Troll":"-1" }