taylorfinley
I believe the temple on Kauai is hand-carved, but I enjoy the contrast of monastic orders using CAD/CAM tooling. It makes perfect sense when you think of the cutting-edge tech it required to make an illuminated manuscript, for example. I suspect there have always been hacker/nerd types among those groups.
[0] https://www.himalayanacademy.com/archive-taka-single-post/?t...
[0] https://rollcall.com/2019/05/08/just-where-is-this-secret-ho...
[0] https://gist.githubusercontent.com/birep/bb865b2799d3f86d55f...
The same guy just bought the company distributing the Musk film (checks notes) 9 days ago; it was then quickly pulled from theaters. Make of that what you will, as the Gizmodo piece says, the timing is certainly odd.
For context, I've currently got 579 registered users. By far, most of them are using it to design brand new projects or to customize our published plans, rather than converting their existing designs into orderable BOMs.
I wonder if you have considered building configurable libraries of designs and/or PCB design features into your MCP? That could allow for building with in-stock, least expensive components. And it opens your product up to tinkerers that wouldn't otherwise design a PCB in KiCad.
I am one such potential customer! I am restoring a classic Skee Ball machine from the early 90s, I want to make a little esp32 board to replace the vintage system board. If I could go from prompt to PO Box for a reasonable price I would certainly be interested.
Sawdust also tracks shop inventory and capabilities, so if you have lumber and fasteners and your table saw configured you can filter down to things you can build with what you have on hand. Could be interesting to do something similar here with e.g. minimum order quantity leftovers.
Also an opportunity to become a marketplace -- if I can design my replacement board then publish it and get a cut of its sales, you can smartly replace OOS or now-more-expensive components, and keep the board purchasable and configurable, solving lots of problems for the open source hardware space.
[1] https://app.sawdust.diy/share/3469b5e6-88f8-43f5-ade0-c373d3...
Sounds like your dad might have gotten a kick out of it! I added sliding miter saws a couple weeks ago, and am working on a jig framework right now.
[0] sawdust.diy
But... boy, the slop smell is strong with this doc.
I would be really interested in seeing what would happen if you gave your agent one turn to clean it all up. You motivated me to share my anti-slop guide [0], which is so unreasonably effective I have hesitated to share it previously -- it's nice to be able to spot the slop from a mile away. But if you have a sec I would be really curious to see the same page after a round of de-smelling.
[0] https://gist.githubusercontent.com/birep/bb865b2799d3f86d55f...
The lower the number the higher the priority, e.g. if production is broken someone might say "This is p -1" (higher than your highest priority).
P0 is "do this immediately", P1 is very important, P2/P3 are like "nice to haves." P100 would mean something like "we will never do this"
And at 8 Euro a month I can't quite justify the Photopea premium plan.
I use it enough I would happily pay say $50 for a self-hosted single user license that will not get updates. But not 8 euro a month forever.
I am finally forcing myself to un-learn the decades of Adobe muscle memory and replace it with gimp/krita. Or maybe I'll vibe up something that does exactly what want and nothing more; bespoke one-off tooling is just so easy to do now.
Edit to add the fix: https://gist.github.com/birep/6f2c8d490c7a29820997d57bd654c3...
I'm building a woodworking app and I've managed to create an autopilot that can take a simple instruction ("get me 5 2x4s", "cut the middle 2x4 into 4 equal pieces", "move the 2x4 3 feet left") and the action instantly happens with next to no lag. There is already an llm but now it can share an intent, and the geometry system shows jev the various actions and jev chooses the action that gets it closer to the goal until it has found a state that matches the intent or gives up. The result is the llm can think "higher level" and let the cheap fast model grind out the options in a relative blink of the eye, without the 30s of reasoning the llm would have done about the various operations it could try.
(This harms the fleshbag)