The implication is that users/subscribers/audience members are loyal and will stay with the programming for some time. There is also a second implication that businesses which are not measured by audience size don’t have this loyal and recurring revenue base. The absence of an “audience” implies transience and impermanence and results in deep discounting of long-term viability. Which is why ecosystems are the desired business construct for technology companies. They allow a more consistent and repeatable transaction model and offer a predictability which is sorely lacking […] when technology changes rapidly.
Posts in "tech"
By 2019, 67 percent of software programmers will primarily be developing in the cloud, up from 18 percent today, predicted Evans Research.
Evans prediction in the tail-end of this piece on IBM going SaaS
By 2019, 67 percent of software programmers will primarily be developing in the cloud, up from 18 percent today, predicted Evans Research.
Evans prediction in the tail-end of this piece on IBM going SaaS
By 2019, 67 percent of software programmers will primarily be developing in the cloud, up from 18 percent today, predicted Evans Research.
Evans prediction in the tail-end of this piece on IBM going SaaS
[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.
Commentary from 451’s Peter ffoulkes:
The transformation of IT to a ‘client service’ model is notable and gaining momentum. While this is occurring in many forms, cloud-oriented projects are consolidating in an activity level at three times the level of other supporting projects, with internal private cloud projects leading the pack at 37%. Over the last year of the Cloud Computing Study there has been some pullback of public cloud activity. While these projects still outweigh traditional IT or ‘cloud-readiness’ projects at a similar level, there has been a small but noticeable shift toward private cloud project activity.
[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.
Commentary from 451’s Peter ffoulkes:
The transformation of IT to a ‘client service’ model is notable and gaining momentum. While this is occurring in many forms, cloud-oriented projects are consolidating in an activity level at three times the level of other supporting projects, with internal private cloud projects leading the pack at 37%. Over the last year of the Cloud Computing Study there has been some pullback of public cloud activity. While these projects still outweigh traditional IT or ‘cloud-readiness’ projects at a similar level, there has been a small but noticeable shift toward private cloud project activity.
[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.