end of chapter 2. idk, author is introducing incredibly backwards vocab to think about services: artifacts, events, resources, capabilities, shortfalls and shortcomings, X for affordance, Y for performance (which should be named executions). What is happening? Takeaways: define the 'whys' and the 'soul' of service not to loose yourself in overcomplicated service scripts. Always look at the whole AND parts.
— Mar 19, 2022 04:54AM
Add a comment