One interesting thing now that Claude, etc. enable is writing very specific linear solvers for specific problems.
In my case, I am using IPOPT to optimize something. A generic linear solver like MUMPS is fine, but if your problem is pretty fixed you can very easily get a much faster solver by baking in the elimination order based on what you know about your matrix.
Now that I have distilled my CasADi IPOPT trajectory planner into a small NN my pro peloton simulator runs 50 riders worth of trajectory planning per core with room to spare.
I don't understand why the built in Claude Code Agent tool doesn't support changing the effort. Obviously there are workarounds, but it seems like a simple and useful thing to support directly.
Somehow in college I never was interested in EE (except for the FPGA class I took from Bill Dally), but 20y later working through Razavi Microelectronics I really enjoy it
Interesting note on changing effort in Fable: "And on Fable 5.1, changing it mid-session no longer invalidates the prompt cache (as of 2.1.260)."



