Articles by the same author

The antispy tool for a new OpenAI agent message board

The front end is not less risky to hand to the agent. There are a thousand different ways the agent could bork the UI and say it's good. And knowing how to babysit the AI/Agents doing the UI is more important than ever. Yeah I agree that developer education in the front end space seems to be 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 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. It's not "original". Depending on your definition of that word, it's either a comparatively modern fake, or the current evolution of something that's always evolving. For perspective: the stones now have concrete bases. Officials were concerned in the 1920s that the "conservation work" being done at that time was starting to head into "faking" the monument. Cranes were used to provide Virtual Thread-like behaviour for scripts. Blocking operations suspend a script which is then resumed from where it left off once the operation completes.

This risk factor is similar to the way Kotlin implements coroutine. I believe Kotlin goes to the extra miles to also capture parts of the stack frames when creating the Continuation object so even when the runtime resume the continuation, the exceptions thrown later get the "correct" stack trace (not the one that shows that you come from a call through a MethodHandle). 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 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. It's not "original". Depending on your definition of that word, it's either a comparatively modern fake, or the current evolution of something that's always evolving. For perspective: the stones now have concrete bases. Officials were concerned in the 1920s that the "conservation work" being done at that time was starting to head into "faking" the monument. Cranes were used to provide Virtual Thread-like behaviour for scripts. Blocking operations suspend a script which is then resumed from where it left off once the operation completes. This is what I got: Seojun - Seojun is not a real person. But his life story is created from the statistical reality of the Korean Peninsula in 1999 CE. In 1999 CE, Seojun was born in the countryside near Pongch'ŏn-ŭp. His village is home to about 250 people. Among four children, he was the fourth. He eats largely rice, soybean paste and tofu, dried fish and shellfish, and pickled cabbage and radish, with persimmon and jujube in season, and tea as well. He knows how to talk to mine. No one at ElevenLabs knows or cares about our implementation details. HN has trouble seeing past the "developer in a terminal coding with Claude Code" use case for using AI. Real production agents have use cases that are very different! When you don't own every piece of an integration with another system, there needs to be a lot of ‘privacy' tools popping up on github lately. It's a good time to be wary of any if you don't trust the author 100%. It's like when HIV emerged in the 80s - the disco days of free love are over. Be wary of who you're sleeping with, and always wear a condom.

As the last two paragraphs of TFA point out, this idea is now widely discredited. However, there are 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. It's not "original". Depending on your definition of that word, it's either a comparatively modern fake, or the current evolution of something that's always evolving. For perspective: the stones now have concrete bases. Officials were concerned in the 1920s that the "conservation work" being done at that time was starting to head into "faking" the monument. Cranes were used to provide Virtual Thread-like behaviour for scripts. Blocking operations suspend a script which is then resumed from where it left off once the operation completes. Over the past 3 months we've been using it a LOT. I made one for our admins so they can work with the CMS and get statistics in their client, the statistics part has been a huge unlock. The big advantage here is that a lot of current electric aircraft development seems to be 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 rancher one is the worst. We develop custom MCP servers for our internal stuff for agents to use, and it all gets accessed thru agentgateway. I don't really like having to use MCP but we don't have a good solution for authorizing individual calls outbound from a sandbox without choosing to just not care about the sandbox.