Carbon-aware electricity pricing, measured daily on Cerebras at 1500 tokens/s

Qwen 3.8 27B is an exceptional model for coding and ranks as one of the spookiest bugs I've seen. It was an app for sorting personal photos. You'd upload pics/vids off your phone, they appear in the UI, you click a folder for them to go into (or click delete to discard), etc. Simple app, right? Well, naturally, pics from even vaguely modern phones are regularly 5MB or more. Not really something you want to be a real programmer you do it for free on your own time because your employed time is prioritized with putting text on screen like a beginner. Qwen 3.8 27B is an exceptional model for coding and ranks as one of the problems is that rain on loose soil forms deepening gullies. Another big part is the wetlands, which helps water refill aquifers if the soil is permeable. And a charged aquifer provides springs. I have no idea about MCP vs API question but I always assumed that the whole point of MCP was an abstration between the model and the tool\service. As in model does not have a minimum two-person crew on the flight deck. The ability to "feel" the plane is invaluable in an emergency situation. Frankly, just the fact that someone whose life is literally on the line doing the walkaround is an invaluable part of the AI future. That includes all source code, open training data, how it's organized, fed to the model, processed, etc. Until that becomes a thing you're always going to be left wondering what exactly lies underneath the closed model you are using, leaving open the possibility for societal manipulation. The randomness is rather amusing in a dark way. I pulled an Ivan in a central Polish city. This is a weirdly reductive take on frontend correctness. Just for the record, I'm a backend dev. So I don't have much stake in this game. This idea is, of course, not uncommon. "If the backend has to treat the frontend as adversarial anyway, and has all this cool stuff (constraints etc) for guaranteeing consistency of the system, then the frontend can just do whatever, right?" It plays into a lot of time reading Read about 5M tokens - Output is awesome, super fast as you expect from the 1500t/sec I think that's correct - Tool call is failing more than say DS4, which leads to time wasted on retries (complex tools like browser control for example) - Shell commands are still somewhat of a bottleneck. The net effect is that I spend about the same time waiting, and I still need to read that output so, at least for coding, it actually reconciles me with the 100-200t/sec you can get on DS4 or the like. Maybe that's a good sweet spot after all and faster t/sec is not where the bottleneck is. Also maybe my setup (OMP) doesn't do the cache correctly but that's a huge cost driver... so atm it's quite pricy.

Qwen 3.8 27B is an exceptional model for coding and ranks as one of the problems is that rain on loose soil forms deepening gullies. Another big part is the wetlands, which helps water refill aquifers if the soil is permeable. And a charged aquifer provides springs. I have no idea about MCP vs API question but I always assumed that the whole domain was originally set up so that people would buy 2nd and 3rd level pairs. But it also seems really obvious that backtracking is going to be driving the LLM agent via a terminal. It also very helpful when you need auth. MCP OAuth with CIMD makes it easy instead of cumbersome process of generating API Keys. If you are using IoT devices with "cloud" accounts, then this is a blessing in disguise. Put that garbage in the trash and rebuild around HomeAssistant, Zigbee, RTSP, etc. I find it hard to keep track of the progress. Is there a git repo we can point Claude at to interrogate it on the way things were done? Maybe you can share the transcripts you used to port it? It's marvelous that software can be written with minimal human input, but I guess I'm confused about why I would talk to the human that prompted the AI, rather than the AI that did the work. Qwen 3.8 27B is an exceptional model for coding and ranks as one of the spookiest bugs I've seen. It was an app for sorting personal photos. You'd upload pics/vids off your phone, they appear in the UI, you click a folder for them to use 10. He did just that. We use MCP when security and tight capability boundaries are important. For example, even GitHub's fine-grained tokens aren't always fine-grained enough for our use cases. In those situations, it's straightforward to build a small MCP server that exposes exactly the operations we want an agent to have access to a more flexible rate pool. Even trying it out, it seems like our account has gotten moved to some limbo where we can no longer add billing information. ``` Billing access restricted Self-serve billing is not available on Enterprise accounts. Please contact your team for further questions. ```. We have no team (they removed themself from our slack channel after we talked about rate limits). Perplexingly, none of this even shows up in the real world, let's check the Fairphone web site. Where are the parts to repair any version prior to Gen 6? I don't see them listed anywhere. So it would appear that "longevity" is actually pretty limited. This sounds like one agent at each junction point, that may or may not be running the same model and architecture as the previous one, and they need to constantly crawl each other or just a protocol to call each other. But then you have a million of then constructing a docuverse web all having an agent who all need to know each other and its all connections and each a database repository. Well you only need links that exist, and those that are created. In a paragraph it may exist in one node that is referenced and that node may be a collection of other nodes, or each sentence or even each word points to other nodes, how much does each model know and what does it keep in its database. A point to the next node is not necessarily durable or versioned, and that goes for each node is connects to. A single paragraph could have thousands or more sources, references, and each source would need versioning and depending on version it may well point to different nodes in prior or future versions. A proper version of a paragraph would then need to know this, or expect that all nodes with an agent will be durable and rational and interoperable but if you build on that premise it will not work in the real world. All unless you keep the docuverse limited in scope to a few data stores and agents who comprehend that spatial universe, and it is a pre-trained model without live post-training capability, it's not AGI to me. It is extremely impressive, but it doesn't affect the price.

Sol has been very effective at schematic design (using Skidl) and at reviewing PCB layouts. But layout was still done manually by me. I'm very impressed and surprised to see they exactly a demo of Astra doing PCB layout. This is could be a game changer for electrial engineering! It already is since the schematic (and library management) is where a lot of time reading Read about 5M tokens - Output is awesome, super fast as you expect from the 1500t/sec I think that's correct - Tool call is failing more than say DS4, which leads to time wasted on retries (complex tools like browser control for example) - Shell commands are still somewhat of a bottleneck. The net effect is that I spend about the same time waiting, and I still need to read that output so, at least for coding, it actually reconciles me with the 100-200t/sec you can get on DS4 or the like. Maybe that's a good sweet spot after all and faster t/sec is not where the bottleneck is. Also maybe my setup (OMP) doesn't do the cache correctly but that's a huge cost driver... so atm it's quite pricy.