Not enough time, too many projects. Useful projects I did over the weekend with Opus 4.6 and GPT 5.4 (just casually chatting with it). 2025 Taxes Dumped all pdfs of all my tax forms into a single folder, asked Claude the rename them nicely. Ask it to use Gemini 2.5 Flash to extract out all tax-relevant details from all statements / tax forms. Had it put together a webui showing all income, deductions, etc, for the year. Had it estimate my 2025 tax refund / underpay. Result was amazing. I now actually fully understand the tax position. It broke down all the progressive tax brackets, added notes for all the extra federal and state taxes (i.e. Medicare, CA Mental Health tax, etc). Finally had Claude prepare all of my docs for upload to my accountant: FinCEN reporting, summary of all docs, etc. Desk Fabrication Planning on having a furniture maker fabricate a custom walnut solid desk for a custom office standing desk. Want to create a STEP of the exact cuts / bevels / countersinks / etc to help with fabrication. Worked with Codex to plan out and then build an interactive in-browser 3D CAD experience. I can ask Codex to add some component (i.e. a grommet) and it will generate a parameterized B-rep geometry for that feature and then allow me to control the parameters live in the web UI. Codex found Open CASCADE Technology (OCCT) B-rep modeling library, which has a web assembly compiled version, and integrated it. Now have a WebGL view of the desk, can add various components, change their parameters, and see the impact live in 3D.
Actually I don't mind. And I'm using this ability to make sense of a large chunks of foreign code, or messy decompiled code, or broken code that no longer compiles on anything, and translate it to something I understand and is written in modern way and can run on Linux, to my advantage. :) Eg. I needed to use a completely nuttilly complex C++ mess of a code that somehow somewhere implements parsing of Xilinix bitstream (from project x-ray). I just needed to parse the damn bitstream to figure out what registers it initializes and what they are so I can debug a Kintex accelerator board, and X-Ray project has it but I can't compile it on Arch Linux, because C++ and tons of outdated dependencies, and even if I did manage it, would I be able to dump the bitstram in the understandable way anyway, or is the parser just used internally? So yeah, after an hour of trying to just build this mess and fighting dependencies, I gave up and just copied the key code/headers to claude, and told it to write simple linux C program that dumps bitstream header to stdout. Worked on the first try. Very nice clean C program, that just walked a file in the most straightforward manner, and printed what I wanted. The same goes for freaking closed source code that either is buggy, or doesn't do what I want, or is unmaintained old or incompatible, or only for windows, or produces/consumes file formats/protocols I want to understand, or I just want to know what it does. Decompile it completely to a single C file with my fav decompiler, remove fluff and apparently FOSS opensource libraries that it statically links (LLM already has them trained in anyway and they'd just eat context for no reason), and tell the LLM to rewrite it as a clean Linux C program (and maybe tell the LLM what FOSS libraries it's using and copy some key .h files from those, to help it up). Bam, pretty much working replica, much better starting point than just staring at Ghidra and trying to figure out the basics, which I would anyway, but after 100x more hours spent. Same for idiot companies who distribute Linux without source code. Every Linux build contains function names/symbols, unless they really try hard to get rid of them. You can use tools to convert decompressed linux image dumped from somewhere to elf with symbols that is simpler to decompile, and then decompile and just extract specific key HW specific drivers and initializations that you don't have source for. Throw the hand-picked subset of the whole mess into a LLM and tell it to produce a driver for modern Linux kernel, and in a matter of days you have a freaking running Linux 7.0 on a shitty MIPSEL SIP HW phone that was until now running some Linux blob from 2.16 era, with almost full support for every peripheral component on the PCB. That you can have this kind of "rewrite this into that" functionality of LLMs comes at a cost that you can use this against FOSS projects, too, but companies that want to be scummy and steal from FOSS projects, will do so anyway. It was always just too easy. It was not easy at all to do it in the reverse, until now. And personally I think that's more important, and it's great, and worth preserving and celebrating. IoT shit that I had hard time reverse engineering in the past is now reverese engineerable in like 1/50th of the time and effort. :) It's now a weekend project to bring full modern Linux support to some simpler IoT garbage that is sold out there. Even if companies provide Linux source for their IoT shit, it will be some 2.16 era or 3.0 era thing, that is obsolete and insecure, not DT based, and it will have quite messy or needlessly complicated written drivers. LLMs can rewrite this too, to fit the modern Linux standards, remove fluff, etc. This is great for bringin old HW to life, or freeing it from incompetent/overworked (or both) hands of original SW developers and their overlords, who can care less about security or privacy. I hope people who have hard-won experience with reverse engineering from the "before" days have already realized how insanely easy current LLM models make this for people with that experience.
 Top