X : What is digital transformation?
Me : A bunch of companies waking up to a thing called the "World Wide Web" and a bunch of consultants trying to sound "new"?
X : Harsh.
Me : Can't fix problems unless we're honest with ourselves. Real question is "why has it taken so long?"
X : Technology?
Me : The technology to achieve this "transformation" has been there for sometime. I believe the issue is "attitude" which is why the isolation economy has becoming a forcing function for change ...
In some cases, what goes back to the old status quo depends upon any new needs and emerging practices cementing the change.

In other cases, those practices already exist (i.e. DevOps) and it is simply a question of adoption.

Overall, the old status quo is now in the past.
X : I thought you said DevOps was the new legacy?
Me : It will be. I would focus on serverless and the emerging practices in that space. But I'm not blind to the issue that some are so far behind that adopting DevOps practices / IaaS would be a vast improvement on what exists.
X : I'm confused on the idea of serverless replacing DevOps.
Me : Serverless won't replace DevOps. What is happening is an emerging set of co-evolved practice built upon serverless (caused by a shift of the runtime from product to utility). This is creating a "new faction' ...
... that new faction I called "FinDev" long ago i.e. finance + development. The community seems to be settling on FinOps. It'll be a new faction that will differentiate itself from the old faction of DevOps which in turn distanced itself from the previous factions ...
... this is fairly normal practice of progress i.e. the creation of new factions, the dismissal of the past.

I've yet to see the IT industry evolve gracefully. I expect "FinOps" to co-opt many of the practice of DevOps but to deny that heritage and claim to be different ...
... with an intense focus by "FinOps" on capital flow, observability of capital in application, P&L for applications, refactoring having financial values etc etc.
New factions (i.e. this new collective around he practices of serverless) tend to create their own rituals, symbols and heroes etc. Hence we currently get the whole serverless vs container debate but this will ultimately become the "FinOps" vs DevOps debate unless ...
... we've suddenly developed a capability in IT to evolve without new factions. I suspect not. The old Next Generation vs "traditional" will continue i.e. the DevOps (next gen) vs ITIL ("legacy") debate will become the FinOps (next gen) vs DevOps ("legacy") debate. C'est la vie.
X : Do you see this happening?
Me : Signals seem to be there including the "laggards" to the new space being "early adopters" of the "old" space i.e. expect companies with extensive DevOps programs and IaaS investment (including home grown) to be laggards to the Serverless world.
X : DevOps is more than just IaaS. It covers culture.
Me : ITIL covered culture. Didn't stop us pinching the ideas, denying the heritage and claiming ITIL was something it wasn't. Factions are about collectives and beliefs, don't expect this to be rational.
X : What is "ILC Ecosystem"
Me : It's shorthand for saying "I'm too lazy to clean up that map". Not needed for this conversation, so here's a simplified map.
X : P&L per application?
Me : Even more than that. Capital flow within applications. Suddenly refactoring has financial value. It's old hat to the serverless community but a short hop from a cup of tea to applications. The power of billing per function.
X : Are those figures correct?
Me : Does it matter? It's an example from a 2017 presentation to emphasise a particular point - that we will be able to measure capital flow in applications. It's based upon the Zimki practice from 2005/06.
X : Zimki?
Me : Long story, not relevant.
X : I don't understand the Zimki part?
Me : Not relevant. All that matters is back in 2005, I had billing per function. It changes the way you invest, how you build, how you monitor ... everything. I've been through this long ago, ditto with @jamesaduncan ...
... a lot of people really don't understand how transformative billing per function is. It'll change and rock the business world ... just add time.
X : How can you know this?
Me : I've been there, done that, bought the T-Shirt. The world of IT is on for one helluva ride.
X : What is ILC?
Me : Old model (circa 2005). You'll find old posts online. It's a way of gaming a market to your advantage. The net effect is your rate of "innovation", efficiency and customer focus simultaneously increase with the size of your ecosystem.
X : Are there other ways of gaming a market?
Me : ILC is one of many.
X : Do you teach this?
Me : If you've been mapping for 5+ years and you've implemented decent principles (i.e. doctrine) then I'm happy to talk strategy / gameplay.
X : 5 years?
Me : Figure of speech. I'm not willing to talk strategy with people who don't understand their landscape. It's a waste of their time and my time.
X : Teaching is a waste of time?
Me : No, strategy is a waste of time.
X : Strategy is a waste of time?
Me : If you don't understand your landscape then yes. You may as well save time and money by clicking on the auto generator until you find something you like - https://strategy-madlibs.herokuapp.com/ 
X : I disagree.
Me : That's fine. Just ask anyone who maps on whether it has changed their decision making processes and what they now think of past strategic choices. Unfortunately, you won't really understand until you map.
You can follow @swardley.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.