Big news for CAD: SMLIB, NVIDIA's NURBS based kernel is finally open source today 🍻🎉
We have been working with SMLIB and its dev team for more than 20 years. It enables all our products: https://t.co/glvclQnzFt headless CAD, GUI, AI/MCP, PDM, etc
https://t.co/q6hnXDXNdK
codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software.
swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go.
admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?".
well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is:
• correct
• bug free
• fast and cost efficient to run
it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start.
but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing!
agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale.
the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree
We need self-replicating factories.
Reindustrialization won't happen against economic laws. Manufacturing has to be competitive worldwide. And improving existing factories, even with automation, is not enough. Only 30-40k robots were installed in the US last year, so the pull from existing factories is weak. They’re good.
Humanoids are being promised as the solution. But who will build them? Still humans. Humanoids not optimised for self-build.
The most practical solution to these problems is a self-replicating factory. It will build humanoids, enable the US reindustrialization, and help colonise other planets as a side product.
Who should I talk to? I’m assembling people who think the same way.
It’d be awesome if logistics software could be visualized and turned into a strategy game.
You manage transportation, routes, and the entire logistics network like you’re playing a strategy game.
Inspired by @DilumSanjaya, I also used Opus 5.5 to build it.
text-to-cad plugin extension is now live on codex!
- generate 3D models as STEP, STL, 3MF, or GLB
- DFM for printing, sheet metal, CNC, injection moulding
- connect to fab services like bambu and sendcutsend
100% open source and free, runs locally inside the codex desktop app
We are releasing → https://t.co/9bfbbdJZip today: AI driven embeddable CAD. If you ever enjoyed my OSS projects (zustand, react-spring, r3f, pmndrs), these all came out of CC. 🍻
A small 🇨🇭 team has been working on CAD for so many years, release seemed always out of reach. This is a huge milestone for us and i'd appreciate a RT. 🙏
this has become one of my most used prompts recently:
> restate in your own words what you think my goals are and what the problem i'm trying to solve is
Why horizontal tabs?
Vertical is navigation. Organizational. Hierarchical. A tree. It's "history". You don't need it on screen all the time.
Horizontal is the working set. The threads that are live. Always visible. Give it icons, colors, status. Context at a glance.
In apps like ChatGPT, Claude Code or T3 Code, horizontal space is expensive. Tabs at the top let you tuck away the sidebar and leave more room for the right panel: preview, browser, code view.
And you still see what's running, what's done, what needs your input.
An .elyx file is a structured, readable description of product design. And while Elyx’s main surface might be a canvas, we’re not hiding that language away behind an MCP server.
You can work with the Elyx language using agents, the CLI, or directly in code view.
From sketch to home, built in 3D with Claude Opus 5.5 using Three.js + TSL. The architecture evolves through four stages: first lines, massing, detail, and finished home.