Took some walking and thinking, we’re on exploration number 3. This is rubber ducking but at a real design level, where the machine helps me place my random ideas into the context of the entire codebase and not just parrot my thoughts back.This time, exploring the approaches that intermediate representation and multiple compiler passes could add to the architecture. This could easily take a couple of days in “the before times” , and would probably be such tunnel vision work that I would lose track of the bigger picture. Certainly I would also hold on to an immature approach by sheer sunk cost fallacy. Today, I easily try out and discard a dozen languages and their compilers before I settle on the proper target architecture. It’s ironically more token efficient than going straight to the answer overall. Think of the amount of effort you’d have to put in editing and fixing even a high level IR instead of modifying a compiler pass. Plus you need to redo it each time.#llms #llm #vibecoding
Took some walking and thinking, we’re on exploration number 3. This is rubber ducking but at a real design level, where ...
