Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/RuthMalan/statuses/113262101892984266">Ruth Malan (ruthmalan@mastodon.social)'s status on Monday, 07-Oct-2024 05:43:57 JST</a><a href="https://mastodon.social/@RuthMalan" title="ruthmalan@mastodon.social"><img src="https://gnusocial.jp/avatar/117020-48-20230505180452.webp" width="48" height="48" alt="Ruth Malan" style="position: absolute; left: 0; top: 0;">Ruth Malan</a><div><ul><li></ul></div></section><article><p>This, from <a href="https://mastodon.social/@bitboss">@bitboss</a> (Updated: The model(s), in any language, is to create common ground -- shared expectations and commitments.)</p><p>See also: Visual Agility: Why We Model<br><a href="https://www.linkedin.com/pulse/visual-agility-why-we-model-ruth-malan/" rel="nofollow noreferrer">https://www.linkedin.com/pulse/visual-agility-why-we-model-ruth-malan/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3783875#notice-7405454">In conversation</a><time datetime="2024-10-07T05:43:57+09:00" title="Monday, 07-Oct-2024 05:43:57 JST">about 4 months ago</time> <span>from <span><a href="https://mastodon.social/@RuthMalan/113262101892984266" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@RuthMalan/113262101892984266">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3271596">Chart showing:Modeling isA LOT about:
Having a cross-functional conversation
Visualizing ideas together
Aligning different perspectivesAnd very little about:
Telling others what to do with UML</a></label><br><a href="https://files.mastodon.social/media_attachments/files/113/262/058/251/126/257/original/78c4e0a1b0cf775b.png" rel="external">https://files.mastodon.social/media_attachments/files/113/262/058/251/126/257/original/78c4e0a1b0cf775b.png</a></li><li><article><header><div>Domain not in remote thumbnail source whitelist: media.licdn.com</div><h5><a href="https://www.linkedin.com/pulse/visual-agility-why-we-model-ruth-malan/">Visual Agility: Why We Model</a></h5><div></div></header><div>Context for this Discussion Design of complex systems is hard -- wickedly hard! It takes all the cognitive assist we can muster. Trade-offs must be made because there is interaction -- not just interaction among components to create a capability, but interaction among properties.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Ruth Malan (ruthmalan@mastodon.social)'s status on Monday, 07-Oct-2024 05:43:57 JSTRuth Malan
- Michael Plöd
This, from @bitboss (Updated: The model(s), in any language, is to create common ground -- shared expectations and commitments.)
See also: Visual Agility: Why We Model
https://www.linkedin.com/pulse/visual-agility-why-we-model-ruth-malan/
In conversationabout 4 months ago from mastodon.socialpermalink
Attachments
1. Chart showing: Modeling is A LOT about: Having a cross-functional conversation Visualizing ideas together Aligning different perspectives And very little about: Telling others what to do with UML
  https://files.mastodon.social/media_attachments/files/113/262/058/251/126/257/original/78c4e0a1b0cf775b.png
2. Domain not in remote thumbnail source whitelist: media.licdn.com
  Visual Agility: Why We Model
  Context for this Discussion Design of complex systems is hard -- wickedly hard! It takes all the cognitive assist we can muster. Trade-offs must be made because there is interaction -- not just interaction among components to create a capability, but interaction among properties.

Public

Embed Notice

HTML Code

Corresponding Notice