Can someone fix the damn Slack plugin so it stops asking me to turn it on every time someone posts a Jira link? I have dozens of messages from the plugin saying "Got it! Will not ask you again."
Right! There is more performance to be taken away yet! They're nearly there but plenty is left. Jira can be made "let's go brew coffee and come back" slow if the really tried
All the design hints required for this or any other type of agentic "set it and forget it" development are interesting to me, because they enable the result but also lock in less-than-desirable results that exhibit a miss "like simulating a 2Mhz clock".
What if Agents were hip enough to recognize that they have navigated into a specialized area and need additional hinting? "I'm set up for CP/M development, but what I really need now is Z80 memory management technique. Let me swap my tool head for the low-level Z80 unit..."
We can throw RAGs on the pile and hope the context window includes the relevant tokens, but what if there were pointers instead?
Makes sense for all the people running Ubuntu under emulated RISC-V who want/need to use snaps for package management, I guess?
Since there aren't boards available that can run 25.10, why even bother packaging for that architecture? Why dig trenches for cable that can't be laid?
Can we go back to IRC now? Slack took what we were already doing with IRC, replaced the duct tape and firewalks, packaged up the key functionality (channels, file sharing, access) with a purple UI and mobile app and went to market.
The days of a single company maintaining a grip on something like workplace chat (and the inherent data) are numbered now. We're not building a C compiler.
Time will come when their subscription fee competes directly with another spend that can generate bespoke but commonplace business tools like chat with no data egress (or better yet, a demonstration that what you now keep and can act on what you previously paid Salesforce to steal.) Soon.
I have never seen a shopper testing out the wares.
reply