[T]here will be classes of developers that go after Git and they’ll love Git for what it allows them to do which is to stay off the radar until their tiered promotion gets it ultimately to visibility, but there will be other shops that want to have that visibility the entire time and their compliance or governance or whatever the management driven stuff that is required will keep it around.
Posts in "BigCo"
[T]here will be classes of developers that go after Git and they’ll love Git for what it allows them to do which is to stay off the radar until their tiered promotion gets it ultimately to visibility, but there will be other shops that want to have that visibility the entire time and their compliance or governance or whatever the management driven stuff that is required will keep it around.
[T]here will be classes of developers that go after Git and they’ll love Git for what it allows them to do which is to stay off the radar until their tiered promotion gets it ultimately to visibility, but there will be other shops that want to have that visibility the entire time and their compliance or governance or whatever the management driven stuff that is required will keep it around.
Atlassian bundles ALM components around the popular git version control system (451 Report)
Atlassian released an ALM bundled centered around git recently. I wrote up a report on that release, git in broader terms, and of course profiling the current state of Atlassian.
Here’s the 451 take:
Git Essentials is a natural bundling move by Atlassian. The company has long been expert at tracking mainstream needs for software development teams and acted as a sort of safety bumper around the leading edge of developer practices and technologies: taking and creating early adopter technologies and making them enterprise ready.
Atlassian bundles ALM components around the popular git version control system (451 Report)
Atlassian released an ALM bundled centered around git recently. I wrote up a report on that release, git in broader terms, and of course profiling the current state of Atlassian.
Here’s the 451 take:
Git Essentials is a natural bundling move by Atlassian. The company has long been expert at tracking mainstream needs for software development teams and acted as a sort of safety bumper around the leading edge of developer practices and technologies: taking and creating early adopter technologies and making them enterprise ready.
Atlassian bundles ALM components around the popular git version control system (451 Report)
Atlassian released an ALM bundled centered around git recently. I wrote up a report on that release, git in broader terms, and of course profiling the current state of Atlassian.
Here’s the 451 take:
Git Essentials is a natural bundling move by Atlassian. The company has long been expert at tracking mainstream needs for software development teams and acted as a sort of safety bumper around the leading edge of developer practices and technologies: taking and creating early adopter technologies and making them enterprise ready.
Secondly, when evaluating new IT hardware and software assets for potential adoption, you need to institute a much stronger requirement for programmability and open APIs. Complete automation of your infrastructure requires programmatic access, and it’s simply insufficient to only have control via graphical interfaces. This isn’t just about provisioning and configuration support via such APIs, you also need to ensure that vendors are providing reliable APIs to get sufficiently detailed status. A core tenet of DevOps is the ability to measure the state of your infrastructure for future improvement and this really needs to be automated programmatically. Ideally these APIs for automation and measurement are simple, easy to adopt, and accessible to people who aren’t full-time software engineers. Thus, beware of complex, language-specific APIs, and strongly lean towards vendors using simple HTTP or REST APIs and standard, easily parsable data formats like JSON.
–Nigel Kersten, Puppet Lab’s CIO. Also, see this interview I did with Nigel way back in 2008 when Nigel was using Puppet to manage the Mac desktops (!) at Google.
Secondly, when evaluating new IT hardware and software assets for potential adoption, you need to institute a much stronger requirement for programmability and open APIs. Complete automation of your infrastructure requires programmatic access, and it’s simply insufficient to only have control via graphical interfaces. This isn’t just about provisioning and configuration support via such APIs, you also need to ensure that vendors are providing reliable APIs to get sufficiently detailed status. A core tenet of DevOps is the ability to measure the state of your infrastructure for future improvement and this really needs to be automated programmatically. Ideally these APIs for automation and measurement are simple, easy to adopt, and accessible to people who aren’t full-time software engineers. Thus, beware of complex, language-specific APIs, and strongly lean towards vendors using simple HTTP or REST APIs and standard, easily parsable data formats like JSON.
–Nigel Kersten, Puppet Lab’s CIO. Also, see this interview I did with Nigel way back in 2008 when Nigel was using Puppet to manage the Mac desktops (!) at Google.
Secondly, when evaluating new IT hardware and software assets for potential adoption, you need to institute a much stronger requirement for programmability and open APIs. Complete automation of your infrastructure requires programmatic access, and it’s simply insufficient to only have control via graphical interfaces. This isn’t just about provisioning and configuration support via such APIs, you also need to ensure that vendors are providing reliable APIs to get sufficiently detailed status. A core tenet of DevOps is the ability to measure the state of your infrastructure for future improvement and this really needs to be automated programmatically. Ideally these APIs for automation and measurement are simple, easy to adopt, and accessible to people who aren’t full-time software engineers. Thus, beware of complex, language-specific APIs, and strongly lean towards vendors using simple HTTP or REST APIs and standard, easily parsable data formats like JSON.
–Nigel Kersten, Puppet Lab’s CIO. Also, see this interview I did with Nigel way back in 2008 when Nigel was using Puppet to manage the Mac desktops (!) at Google.
Mirantis navigates changing OpenStack market, growth with 4.0 release (451 Report)
My team has a new report up on Mirantis, with updates on their momentum and an overview of what’s in their 4.0 OpenStack distro release.
Here’s the 451 take, our brief opinion on the news:
Mirantis reported more bookings in the last quarter of 2013 than all of 2012 – its growth by revenue, employees and overall business highlights the company as a leader among OpenStack pure-play vendors. Mirantis seems well positioned for an evolving OpenStack ecosystem and market, but the transition from services and support, which has been its specialty, to product subscription models may be challenging.