Is it me, or will this just speed up the timeline where a 'good enough' open model (Qwen? Deepseek? - I'm sure the Chinese will see a value in undermining OpenAI/Anthropic/Google) combined with good enough/cheap hardware (10x inference improvement in a M7 Macbook Air?) makes running something like opencode code locally a no brainer?
The good enough alternative models are here or will be soon, depending on your definition of good enough. MiniMax-M2.5 looks really competitive and its a tenth of the cost of Sonnet-4.6 (they also have subscriptions).
Running locally is going to require a lot of memory, compute, and energy for the foreseeable future which makes it really hard to compete with ~$20/mo subscriptions.
People running models locally has always been the scare for the sama's of the world. "Wait, I don't need you to generate these responses for me? I can get the same results myself?"
Personally I am already there- I go to Qwen and Deepseek locally via ollama for my dumb questions and small tasks, and only go to Claude if they fail. I do this partially because I am just so tired of everything I do over a network being logged, tracked, mined and monetized, and also partially because I would like my end state to be using all local tools, at least for personal stuff.
I picked up an M3Pro/11/14/36GB/1TB to 'test' over the long holiday return period to see if I need an M3 Max. For my workflow (similar to blog post) - I don't! I'm very happy with this machine.
Die shots show the CPU cores take up so little space compared to GPUs on both the Pro and Max... I wonder why.
Can anyone ELI5 - Is the compound/material used for LK-99 that unique? Are there other, similar materials that might also have this 'quantum well' quality?
It's relatively common materials, basically, lead, copper, sulfur, and oxygen, combined in a specific manner.
There is a chance that either the original measurements were wrong or that there remains some unrealized step in the process to make the superconductor superconduct.
I get that, that’s what I do with my team, but I’ve never heard that referred to as “doing Kanban”. Maybe I’m just being pedantic, but writing an article to say “you don’t need Scrum, just pull tasks off the board” completely misses the point of why teams use Scrum.
Scrum is pushing stuff into a sprint. Kanban is pulling the highest priority stuff through - it's done when it's done.
Metrics/Analytics can be calculated when your done based on actual information, as opposed to the beginning when you're guessing, and likely to be held to your estimates.
For us, visibility isn’t an issue. I would say estimations are by far the biggest struggle we have in “doing Kanban”. Luckily, they’re not super important for us and I usually bubble up a very rough estimate in monthly reports to management, but in an org where they matter more, I can absolutely see why Scrum gets adopted the way it does.
Why do you estimate when using a kanban? You might look at an item and break it down for simplicity. You also might go in with a goal of 'one card per member per day' or something similar. But nothing should be fixed to an estimate. If something is delayed, it should show up stuck in a lane. Respond as needed.
Because work is deadline driven by whoever is paying the teams' salaries. If you can't accurately estimate when you can get it done, you break it down until you can you get replaced by someone who can.
reply