Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://dair-community.social/users/trochee/statuses/112265334953012633">Jeremy Kahn (trochee@dair-community.social)'s status on Sunday, 14-Apr-2024 03:59:58 JST</a><a href="https://dair-community.social/@trochee" title="trochee@dair-community.social"><img src="https://gnusocial.jp/avatar/80072-48-20240526045552.webp" width="48" height="48" alt="Jeremy Kahn" style="position: absolute; left: 0; top: 0;">Jeremy Kahn</a><div><a href="https://triangletoot.party/@donaldball/112265237082882023" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/110920" title="donaldball@triangletoot.party">Donald Ball</a></li></ul></div></section><article><p><a href="https://triangletoot.party/@donaldball">@donaldball</a></p><p>Indeed there are plenty of cases where the engineers' solution is _worse_ , because they've added a technical problem — the maintenance and configuration of a tool — to what was previously a business problem</p><p>("Now you have two problems")</p><p>Many technologies fit in this antipattern. I've seen it peak multiple times<br> regex 1999<br> XML 2003<br> "big data" 2007<br> "machine learning" 2010<br> "put a neural net on it" 2012<br> "Blockchain" 2013<br> "put a chatbot on it" 2016<br> GPTs 2022?</p><p><a href="https://hachyderm.io/@inthehands">@inthehands</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2934876#notice-5839422">In conversation</a><time datetime="2024-04-14T03:59:58+09:00" title="Sunday, 14-Apr-2024 03:59:58 JST">about 7 months ago</time> <span>from <span><a href="https://dair-community.social/@trochee/112265334953012633" rel="external" title="Sent from dair-community.social via ActivityPub">dair-community.social</a></span></span><a href="https://dair-community.social/@trochee/112265334953012633">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
Jeremy Kahn (trochee@dair-community.social)'s status on Sunday, 14-Apr-2024 03:59:58 JSTJeremy Kahn
in reply to
- Paul Cantrell
- Donald Ball
@donaldball
Indeed there are plenty of cases where the engineers' solution is _worse_ , because they've added a technical problem — the maintenance and configuration of a tool — to what was previously a business problem
("Now you have two problems")
Many technologies fit in this antipattern. I've seen it peak multiple times
regex 1999
XML 2003
"big data" 2007
"machine learning" 2010
"put a neural net on it" 2012
"Blockchain" 2013
"put a chatbot on it" 2016
GPTs 2022?
@inthehands
In conversationabout 7 months ago from dair-community.socialpermalink

Public

Embed Notice

HTML Code

Corresponding Notice