글

KMAP: A BIM Knowledge Map in Two Languages, and Why Position Had to Mean Something

-
이미지
Every BIM class I teach runs into the same wall. The vocabulary is not the difficult part, because IFC, ISO 19650, level of development, the common data environment, clash detection and digital twins are all terms that people can define on request. The difficulty is that almost nobody can show how those terms connect to each other on a single page, so each one arrives as an isolated fact and the shape of the field never appears. So I built the page. It is one map of BIM containing 73 terms, 92 relations and 8 clusters, and it exists in Korean and in English with the same structure on both sides. This post shows the map, explains why the clusters are cut the way they are, and then covers the two rounds of tool updates that building the map forced me to make. One page of BIM Solid outline means a person confirmed the term. Dashed outline means the term is still an unreviewed AI draft. At the moment exactly one term out of 73 is confirmed, and the legend prints that accounting in...
댓글 쓰기
Read more »

Dynamo Generative Design for Water Treatment Plant Layout

-
At Autodesk University 2025 I had about three minutes. The segment sits at 27:30 inside Sol Amour's session Exploring the Dynamo Product Road Map and Vision for the Future , which runs 46:30 in total, and the subject was water treatment plant layout generated with Generative Design. Three minutes is a reasonable amount of time to demonstrate that something works. It is nowhere near enough time to show another engineer how to rebuild it. This month the same material had to become a twelve-hour course, delivered over two days to practising engineers at a public-sector training academy. Expanding a three-minute demo by a factor of two hundred and forty sounded absurd when I first wrote the number down, and then I built the curriculum and discovered that the ratio was never the interesting part. A demo and a course are not the same content played at different speeds. They are largely different content, and the portions that survive the translation are not the portions I would have ...
댓글 쓰기
Read more »

Claude Remote Control: Why My Phone Could Not Start a Session

-
 Research Log [2026 08 16]: Diagnosing and Automating a Phone-to-PC Remote Control Link for an LLM Agent 1. Objective Driving an LLM agent on a desktop machine from a phone is useful for a specific reason. The agent operates on the real files that exist only on that machine, including models, scripts, and drawings, so work started at the desk can be continued while away from it. A cloud session cannot do this, because the files are not there. The link had been in use for about a month and it stopped working one morning. This log documents the diagnosis, the three separate causes that were found underneath the failure, and the configuration that now survives a reboot. It also documents six errors in my own diagnostic reasoning, because those errors consumed roughly five hours and are more generally useful than the fix itself. 2. Summary of Work The failure had three independent causes that happened to coincide. A refresh token had expired on a thirty-day clock, an autostar...
댓글 쓰기
Read more »

AEC 3D Viewers: What 32 Tools Chose, and a 5x Speed Gap

-
이미지
 Over the past year I built five different 3D viewers for AEC work - routing, structural review, tunnel sections, a Revit perspective tool, a spreadsheet-to-3D viewer. Before I trusted my own instincts about how to build them, I did two things: I profiled all five on the same GPU, and I studied how 32 other AEC 3D tools - Autodesk Forma, Speckle, TestFit, xeokit, Bentley iTwin, and more - solve the same problem. This post is both halves: what the industry chose, and then what my own measurements showed. The short version is that rendering is a commodity, and the interesting decisions are everywhere else. Part 1 - What 32 AEC viewers actually chose I expected a mess of proprietary engines. Instead the choices collapse into six patterns, and the deciding question is never "which renderer is best" - it is "what is our actual moat."
댓글 쓰기
Read more »

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.
댓글 쓰기
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.
댓글 쓰기
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.
댓글 쓰기
Read more »