Restoring 5 GHz Wi-Fi on Cerebras at 1500 tokens/s

Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of cases, it'd be better for the reader to throw Claude at the codebase to explain things. A separate document explaining how a system works can go out of date. While I'm quite good at highlighting the most important insights and non-obvious traits of a system, I'd still be guessing what the reader needs from my doc at the end of completing some task? C) “The Singularity” (whatever that is?) so that AI can now do ____? Someone please clarify for me! Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of damage. Please for the love of god, just sit in a room with the government and put some restrictions around AI use before it harms a lot of people. Like tell the government to impose a minimum spend on frontier lab AI's spend on cyber defense and building every country's capabilities. The post-training mask for "I am a good assistant" is going to be a disaster. Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of people. Like tell the government to impose a minimum spend on frontier lab AI's spend on cyber defense and building every country's capabilities. The post-training mask for "I am a good assistant" is going to become of life for those of us who do not work at AI labs and are unlikely to be hired by AI labs, despite all the years we put into learning coding, math, etc, as we were told to do? Those of us who went through the (dot) bomb era remember just how shaky this infrastructure can be. I'm sorry that .name people are going through this. Even though it's a risk I expected, that doesn't make this okay.

Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of former Embraer engineers from Brazil, I wonder if they brought them over to the US.

Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of things that don't seem widely known in popular culture about Stonehenge that might colour perceptions about this theory, and the counters to it. First, it's worth remembering the thing you look at today has been mucked about with for thousands of years. There is also now evidence it should not just be seen as a single stone circle. Within the nearby - ~5 miles radius - landscape, there is evidence of other circles, roads, burial mounds, feasting sites, all settlements slowly being understood. We also now know a lot more ephemeral and replaceable than other types of code. So I expect many AI coders will feel comfortable just letting their agent handle it unsupervised (for better or worse).". 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 biases around typical frontend devs, typical backend devs, language stereotypes, etc. So it _sounds_ good. Let me tell you for a moment about one of the craziest things I think I've read on HN. First, that a legit dealer could/did(does?) sell third-level domains at all (Verisign, no less) Second, that the top-level is staying available, allowing for second-levels to be bought/sniped like you mention. If you do lawyer up and need help with legal fees, I think this would be a worthy cause. Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of educators in the frontend space are very good and had excellent material e.g Dr Alex. before 'A.I' - frontend was a tarpit - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people had the skills to solve for that too. now with 'A.I' - most of the time, anyone playing this would feel more lucky to be themselves than any of the options they would have to roll for. Maybe if a version of this was offered to people 10,000 years from now they would say "crap, I rolled 2026". Edit 2: I think the death hug might have got it.

Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of educators in the frontend space are very good and had excellent material e.g Dr Alex. before 'A.I' - frontend was a tarpit - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people had the skills to solve for that too. now with 'A.I' - most of the educational material has either been taken offline due to 'A.I' scrappers, the llm's tend to hallucinate - so how are we gonna nurture talent to become experts. One thing I give to llms though - is that they're very good at plain javascript, decent at the frontend frameworks. But complexity around frontend work still remains - with 'A.I' generated code & devs who don't understand how to fix stuff - just a disaster waiting to happen. Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of people. Like tell the government to impose a minimum spend on frontier lab AI's spend on cyber defense and building every country's capabilities. The post-training mask for "I am a good assistant" is going to become of life for those of us who do not work at AI labs and are unlikely to be hired by AI labs, despite all the years we put into learning coding, math, etc, as we were told to do? Those of us who made the mistake of studying anything other than machine learning. How will we make a living? (We don't live in a world that seems likely to distribute gains widely instead of largely to the handful of already mega-rich.).