To be fair it’s a notoriously difficult thing to plan for. It’s less about incompetence, and more about having a strong understanding of user requirements, and a streamlined way to allocate costs to each business area based on their needs. That’s really hard for any company or MSP to do.
Variable costs means you never want to over invest in unused cores and memory, which leads to over subscribing those cores and memory… that’s fine for normal working hours, except Monday mornings when everyone starts logging in at once.
You can’t really queue logins that in a way that doesn’t make users think they’re using an infuriatingly slow machine.
I disagree. Are people really that attached to their conversations though?
Anecdotally, the vast majority of my own conversations and coding interactions are transient in nature, to the point where I prefer to use the ‘temporary’ mode in whatever tool I’m using.
For coding, every project needs a plan and readme to get whatever agent back up to speed with what the task is. Anyone with a paid-for GH Copilot license knows that you can just switch between whatever provider at a whim, depending on the needs of your task or financial requirements.
I think people will find it easier to revert back to Siri 2.0 if that ever materialises, in which case the stickiness moat is bridged by a more familiar and widely integrated abstraction layer.
I see quarries everywhere, and they’re kind of required near any city or road project around Australia. Never considered them as a mine though… more like a ‘general resource site’?
reply