Twitter | Search | |
Simon Wardley #EEA
X : How to deal with technical debt? Me : As a rough analogy, I will take liberties, let us start with out Tea Shop example with custom built kettles.
Reply Retweet Like More
Simon Wardley #EEA Dec 1
Replying to @swardley
Me : The first thing I do is mark on where things should be ... in this case our operations people are arguing that we should use standard kettles.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
I would then add metrics per unit provided (i.e. cup of tea). I will make an awful assumption that the only capital expense is the kettle (i.e. we have depreciation of the kettle) and everything else is variable - paper cups etc.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
I will then follow one flow through the map, create an income statement ... in this case the custom built kettle.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
For comparison, I will then follow a different flow using the standard kettle. As you can see, the use of a standard kettle makes a significant impact to income compared to the previous. This is the impact of my technical debt.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
X : But what has this got to do software? Me : Well, let us just imagine we're in a serverless world and add in functional billing. I'll use a car hire example mimicking the cup of tea world but using a custom built "car.getProfiles()"
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @simalexan
... from this you can calculate the impact of using some standard functions. You can therefore calculate a value to refactoring code. X : Can you really calculate capital flow in applications? Me : We're getting there. Ask
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
... this is the future of software engineering. A combination of development, architectural and finance skills. Monitoring, operating, refactoring and developing based upon capital flow. Even risk management will utilise this. The future practices are very different from today.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
Now, all those function components in the car hire map have a sub component - the platform and services consumed. I didn't draw them on there but you can if you wish ...
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
... under those sub components are things like orchestration, containers and on ... all the way to hardware, power and data centres. In a serverless world are you really going to give two hoots going down to this low level and try to optimise the capital expense involved?
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @forrestbrazeal
I'll leave it as an exercise for the reader (don't forget to add racks, buildings, security, aircon etc) but you'll soon discover that one faction is the future, the other is the past. Or as put it ...
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
... there is a reason why I describe containers as invisible subsystems. In the future, we're going to be too busy to care about them. It'll be like the Tea Shop arguing we should spend $0.5M on our own power generator as we can get a better price ... far from the user need.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
X : Why is there no cost with location.verify()? Me : Did I say something about this being a rough analogy with me making lots of assumptions and taking liberties? X : Yes Me : Ok then. I'm simply pointing the way, not giving you a fully worked example.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
X : Given the state of enterprises, how long will this take? Me : For some, they'll be doing this in a few years. Others will take 15-20 years or possibly simply disappear in a puff of bankruptcy as they are both outpaced and their cost efficiency is just too low.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @mengwong
X : What industries will this impact? Me : Any which have technology ... in other words, almost everyone. Even Lawyers - go talk to on that front.
Reply Retweet Like
Sangeet Paul C Dec 1
Replying to @swardley @mengwong
Finally, the intersection of maps and :)
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @sanguit @mengwong
I know , I take a great interest in his work. We mapped out part of the legal industry ... many years ago.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
X : But containers allow for portability. Me : We can talk about all the other connected services, operational parameters, our history with lock-in, second sourcing etc but I won't, I'll keep it simple. Portability is a nice to have. Billing per function changes the world.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
X : What do you think the future of software will be? Me : Voice (conversational programming), maps and capital flow. X : Then why are so many enterprises investing in containers? Me : I mostly assume it's executives with an eye on retirement and no eyes on the landscape.
Reply Retweet Like
Simon Wardley #EEA Dec 1
Replying to @swardley
X : How do you deal with resistance to changing the function or kettle? Me : First be aware. Marked that up for you. Now, consider the 16 different forms of inertia which you're likely to face.
Reply Retweet Like