Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://hachyderm.io/users/inthehands/statuses/111976542943535393">Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 23-Feb-2024 03:27:30 JST</a><a href="https://hachyderm.io/@inthehands" title="inthehands@hachyderm.io"><img src="https://gnusocial.jp/avatar/53259-48-20231130154634.webp" width="48" height="48" alt="Paul Cantrell" style="position: absolute; left: 0; top: 0;">Paul Cantrell</a><div><a href="https://aus.social/@Steveg58/111975508643728138" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/147649" title="raven667@hachyderm.io">Raven667</a></li></ul></div></section><article><p><a href="https://aus.social/@Steveg58">@Steveg58</a> <a href="https://hachyderm.io/@raven667">@raven667</a> Rigid specifications, blocked communication, and CYA-first thinking all go hand in hand. It’s a tough hole for an org to crawl out of.</p><p>At best, a spec is a tool of communication, a light to shine misunderstandings and hidden assumptions into sharp relief. At worst, it’s a legal prop.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2746621#notice-5452189">In conversation</a><time datetime="2024-02-23T03:27:30+09:00" title="Friday, 23-Feb-2024 03:27:30 JST">about a year ago</time> <span>from <span><a href="https://hachyderm.io/@inthehands/111976542943535393" rel="external" title="Sent from hachyderm.io via ActivityPub">hachyderm.io</a></span></span><a href="https://hachyderm.io/@inthehands/111976542943535393">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="http://of.At/">of.at - Shopping リソースおよび情報</a></h5><div></div></header><div>of.at は、あなたがお探しの情報の全ての最新かつ最適なソースです。一般トピックからここから検索できる内容は、of.atが全てとなります。あなたがお探しの内容が見つかることを願っています！</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 23-Feb-2024 03:27:30 JSTPaul Cantrell
in reply to
- Steveg58
- Raven667
@Steveg58 @raven667 Rigid specifications, blocked communication, and CYA-first thinking all go hand in hand. It’s a tough hole for an org to crawl out of.
At best, a spec is a tool of communication, a light to shine misunderstandings and hidden assumptions into sharp relief. At worst, it’s a legal prop.
In conversationabout a year ago from hachyderm.iopermalink
Attachments
1. No result found on File_thumbnail lookup.
  of.at - Shopping リソースおよび情報
  of.at は、あなたがお探しの情報の全ての最新かつ最適なソースです。一般トピックからここから検索できる内容は、of.atが全てとなります。あなたがお探しの内容が見つかることを願っています！

Public

Embed Notice

HTML Code

Corresponding Notice