글

Parsing 149 GB of JSON Without Loading It Into Memory

-
이미지
 Part 9 of a series — a Dynamo tunnel geometry that was already finished, a 39-sheet Excel workbook it had never been wired to, the web viewer built to referee the two, and the Revit add-in at the end of it. When the work stopped, it had left 149 GB of snapshots on a desktop drive. The obvious next task was to delete them. This post is about what happened when I tried to establish that deleting them was safe — which turned out to be a longer job than the deletion, and ended with a different answer than the one I started with. What 45 days physically left behind Part of what 45 days left behind: the reference images pulled out of the workbook, on one contact sheet with each source size printed underneath. 57 MB of this, against 149 GB of snapshots. A single verification artefact: source tunnel section with the production candidate drawn over it, and the raw scale conflict stated in the header. Hundreds of files like this one are what the reports directory actually is. Fi...
댓글 쓰기
Read more »

AI Clarifying Questions: A Template From Seven Real Ones

-
이미지
 Part 8 of a series — a Dynamo tunnel geometry that was already finished, a 39-sheet Excel workbook it had never been wired to, the web viewer built to referee the two, and the Revit add-in at the end of it. On 14 July the AI stopped guessing and wrote a list of things it could not decide. Seven questions, thirteen evidence crops, one document. The answers came back the same night, and one of them — a single sentence about a block of concrete nobody had bothered to name — collapsed three other questions and cleared a month of round trips before dawn. Part 4 summarised those seven questions in a table. That table is the most compressed thing in the whole series, and compression hid the interesting part. The answer to Q2 did not arrive because the engineer suddenly became more forthcoming. It arrived because the question had a shape that made it cheap to answer. This part goes through all seven — the wording, the interim handling, why the machine could not settle it alone, what ...
댓글 쓰기
Read more »

Prompt Engineering for BIM: 101 Instructions, One Drawing

-
이미지
 Part 7 of a series — a Dynamo tunnel geometry that was already finished, a 39-sheet Excel workbook it had never been wired to, the web viewer built to referee the two, and the Revit add-in at the end of it. Over eleven days, on a single tunnel section, the transcript logged 106 turns from my side to an AI coding assistant. It wrote thousands of lines of Python and JavaScript in response. But when I went back and read the whole thing, what surprised me was not the code. It was that only 17 of those 106 turns actually asked for a shape. The other 89 were corrections, rejections, questions, requests to see the screen, one long apology for having said the wrong thing — and five that I never typed at all, which section 2 accounts for. The honest count of instructions I actually sent is 101. This post is the transcript. Not a summary of it — the actual sentences, in the order they were said, with what the AI did in response. It is the part of this project I get asked about most, be...
댓글 쓰기
Read more »