“These days, I'm sure the vast majority of people who've used an "agile card wall" for the purpose of prioritizing work and communicating status have only done so with a mediocre web app featuring awkward horizontal scrolling and glitchy drag-and-drop of "cards." Not a physical wall with paper index cards and sharpies that always ran dry too fucking fast.”
Are you calling me old, @searls? It sure as shit feels like you’re saying I’m old. And you’re not wrong, but DAMN!
https://justin.searls.co/mails/2024-08/
=> More informations about this toot | More toots from stevenharman@ruby.social
@searls
“Every opinionated issue tracker company eventually sells out its own product and gradually removes their thoughtful design constraints until it resembles a somehow-even-worse version of JIRA before the whole thing slides into irrelevance.”
=> More informations about this toot | More toots from stevenharman@ruby.social
@stevenharman @searls every product that produces inventories of issues is doomed to the same fate. Customers who process issues under statistical control only ever need the minimal set of common features. Those are also the customers who aren’t dysfunctional. That means the only customers who need new features (and thus even consider differentiators) are by definition dysfunctional organizations. The issue tracker market is therefore fundamentally prone to produce market failure
=> More informations about this toot | More toots from ntl@ruby.social
@stevenharman @searls (long winded way of saying, “I totally agree, and here’s my theory for why 😂)
=> More informations about this toot | More toots from ntl@ruby.social
@ntl Listen here, sir, we are here for arguments and dunking, with zero
room for nuance, compassion, nor compromise! We gotta score them Internet Points!
Oh. Wait. That was the old place. 🤣
=> More informations about this toot | More toots from stevenharman@ruby.social
text/geminiThis content has been proxied by September (3851b).