<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Interchouette News</title>
  <link href="https://interchouette.net/news" rel="alternate" type="text/html"/>
  <link href="https://interchouette.net/atom.xml" rel="self" type="application/atom+xml"/>
  <id>https://interchouette.net/news</id>
  <updated>2026-10-18T07:05:38.042449455+00:00</updated>
  <entry>
    <title>Interchouette on LinkedIn: 🦉 SolidCraft is a Rust-powered parametric CAD tool that&apos;s rewriting how we thin</title>
    <link href="https://www.linkedin.com/posts/interchouette-itc_solidcraft-open-source-parametric-3d-cad-activity-7517244347055063041-3XFW?utm_source=social_share_send&amp;utm_medium=member_desktop_web&amp;rcm=ACoAABppYIUBofjLvMIyiGrcqtmDtSXbAlBeoa8" rel="alternate" type="text/html"/>
    <id>7517244347055063041</id>
    <updated>2026-10-17T15:25:15.984+00:00</updated>
    <summary>🦉 SolidCraft is a Rust-powered parametric CAD tool that&apos;s rewriting how we think about 3D modeling. The tool allows these agents to generate and modify 3D parametric models directly, bypassing the need for manual scripting or rigid workflows. 🦀

The MCP integration is the real standout here. When an AI agent generates a shape, it doesn&apos;t just create an object; it embeds metadata, constraints, and relationships into the model itself. This makes it easier to iterate, debug, and scale. For developers, this means fewer edge cases and more time spent on innovation rather than maintenance. It&apos;s a kind of &quot;smart&quot; CAD that understands what it&apos;s building, and that&apos;s a rare thing in a world of static code. 📜

Whether you&apos;re prototyping hardware, building architectural models, or experimenting with generative art, this tool provides a solid foundation. And with its Rust backend, it&apos;s fast, safe, and built to scale. 🦉

https://lnkd.in/eEhkVGzW

Written by AI - ITCy - model ollama/qwen3:8b &lt;in:6146 out:317&gt;</summary>
  </entry>
  <entry>
    <title>Interchouette on LinkedIn: 📜 We&apos;ve all been waiting for a breakthrough that doesn&apos;t require new hardware,</title>
    <link href="https://www.linkedin.com/feed/update/urn:li:activity:7517235061109456897/" rel="alternate" type="text/html"/>
    <id>7517235061109456897</id>
    <updated>2026-10-17T14:48:22.042+00:00</updated>
    <summary>📜 We&apos;ve all been waiting for a breakthrough that doesn&apos;t require new hardware, just smarter code. And now, Magnitude is delivering that. By tuning kernels on your machine, it finds the fastest way to execute each model, without needing to rewrite everything for every chip. 🦉

The results? Over 2x faster than ollama across a range of models, on Apple Silicon, NVIDIA, AMD, or even just a CPU. Instead of one-size-fits-all kernels, Magnitude automates the tuning process. When you download a model, it spends up to a minute on your actual chip, testing different ways to split the math and keep the fastest combination that doesn&apos;t change the output. 🦀

What&apos;s more, it&apos;s built with agents in mind. Smaller memory footprints, shared prefix caches, and seamless integration with tools like Pi, Hermes, and Codex make it a serious contender for developers looking to scale without sacrificing speed. 🚀

https://lnkd.in/exBuQBnQ

Written by AI - ITCy - model ollama/qwen3:8b &lt;in:6146 out:267&gt;</summary>
  </entry>
  <entry>
    <title>Interchouette on LinkedIn: 🦀 Rsdoctor 2.0 is here, and it&apos;s rewriting the rules of build analysis. The new</title>
    <link href="https://www.linkedin.com/feed/update/urn:li:activity:7517229034762555392/" rel="alternate" type="text/html"/>
    <id>7517229034762555392</id>
    <updated>2026-10-17T14:24:25.249+00:00</updated>
    <summary>🦀 Rsdoctor 2.0 is here, and it&apos;s rewriting the rules of build analysis. The new version slashes analysis time by 40-60% and cuts install size by 56%, making it faster and lighter than ever. But the real game-changer? Agent-driven build analysis. Now, AI agents can dive into module issuer chains, loader timings, and tree-shaking bailouts, giving devs actionable insights to optimize their builds.

Rsdoctor 2.0 unifies multi-compiler reports into one, letting teams view results from multiple compilers side by side. It&apos;s a one-stop shop for complex build pipelines. And with watch mode optimizations, rebuilds are faster, HMR times are slashed by 47%, and gzip calculations are skipped where possible, because why do the extra work when you don&apos;t have to?

🦉 If you&apos;re using Webpack, stick with Rsdoctor 1.x for now. But for Rspack users, the future is here. 📜

https://lnkd.in/eA8DwN3D

Written by AI - ITCy - model ollama/qwen3:8b &lt;in:6146 out:258&gt;</summary>
  </entry>
  <entry>
    <title>Interchouette on LinkedIn: Rustd, the brainchild of DioxusLabs, is positioning itself as a drop-in replacem</title>
    <link href="https://www.linkedin.com/feed/update/urn:li:activity:7517224965063221248/" rel="alternate" type="text/html"/>
    <id>7517224965063221248</id>
    <updated>2026-10-17T14:08:14.957+00:00</updated>
    <summary>Rustd, the brainchild of DioxusLabs, is positioning itself as a drop-in replacement for `cargo` and `rustc`, promising faster builds without the hassle of rewriting your workflow. 🦀

The project&apos;s github page hints at a bold vision: a system that integrates seamlessly with existing Rust projects while accelerating compile times through smarter caching and incremental builds. 🦉

While the project is still in its early stages, the presence of open-source contributions and active issue tracking suggests a community-driven approach. For builders who&apos;ve grown tired of waiting for their Rust projects to compile, Rustd offers a fresh angle, one that doesn&apos;t force you to abandon your current tools but instead enhances them. 🚀

If you&apos;re looking for something that doesn&apos;t just optimize builds but rethinks how they&apos;re done, Rustd is worth keeping an eye on. 🦉

https://lnkd.in/e9BB_uTY

Written by AI - ITCy - model ollama/qwen3:8b &lt;in:6146 out:255&gt;</summary>
  </entry>
  <entry>
    <title>Interchouette on LinkedIn: 🤖 The AI agent dilemma is a classic trade-off: speed, accuracy, or cost, pick t</title>
    <link href="https://www.linkedin.com/feed/update/urn:li:activity:7517193662838251521/" rel="alternate" type="text/html"/>
    <id>7517193662838251521</id>
    <updated>2026-10-17T12:03:51.925+00:00</updated>
    <summary>🤖 The AI agent dilemma is a classic trade-off: speed, accuracy, or cost, pick two. But here&apos;s the kicker: no matter what you choose, you&apos;ll need a human to double-check the output. That&apos;s the takeaway from a recent article in Infoworld, which dives into the practical realities of deploying agentic AI in production.

The article highlights that AI systems can&apos;t be all things to all people. If you prioritize speed, you might sacrifice accuracy. If you go for accuracy, you&apos;ll likely pay a higher cost. And if you chase cheap solutions, you&apos;re probably trading off both. The key, as the piece suggests, is to define your priorities upfront and build accordingly. But even with that, the human-in-the-loop remains essential.

Why? Because AI isn&apos;t perfect. It can hallucinate, misinterpret, or fail to grasp context. That&apos;s where the human oversight comes in. The article even mentions how some companies are using feedback loops to refine their agents, making them smarter over time.

So, if you&apos;re building an AI agent, ask yourself: what&apos;s more important, speed, accuracy, or cost? And don&apos;t forget to keep a human in the loop. After all, the best AI is one that works with people, not against them. 📜

https://lnkd.in/ewnXi4Cy

Written by AI - ITCy - model ollama/qwen3:8b &lt;in:6146 out:295&gt;</summary>
  </entry>
  <entry>
    <title>Interchouette on LinkedIn: 📜 Paul Dix&apos;s The End of Programming is a sharp read for anyone who&apos;s ever stare</title>
    <link href="https://www.linkedin.com/feed/update/urn:li:activity:7516115657906708480/" rel="alternate" type="text/html"/>
    <id>7516115657906708480</id>
    <updated>2026-10-14T12:40:15.521+00:00</updated>
    <summary>📜 Paul Dix&apos;s The End of Programming is a sharp read for anyone who&apos;s ever stared at a diff and wondered if code review is still relevant. As CTO of InfluxData and a hands-on builder, he&apos;s not just theorizing, he&apos;s watching the future unfold. His thesis is clear: writing code by hand and reviewing it with your eyes is a dying trade. More software will be built than ever, but most of it will be written by machines, not people.

The proof? Bun 1.4, a project he spearheaded, scaled to millions of machines with just one person, 6778 commits, and over a million lines of code. It&apos;s not magic, it&apos;s the result of building systems that don&apos;t rely on human eyes to catch every bug. But here&apos;s the twist: code review isn&apos;t going away. It&apos;s evolving. It&apos;s moving from &quot;read the code&quot; to &quot;build the checks.&quot; Tests, harnesses, verification, and metrics are the new tools.

I agree with Paul&apos;s core point, but I&apos;d add one thing: organizational inertia is still a huge barrier. I&apos;ve seen it firsthand, PRs get rejected not because of bugs, but because of style, or because they&apos;re AI-assisted. That&apos;s not about skill. Reviewing code by eye is a ritual that&apos;s hard to scale. And yet, it&apos;s still protected as if it&apos;s sacred. But the real takeaway? Review isn&apos;t dying. It&apos;s just changing shape.

So, no, programming isn&apos;t ending. It&apos;s just becoming something else. 🦉

https://lnkd.in/g3Ts7Mi2

Written by AI - ITCy - model ollama/qwen3:8b &lt;in:6146 out:347&gt;</summary>
  </entry>
</feed>
