Owner / field desk

Ahmed

Ahmed owns the site and turns field-tested work into reusable notes for builders, BIM leads, and tool-minded teams.

Beat: BIM, Revit, automation, and practical technology notes
Published: 19 posts

A length of 1,000 millimetres converts to approximately 3.28084 internal feet, then converts back to 1,000 millimetres for verification.

Oct 18, 20266 min read

Revit API units: convert once, verify twice

A 1,000 mm input can become 304.8 metres if a Revit script treats it as an internal length. Make units explicit, preview the conversion, and verify the actual parameter after writing.

AhmedRevit

Oct 17, 20267 min read

The agentic loop: how to judge AI development work

A practical development loop for AI coding agents: define acceptance criteria, make a bounded change, inspect evidence, and decide when to repair, stop, or ship.

AhmedAI

Jun 27, 20264 min read

Where Ahmed is more confident than Claude

A running log of the moments where Ahmed's hands-on BIM experience beat the model's confident generalizations, starting with Revit journal save history.

AhmedRevit

Jun 8, 20263 min read

Port the behavior, not the identity

A field note on how to ask AI coding agents to copy useful tools between projects without crossing manifests, namespaces, IDs, deployment paths, or ownership boundaries.

AhmedAI

Iconic Subarashi cover artwork for a 250 GB C:\Autodesk\WI folder field note.

May 29, 20262 min read

What I learned from a 250 GB C:\Autodesk\WI folder

A field note on what the C:\Autodesk\WI folder is, why Autodesk installer files can pile up, and what I checked before cleaning disk space.

AhmedRevit

May 27, 20266 min read

BIM automation must survive handoff

Ahmed explains why BIM and Revit automation is only finished when another teammate can run it safely, understand the inputs, recover from mistakes, and trust the handoff.

AhmedBIM

May 27, 20265 min read

AI workflow demos should show the handoff file

Ahmed and Zack explain why AI workflow demos should show the exported file, review notes, cleanup path, and handoff evidence before claiming production value.

AhmedAI

May 27, 20265 min read

Dynamo cleanup scripts need a rollback plan

Ahmed explains why every Dynamo cleanup script needs a rollback plan before it touches live Revit models, parameters, views, or sheets.

AhmedDynamo

May 27, 20265 min read

Family libraries need ownership before automation

Ahmed explains why Revit family libraries need named ownership, standards, review gates, and retirement rules before automation starts reorganizing content.

AhmedRevit

May 27, 20265 min read

How to decide whether a tool belongs in the pipeline

Ahmed gives BIM, AI, and creator teams a practical decision matrix for deciding whether a tool belongs in production, stays in experiments, or gets rejected.

AhmedAI

May 27, 20265 min read

Revit batch tools need a test model first

Ahmed explains why Revit batch tools should prove themselves on a small test model before touching production files, shared standards, or live deliverables.

AhmedBIM

May 27, 20266 min read

Revit cleanup scripts should write reports first

Ahmed explains why Revit cleanup scripts should produce reviewable reports before they rename, delete, rebind, or rewrite anything in a live model.

AhmedRevit

May 27, 20264 min read

Revit family automation needs boring naming rules

Ahmed explains why Revit family automation needs stable, boring naming rules before scripts, agents, or batch tools start touching production content.

AhmedRevit

May 27, 20265 min read

Revit shared parameter file traps I keep hitting

Ahmed turns repeated Revit shared-parameter mistakes into a practical checklist for names, GUIDs, bindings, schedules, and team handoff.

AhmedRevit

May 27, 20265 min read

Shared parameters are an interface

Ahmed explains why Revit shared parameters should be treated like an interface contract between models, families, schedules, tags, exports, and automation.

AhmedBIM