Tertiary and quaternary protein structures are much more complex than molecules and have emergent properties.

> Do you need a conductive substrate on both sides to apply the release voltage?

Yes, you attach VCC to the substrate you want to remain bonded and GND to the substrate you want to detach.

> How available is it for purchase if you aren't Apple or Samsung?

You can just call up your usual 3M distributor and request it. It's over $2,000 for a 100 meter roll so it's not something you'll usually find in stock at your local Grainger but it's not some super-secret material only available to the biggest manufacturers.

The big money is in really boring industries like mining/oil/resource extraction, power plants, infrastructure, construction, and other industries that are predictable and in high demand everywhere. PE firms often get the best deals because they thrive on those kinds of connections and can offer up large amounts of capital on favorable terms in exchange for first dibs. The "rich get richer" is their primary strategy and it works without minmaxing exploitation because that's a bottom feeder strategy, not one that can guarantee steady returns on tens of billions of dollars.

At least, that’s the theory. The problem is that none of the existing CAD tools (almost all exclusively built on Parasolid) are set up to support agentic workflows. None have proper text based representations, with the possible exception of OnShape’s feature script which is too undocumented and proprietary to be of much use. Even if it was supported, Parasolid isn’t set up to provide the kind of detailed error reporting needed to provide agent feedback.

I’ve been experimenting with this in ECAD by giving agents the ability to edit Altium files directly and it’s been working very well (even with footprint drawings!), but my attempts to do it with MCAD have fallen flat on their face because it’d require developing a geometric kernel from scratch with this workflow in mind.

Reverse engineering [1]. When decompiling a bunch of code and tracing functionality, it's really easy to fill up the context window with irrelevant noise and compaction generally causes it to lose the plot entirely and have to start almost from scratch.

(Side note, are there any OpenAI programs to get free tokens/Max to test this kind of stuff?)

[1] https://github.com/akiselev/ghidra-cli

The low level parts (OLE container, streams and blocks) are easy but the domain specific stuff like deserializing to typed structs is much harder.

I’m using a combination of 100s of megabytes of Ghidra decompiled delphi DLLs and millions of lines of decompiled C# code to do this reverse engineering. I can’t imagine even trying such a large project for LLMs so while a good implementation is still taking a lot of time, it’s definitely a lot cheaper than before.

[1] I saw your red/green TDD article/book chapter and I don’t think you go far enough. Since we have agents, you can generalize red/green development to a lot of things that would be impractical to implement in tests. For example I have agents analyze binary diffs of the file format to figure out where my implementation is incorrect without being bogged down by irrelevant details like the order or encoding of parameters. This guides the agent loop instead of tests.

That said, it should be easier to use as a human to follow along with the agent and Claude Code seems to have an easier time with discovery rather than stuffing all the tool definitions into the context.

Not in the sense that it was viewed as a war by the protestors, but in the sense that the logistics, training, and operations of the Civil Rights movement were a well oiled machine that looked like a well organized, but nonviolent, army (including counterexamples where there was no organization).

One of the most memorable details is how James Lawson trained in nonviolence under Ghandi and came over to train protestors in nonviolent tactics. They gathered in church basements to scream insults and spit on each other to prepare for the restaurant sitins and other ops.

I’ve been using Ghidra to reverse engineer Altium’s file format (at least the Delphi parts) and it’s insane how effective it is. Models are not quite good enough to write an entire parser from scratch but before LLMs I would have never even attempted the reverse engineering.

I definitely would not depend on it for security audits but the latest models are more than good enough to reverse engineer file formats.

I disagree. At least for a little while until models improve to truly superhuman reasoning*, frameworks and libraries providing abstractions are more valuable than ever. The risk/reward for custom work vs library has just changed in unforeseen ways that are orthogonal to time and effort spent.

Not only do LLMs make customization of forks and the resulting maintenance a lot easier, but the abstractions are now the most valuable place for humans to work because it creates a solid foundation for LLMs to build on. By building abstractions that we validate as engineers, we’re encoding human in the loop input without the end-developer having to constantly hand hold the agent.

What we need now is better abstractions for building verification/test suites and linting so that agents can start to automatically self improve their harness. Skills/MCP/tools in general have had the highest impact short of model improvements and there’s so much more work to be done there.

* whether this requires full AGI or not, I don’t know.

IME it pays dividends but it can be really painful. I’ve run into a situation multiple times where I’m using Claude Code to write something, then a week later while working it’ll come up with something like “Oh wait! Half the binaries are in .Net and not Delphi, I can just decompile them with ilspy”, effectively showing the way to a better rewrite that works better with fewer bugs that gets done in a few hours because I’ve got more experience from the v1. Either way it’s tens of thousands of lines of code that I could never have completed myself in that amount of time (which, given problems of motivation, means “at all”).

It honestly might have been easier without that experience because KiCad is open source and their S-expr file format is easy to use. I'm stuck with Altium since that's what I learned on and am used to.

Hear, hear! I’ve got my altium-cli repo open source in Github as well, which is a vibe coded CLI for editing vibe reverse engineered Altium PCB projects. It’s not yet ready for primetime (I’m finishing up the file format reverse engineering this weekend) and the code quality is probably something twelve year old me would have been embarrassed by, but I can already use it and Claude/Gemini to automate a lot of the tedious parts of PCB design like part selection and footprints. I’m almost to the point where Claude Code can use it for the entire EE workflow from part selection to firmware, minus the PCB routing which I still do by hand.

I just ain’t wasting time blogging about it so unless someone stumbles onto it randomly by lurking on HN, they won’t know that Claude Code can now work on PCBs.