“On the business side, Progressive Delivery involves two core changes in the delivery model: Release progression – progressively increasing the number of users that are able to see (and are impacted by) new features (e.g. Stage 1: visible to developers only; Stage 2: visible to developers and beta users; Stage 3: visible to more users; Stage n: visible to everyone) Delegation – progressively delegating the control of the feature to the owner that is most closely responsible for the outcome.

“On the business side, Progressive Delivery involves two core changes in the delivery model: Release progression – progressively increasing the number of users that are able to see (and are impacted by) new features (e.g. Stage 1: visible to developers only; Stage 2: visible to developers and beta users; Stage 3: visible to more users; Stage n: visible to everyone) Delegation – progressively delegating the control of the feature to the owner that is most closely responsible for the outcome.

“Low-code [uses] declarative techniques instead of traditional lines of programming… Common features include reusable components, drag-and-drop tools, & process modeling. Individuals or small teams can experiment, prototype, & deliver apps in days or weeks.” Plus, marketsizing: something like $4bn. Original source: Why You Need To Know About Low-Code, Even If You’re Not Responsible For Software Delivery

“Low-code [uses] declarative techniques instead of traditional lines of programming… Common features include reusable components, drag-and-drop tools, & process modeling. Individuals or small teams can experiment, prototype, & deliver apps in days or weeks.” Plus, marketsizing: something like $4bn. Original source: Why You Need To Know About Low-Code, Even If You’re Not Responsible For Software Delivery

“Let’s think about control. I’d struggle to find any engineers operating within a DevOps mindset eschew control of their production systems. I encourage the use of a CMDB, but again, it’s live, automatically updated, and software-based. It’s called a Chef server. Similarly, ITIL places a strong emphasis on configuration. Teams I have built do the same. All changes to the system are made in code, go through a peer review process, are automatically tested, and rolled out in a recordable, repeatable, and auditable manner.

“Let’s think about control. I’d struggle to find any engineers operating within a DevOps mindset eschew control of their production systems. I encourage the use of a CMDB, but again, it’s live, automatically updated, and software-based. It’s called a Chef server. Similarly, ITIL places a strong emphasis on configuration. Teams I have built do the same. All changes to the system are made in code, go through a peer review process, are automatically tested, and rolled out in a recordable, repeatable, and auditable manner.

“ I don’t worry much about where maintenance occurs. Indeed, if maintenance can be done for less we ought to buy more, so less expensive can mean safer…. Rather than fearing the offshoring of airplane maintenance we ought to ask how we can expand the concept. Medical tourism, for example, is growing. If foreign airplane maintenance is good enough for Delta then foreign human maintenance is good enough for me.”

“ I don’t worry much about where maintenance occurs. Indeed, if maintenance can be done for less we ought to buy more, so less expensive can mean safer…. Rather than fearing the offshoring of airplane maintenance we ought to ask how we can expand the concept. Medical tourism, for example, is growing. If foreign airplane maintenance is good enough for Delta then foreign human maintenance is good enough for me.”

“The tiny margin in CA’s enterprise software business, which contrasts with its richly profitable mainframe division, won’t help Broadcom hit its projected EBITDA targets, no matter how many ‘adjustments’ are made. In fact, the division stands in the way.” Original source: Broadcom can’t get there from here

“The tiny margin in CA’s enterprise software business, which contrasts with its richly profitable mainframe division, won’t help Broadcom hit its projected EBITDA targets, no matter how many ‘adjustments’ are made. In fact, the division stands in the way.” Original source: Broadcom can’t get there from here